[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Heiko W. Rupp commented on JOPR-89:
-----------------------------------
I see that startup.sh has a comment -- so RUNNING.txt should get this comment too --
before startup.sh is mentioned
BUT:
The provided template is bad on linux:
sh -x startup.sh
....
+ JAVA_OPTS=
+ -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=8999
startup.sh: line 52: -Dcom.sun.management.jmxremote: command not found
+ exec ./catalina.sh start
Arguments need to be put into double-quotes and also be exported as otherwise it is not
visible to the catalina.sh script
export JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8999"
We should also point out that the user/password checks can be omitted with
-Dcom.sun.management.jmxremote.authenticate=false and that is may be possible to just
use -Dom.sun.management.jmxremote without port when the user id of tomcat and the agent
are the same.
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
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