[
https://jira.jboss.org/jira/browse/JBESB-2218?page=com.atlassian.jira.plu...
]
Pavel Macik commented on JBESB-2218:
------------------------------------
Another exception appears when the server2 is turned off:
2008-12-04 15:36:40,877 ERROR [org.jboss.jms.client.FailoverCommandCenter] Failover
failed
javax.jms.JMSException: Cannot find a cached connection factory delegate for node -1
at
org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:217)
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:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
at
org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
at
org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
at
org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:608)
2008-12-04 15:36:40,878 DEBUG [org.jboss.jms.client.FailoverCommandCenter]
FailoverCommandCenter[ConnectionState[4c9-4hvbibof-1-0uf7ibof-qr6sza-a4wya]] aborted
failover
2008-12-04 15:36:40,881 ERROR [org.jboss.jms.client.container.ConnectionFailureListener]
Caught exception in handling failure
javax.jms.JMSException: Cannot find a cached connection factory delegate for node -1
at
org.jboss.jms.client.container.ClusteringAspect.handleCreateConnectionDelegate(ClusteringAspect.java:217)
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:585)
at org.jboss.aop.advice.PerInstanceAdvice.invoke(PerInstanceAdvice.java:121)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeNext(ClientClusteredConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
at
org.jboss.jms.client.delegate.ClientClusteredConnectionFactoryDelegate.createConnectionDelegate(ClientClusteredConnectionFactoryDelegate.java)
at
org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:129)
at
org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:62)
at
org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:81)
at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:608)
See attached server-2.log .
Exception "javax.jms.IllegalStateException: Cannot find session
with id ..." during clustered/failover testing.
----------------------------------------------------------------------------------------------------------------
Key: JBESB-2218
URL:
https://jira.jboss.org/jira/browse/JBESB-2218
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Message Store
Affects Versions: 4.2.1 CP4
Environment: Linux 2.6.18-53.1.14.el5xen, x86_64, SOA-P 4.2.0 CP03 CR5,
"production" based configuration, jdk1.5.0_12
Reporter: Pavel Macik
Attachments: server-logs.zip
Performing cluster / failover test following this steps:
http://jboss-wiki.brq.redhat.com/Cluster/failover_tests .
I have to set the Clustered attribute of the
org.jboss.messaging.core.jmx.MessagingPostOfficeService mbean to "true", if
dbinstall tool doesn't.
When I remove Failover2(1).esb archive (according to the 15 (17) step) the following
exceptions appears:
2008-12-04 15:32:32,491 ERROR [org.jboss.messaging.util.ExceptionUtil]
ConnectionEndpoint[vb4-md4bibof-1-0uf7ibof-qr6sza-a4wya] sendTransaction
[sb9-vfvbibof-1-0uf7ibof-qr6sza-a4wya]
javax.jms.IllegalStateException: Cannot find session with id
ad4-sd4bibof-1-0uf7ibof-qr6sza-a4wya
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835)
at
org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:489)
...
2008-12-04 15:32:32,498 ERROR [org.jboss.jms.client.container.ClosedInterceptor]
ClosedInterceptor.ClientSessionDelegate[ad4-sd4bibof-1-0uf7ibof-qr6sza-a4wya]: method
redeliver() did not go through, the interceptor is CLOSED
2008-12-04 15:32:32,499 ERROR [org.jboss.resource.adapter.jms.inflow.JmsServerSession]
Failed to commit session transaction
javax.jms.IllegalStateException: The object is closed
at org.jboss.jms.client.container.ClosedInterceptor.invoke(ClosedInterceptor.java:157)
at org.jboss.aop.advice.PerInstanceInterceptor.invoke(PerInstanceInterceptor.java:105)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira