[
https://issues.apache.org/jira/browse/ODE-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12452150#action_12452150
]
solmaz edited comment on ODE-82 at 4/22/08 12:05 PM:
-----------------------------------------------------------
When servicemix is running aqtivemq's mbean registered to same mbeanserver that
servicemix use. How can i register ode with same mbeanserver
I'M NEW TO SERVICEMIX
solmaz anvar
was (Author: solmaz):
When servicemix is running, in jconsle i can see aqtivemq mbean that seems
register to same mbeanserver which servicemix use.
when i compare OdeLifeCycle.java and JmsLifeCycle.java, i saw in first
class(ode) getExtensionMBeanName() method return null but in second class(jms)
getExtensionMBeanName() return org.apache.servicemix.jms.JmsConfiguration
instance . is it related to registering jms mbean to servicemix mbean server?
I'M NEW TO SERVICEMIX
solmaz anvar
> Register PM API with JMX when Ode is deployed in JBI container
> --------------------------------------------------------------
>
> Key: ODE-82
> URL: https://issues.apache.org/jira/browse/ODE-82
> Project: ODE
> Issue Type: Improvement
> Components: JBI Integration
> Affects Versions: 1.0-incubating
> Reporter: Alex Boisvert
> Assignee: Tammo van Lessen
> Fix For: 1.2
>
>
> As requested on the mailing list, we should register the process management
> (PM) API in JMX when Ode is deployed in a JBI container.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
