[jopr-issues] [JBoss JIRA] Resolved: (JOPR-89) Manager URL not pre-populated for TC5

Jay Shaughnessy (JIRA) jira-events at lists.jboss.org
Thu Mar 19 15:28:24 EDT 2009


     [ https://jira.jboss.org/jira/browse/JOPR-89?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

        



More information about the jopr-issues mailing list