[jboss-jira] [JBoss JIRA] Commented: (JBAS-5120) Problem with JBoss Messaging Post Office Service in all config with new classloader
[ http://jira.jboss.com/jira/browse/JBAS-5120?page=comments#action_12411086 ]
Himadri Das commented on JBAS-5120:
-----------------------------------
Am using JBOSS5.0 Beta4 and can see this exception during start up. Is this fixed ?
This is what I have done ( basically I was trying to achive cluster setup with Beta4 )
1. create profile node_1 (copy all directory from all).
2. create profile node_2 (copy all directory from all)
3. deployers/profileservice-beans.xml.bak to deployers/profileservice-beans.xml for
node_1 , node_2 and all profile.
4. Start node_1 , node_2 and all
I see the above exception in startup of all three profile.
Problem with JBoss Messaging Post Office Service in all config with
new classloader
-----------------------------------------------------------------------------------
Key: JBAS-5120
URL: http://jira.jboss.com/jira/browse/JBAS-5120
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public(Everyone can see)
Components: JMS service
Reporter: Adrian Brock
Assigned To: Scott M Stark
Priority: Critical
Fix For: JBossAS-5.0.0.Beta4
When booting the all configuration I see this error message:
15:48:33,126 ERROR [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)
This is supposedly already fixed in the linked task?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira