[jopr-issues] [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 # -- 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