6:01 a.m.
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
6:31 a.m.
New subject: [JBoss JIRA] Commented: (JOPR-89) Manager URL not pre-populated for TC5
[
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
6:49 a.m.
New subject: [JBoss JIRA] Commented: (JOPR-89) Manager URL not pre-populated for TC5
[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Heiko W. Rupp commented on JOPR-89:
-----------------------------------
About the password file:
Have us delver a default one in tc5/conf and set
-Dcom.sun.management.jmxremote.password.file=/home/hrupp/jboss-ews-1.0/tomcat5/conf/passwordfile
Same for the access file:
-Dcom.sun.management.jmxremote.access.file=home/hrupp/jboss-ews-1.0/tomcat5/conf/accessfile
And we need to document either how to correctly set up SSL or
-Dcom.sun.management.jmxremote.ssl=false
---------
So this is the final entry for startup.sh to get a connection to TC5:
export JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.port=8999
-Dcom.sun.management.jmxremote.password.file=/home/hrupp/jboss-ews-1.0/tomcat5/conf/passwdfile
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.access.file=/home/hrupp/jboss-ews-1.0/tomcat5/conf/accessfile"
with conf/accessfile :
[hrupp@fedora9 bin]$ cat ../conf/accessfile
heiko readwrite
and conf/passwdfile :
[hrupp@fedora9 bin]$ cat ../conf/passwdfile
heiko secret
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
3:52 p.m.
New subject: [JBoss JIRA] Assigned: (JOPR-89) Manager URL not pre-populated for TC5
[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy reassigned JOPR-89:
-----------------------------------
Assignee: Jay Shaughnessy
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
3:56 p.m.
New subject: [JBoss JIRA] Commented: (JOPR-89) Manager URL not pre-populated for TC5
[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy commented on JOPR-89:
-------------------------------------
The bad entry in the startup.sh file is a known issue with CR2 and we already have
commitment to update it with the following :
# JON/Jopr Management
# To enable EWS for JON/Jopr management it is necessary to enable remote JMX access to the
EWS server:
# 1) Choose an unused and accessible portNum
# 2) Follow the steps for secure access as described here:
http://java.sun.com/j2se/1.5.0/docs/guide/management/agent.html.
# 3) Update and uncomment the following lines:
#
# JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.port=<port>"
# JAVA_OPTS="$JAVA_OPTS
-Dcom.sun.management.jmxremote.access.file=<access-file-path>"
# JAVA_OPTS="$JAVA_OPTS
-Dcom.sun.management.jmxremote.password.file=<password-file-path>"
# JAVA_OPTS="$JAVA_OPTS -Dcom.sun.management.jmxremote.ssl=false"
# export JAVA_OPTS
#
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
4:01 p.m.
New subject: [JBoss JIRA] Commented: (JOPR-89) Manager URL not pre-populated for TC5
[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy commented on JOPR-89:
-------------------------------------
Heiko, your idea of including the access and password files is a good one and we discussed
with the EWS team the possibility of providing pretty much what you have described. But
they were more comfortable with a solution involving just the commented out text and no
additional artifacts. So, we've put the link to the secure access setup instructions
in the comment to hopefully help the admin.
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
4:03 p.m.
New subject: [JBoss JIRA] Commented: (JOPR-89) Manager URL not pre-populated for TC5
[
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
2:28 p.m.
New subject: [JBoss JIRA] Resolved: (JOPR-89) Manager URL not pre-populated for TC5
[
https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy resolved JOPR-89.
---------------------------------
Resolution: Done
The JON Hooks for EWS 1.0 are finalized and in EWS CR4. They include commented out
jmxremote property hooks in bin/startup.sh as well as a blurb in RUNNING.txt. Not related
to this Jira but we also have rtfilter hooks in the conf/web.xml, again, commented at
install time.
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
5763
days inactive
5771
days old
7 comments
2 participants
participants (2)
-
Heiko W. Rupp (JIRA) -
Jay Shaughnessy (JIRA)