[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: MBean Servic cannot open jms session
adrian@jboss.org
do-not-reply at jboss.com
Thu Jan 10 10:11:28 EST 2008
The JIRA issues says this is fixed.
But I still see it running in JBoss Head with the new claasloader:
| 2008-01-10 15:48:33,126 ERROR [org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager] Failed to start connection info
| java.lang.NullPointerException
| at org.jboss.jms.client.container.FailoverValveInterceptor.invoke(FailoverValveInterceptor.java:87)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
| at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:170)
| at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:106)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate$start_N8025343665958530775.invokeNext(ClientConnectionDelegate$start_N8025343665958530775.java)
| at org.jboss.jms.client.delegate.ClientConnectionDelegate.start(ClientConnectionDelegate.java)
| at org.jboss.jms.client.JBossConnection.start(JBossConnection.java:121)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager$ConnectionInfo.start(ClusterConnectionManager.java:664)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.ensureAllConnectionsCreated(ClusterConnectionManager.java:426)
| at org.jboss.messaging.core.impl.clusterconnection.ClusterConnectionManager.notify(ClusterConnectionManager.java:247)
| at org.jboss.messaging.core.impl.DefaultClusterNotifier.sendNotification(DefaultClusterNotifier.java:72)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.putReplicantLocally(MessagingPostOffice.java:1167)
| at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.put(MessagingPostOffice.java:1420)
| at org.jboss.jms.server.connectionfactory.ConnectionFactoryJNDIMapper.registerConnectionFactory(ConnectionFactoryJNDIMapper.java:240)
| at org.jboss.jms.server.connectionfactory.ConnectionFactory.startService(ConnectionFactory.java:201)
| at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:299)
| at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:196)
|
What is the issue with scoping why does it make a difference?
Seems like you (or aop) have a bad assumption related to classloading?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4118698#4118698
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4118698
More information about the jboss-dev-forums
mailing list