You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <ui...@incubator.apache.org> on 2008/07/17 18:23:31 UTC
[jira] Updated: (UIMA-1118) Fix "Failed to start jmx connector:
Cannot bind to URL" while starting uima AS service
[ https://issues.apache.org/jira/browse/UIMA-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-1118:
--------------------------------
Attachment: uimaj-as-activemq-UIMA-1118-patch.txt
When starting a collocated ActiveMQ broker, the code checks if there is an existing MBeanServer running in the JVM. If it is, the code plugs-in the MBeanServer to the Broker to prevent an attempt to start another MBeanServer which causes "jmx.ManagementContext - Failed to start jmx connector: Cannot bind to URL ..." message logged by ActiveMQ.
> Fix "Failed to start jmx connector: Cannot bind to URL" while starting uima AS service
> --------------------------------------------------------------------------------------
>
> Key: UIMA-1118
> URL: https://issues.apache.org/jira/browse/UIMA-1118
> Project: UIMA
> Issue Type: Bug
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Priority: Minor
> Attachments: uimaj-as-activemq-UIMA-1118-patch.txt
>
>
> When starting UIMA AS aggregate service on linux ActiveMQ logs "Failed to start jmx connector: Cannot bind to URL". This message is logged when an internal ActiveMQ Broker is starting up.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.