[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy commented on JOPR-89:
-------------------------------------
I will suggest to the EWS team that we provide a blurb in RUNNING.txt, pointing to
startup.sh. As an aside, the reason we put the jmxremote properties in startup.sh as
opposed to catalina.sh was to ensure we avoided
https://issues.apache.org/bugzilla/show_bug.cgi?id=36976.
Manager URL not pre-populated for TC5
-------------------------------------
Key: JOPR-89
URL:
https://jira.jboss.org/jira/browse/JOPR-89
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: Heiko W. Rupp
Assignee: Jay Shaughnessy
The TC5 plugin is relying on the manager url to determine how to connect to the TC
instance
The plugin is looking for -Dcom.sun.management.jmxremote.port on the command line which
is by default not set in EWS-TC5
So the connection fails and the server stays marked as down.
I think we need to either talk to the ews guys to populate this property by default or
have an operation to set it - or at least mention this on description of the manager url
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira