Re: [mobicents-public] problems with remote NotificationListener registration
12 views
Skip to first unread message
Wozza Xing
unread,
May 21, 2013, 4:55:29 AM5/21/13
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to mobicent...@googlegroups.com
Can you raise it as a bug please?
On 05/14/2013 01:33 AM, gosha wrote:
> Hi,
>
> I have problems with remote registration of alarm notification listener at
> SLEE MBean server for the AlarmMBean (javax.slee.management:name=Alarm)
> method. The sample listener SimpleListener is just received notifications
> and print in to log about this. It implements NotificationListener and
> Serializable interfaces. Listener is a part of rhq plugin and is added to
> lib folder inside plugin jar. For remote connections to JBoss JMX server
> mc4j is used.
> Attempting to register listener by invoke addNotificationListener operation
> on javax.slee.management:name=Alarm for an MBean running in Jain slee
> 2.7.0 produces the following exception:
>
> org.mc4j.ems.connection.EmsInvocationException: Exception on invocation of
> [addNotificationListener]org.mc4j.ems.connection.EmsConnectException:
> Connection failure getArguments failed
> at
> org.mc4j.ems.impl.jmx.connection.bean.operation.DOperation.invoke(DOperation.java:126)
> ...
> Caused by: org.mc4j.ems.connection.EmsConnectException: Connection failure
> getArguments failed
> Caused by: java.lang.ClassNotFoundException: jslee.alarms.SimpleListener
>
> Any other operations for alarm Mbean and others with using mc4j are
> performed fine.
> I really appreciate any help with this problem.
>