Unable to access camel MBean Server from JBoss

[deepak_a <an...@gmail.com>]

All,

I run (camel) in a separate JVM.
Camel @ runtime creates and registers MBean management objects with a
MBeanServerinstance in the VM.

Another application deployed in JBoss access this MBean Server.

i.e. a Singleton Bean deployed in Jboss (EAP 6.3.0 / 6.1.0 Alpha) will try
to access this MBean server.
But I have not been able to access it all.

https://developer.jboss.org/thread/248974

I have posted a query in the EAP user forum - (exception log ang sample code
in the link) but have not got any leads so far - would appreciate if some
one can clarify if they have attempted the same?

Note: This used to work fine with JBoss 5.1.0GA but not working in EAP
6.1.0+ -> clearly looks like a Jboss issue - (so sorry for cross posting in
Camel board - but worth a try just in case another Camel user has a similar
architecture)


Regards,
Deepak.




--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-access-camel-MBean-Server-from-JBoss-tp5756949.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Unable to access camel MBean Server from JBoss

[deepak_a <an...@gmail.com>]

Hi,

createConnector="true" is already set.

My question is - is it possible to start MBean server and expose JMX through
Java JSR 160 (remote jmx) instead of RMI.


regards



--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-access-camel-MBean-Server-from-JBoss-tp5756949p5756969.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Unable to access camel MBean Server from JBoss

[Claus Ibsen <cl...@gmail.com>]

Hi

You can set createConnector=true, see
http://camel.apache.org/camel-jmx.html

On Wed, Sep 24, 2014 at 12:24 PM, deepak_a <an...@gmail.com> wrote:
> All,
>
> Just realized the following
>
> JMXConnector:
> service:jmx:rmi:///jndi/rmi://LDN-LRM-PC-189:19999/jmxrmi/camel
>
> I see the above from Camel log.
> Thats the service exposed by Camel's MBEan Server.
> It appears camel exposes only jmx via RMI, while JBoss (EAP 6.1+) supports
> JSR 160 (JMX Remoting).
>
> i.e connecting to Remote MBean server via (JMX Remoting).
>
> Want to find out if i can start Camel and expose JMX via JMX remoting
> instead of RMI?
> -> This was my client (deployed in JBoss) can access the MBean server via
> JMX Remoting?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Unable-to-access-camel-MBean-Server-from-JBoss-tp5756949p5756956.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/

Re: Unable to access camel MBean Server from JBoss

[deepak_a <an...@gmail.com>]

All,

Just realized the following

JMXConnector:
service:jmx:rmi:///jndi/rmi://LDN-LRM-PC-189:19999/jmxrmi/camel

I see the above from Camel log.
Thats the service exposed by Camel's MBEan Server.
It appears camel exposes only jmx via RMI, while JBoss (EAP 6.1+) supports
JSR 160 (JMX Remoting).

i.e connecting to Remote MBean server via (JMX Remoting).

Want to find out if i can start Camel and expose JMX via JMX remoting
instead of RMI?
-> This was my client (deployed in JBoss) can access the MBean server via
JMX Remoting?



--
View this message in context: http://camel.465427.n5.nabble.com/Unable-to-access-camel-MBean-Server-from-JBoss-tp5756949p5756956.html
Sent from the Camel - Users mailing list archive at Nabble.com.