[jboss-user] [JBoss Messaging] - ClusteredConnectionFactory : Exception trace in starting second node using jboss messaging

Vijay Rawat [http://community.jboss.org/people/vijayraw] created the discussion "ClusteredConnectionFactory : Exception trace in starting second node using jboss messaging" To view the discussion, visit: http://community.jboss.org/message/564227#564227 -------------------------------------------------------------- Hi All, I am using jboss 4.2.3-GA, jboss-messaging 1.4.0.SP3, jboss-remoting 2.2.2 SP11 I have cluster with 2 nodes. I am using *ClusteredConnectionFactory* with <attribute name="SupportsLoadBalancing">true</attribute> I am able to start first node without any problems with all queues up. When I start second node , I get exception strace -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- 2010-09-29 18:45:43,468 INFO  [org.jboss.jms.server.connectionfactory.ConnectionFactory] org.jboss.jms.server.connectionfactory.ConnectionFactory@13306ad started 2010-09-29 18:45:44,468 WARN  [org.jboss.jms.server.security.SecurityMetadataStore] WARNING! POTENTIAL SECURITY RISK. It has been detected that the MessageSucker component which sucks messages from one node to another has not had its password changed from the installation default. Please see the JBoss Messaging user guide for instructions on how to do this. 2010-09-29 18:45:45,203 ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[71-7v4rjoeg-1-xoeqjoeg-31o2zq-21o4c5] createConsumerDelegate [81-nv4rjoeg-1-xoeqjoeg-31o2zq-21o4c5] javax.jms.InvalidDestinationException: No such destination: JBossQueue[CalendarMessage] has it been deployed?     at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegateInternal(ServerSessionEndpoint.java:1838)     at org.jboss.jms.server.endpoint.ServerSessionEndpoint.createConsumerDelegate(ServerSessionEndpoint.java:252)     at org.jboss.jms.server.endpoint.advised.SessionAdvised.org$jboss$jms$server$endpoint$advised$SessionAdvised$createConsumerDelegate$aop(SessionAdvised.java:94)     at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)     at org.jboss.jms.server.container.SecurityAspect.handleCreateConsumerDelegate(SecurityAspect.java:123)     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)     at java.lang.reflect.Method.invoke(Method.java:597)     at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)     at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)     at org.jboss.jms.server.container.ServerLogInterceptor.invoke(ServerLogInterceptor.java:105)     at org.jboss.jms.server.endpoint.advised.SessionAdvised$createConsumerDelegate_8721389917985689973.invokeNext(SessionAdvised$createConsumerDelegate_8721389917985689973.java)     at org.jboss.jms.server.endpoint.advised.SessionAdvised.createConsumerDelegate(SessionAdvised.java)     at org.jboss.jms.wireformat.SessionCreateConsumerDelegateRequest.serverInvoke(SessionCreateConsumerDelegateRequest.java:100)     at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)     at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866)     at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608)     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420)     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) ----------------------------------------------------------------------------------------------------------- If anyone knows to avoid exception trace. Please let me know. Regards, Vijay Rawat jboss-messaging 1.4.0.SP3 jboss-remoting 2.2.2 SP11 -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/564227#564227] Start a new discussion in JBoss Messaging at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]