Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cant activate two sipra entities #27

Closed
jaimecasero opened this issue Oct 27, 2016 · 3 comments
Closed

Cant activate two sipra entities #27

jaimecasero opened this issue Oct 27, 2016 · 3 comments
Labels

Comments

@jaimecasero
Copy link

after activating the second one we get:
L
08:38:20,964 ERROR SipResourceAdaptor error in initializing resource adaptor
java.util.TooManyListenersException: Stack already has a listener. Only one listener per stack allowed
at gov.nist.javax.sip.SipProviderImpl.addSipListener(SipProviderImpl.java:221)
at org.mobicents.slee.resource.sip11.SipResourceAdaptor.raActive(SipResourceAdaptor.java:1271)
at org.mobicents.slee.resource.ResourceAdaptorObjectImpl.raActive(ResourceAdaptorObjectImpl.java:255)
at org.mobicents.slee.resource.ResourceAdaptorEntityImpl.activate(ResourceAdaptorEntityImpl.java:374)
at org.mobicents.slee.container.management.ResourceManagementImpl.activateResourceAdaptorEntity(ResourceManagementImpl.java:275)
at org.mobicents.slee.container.management.jmx.ResourceManagementMBeanImpl.activateResourceAdaptorEntity(ResourceManagementMBeanImpl.java:102)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)

This maybe an actual slee isssue, since classloading may be affecting the initialization

@yarel79
Copy link
Contributor

yarel79 commented Oct 30, 2016

PR with the fix created: #28

@yarel79
Copy link
Contributor

yarel79 commented Dec 16, 2016

I guess this issue can be closed, since fix is merged.

@SergeyLee
Copy link
Contributor

@yarel79 Sure. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants