Bug 756461 - Tomcat - no default value for Manager URL
Tomcat - no default value for Manager URL
Status: NEW
Product: RHQ Project
Classification: Other
Component: Agent (Show other bugs)
4.2
Unspecified Unspecified
low Severity low (vote)
: ---
: ---
Assigned To: RHQ Project Maintainer
Mike Foley
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2011-11-23 11:56 EST by Libor Zoubek
Modified: 2015-11-01 19:45 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Libor Zoubek 2011-11-23 11:56:54 EST
Description of problem:


Version-Release number of selected component (if applicable):
JON 3.0.0.CR2

How reproducible:always


Steps to Reproduce:
1. setup and inventory tomcat
2. go to tomcat's connection settings in JON UI
  
Actual results:

If you check agent's log, you'll find NPE, even before step #2

WARN  [ResourceContainer.invoker.daemon-18] (jboss.on.plugins.tomcat.TomcatServerComponent)- Could not establish connection to the Tomcat instance [11] times for resource [C:\Program Files\Red Hat\Enterprise Web Server\share\apache-tomcat-6.0.32]
org.mc4j.ems.connection.EmsConnectException: Could not connect [null] java.lang.NullPointerException

In JON UI (after setp #2) I get error welcome message

The following connection settings have invalid values: [Manager URL]. The values must be corrected before the settings can be saved.

Right next to the field, there is a hint of default value.

Expected results:
Default Manager URL should be predefined. That would mean NPE in agent log disappears.

Note You need to log in before you can comment on or make changes to this bug.