[JBoss JIRA] Created: (JBMESSAGING-596) BrowserTest should close its Connection in tearDown()
by Ron Sigal (JIRA)
BrowserTest should close its Connection in tearDown()
-----------------------------------------------------
Key: JBMESSAGING-596
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-596
Project: JBoss Messaging
Issue Type: Bug
Affects Versions: 1.2.0.Alpha2
Reporter: Ron Sigal
Assigned To: Ovidiu Feodorov
Priority: Minor
Fix For: 1.2.0.Alpha2
Not closing the Connection in BrowserTest.tearDown() leads to some unexpected test failures, due to the confluence of the following facts:
1. Leaving the Connection open leaves a JMSRemotingConnection running, which keeps a Remoting Lease alive on the server side.
2. From time to time during the test suite, ServerPeer is restarted, which resets the objectIDSequence counter, allowing the creation of distinct objects with duplicate ID's.
3. SimpleConnectionManager maps Remoting session id's to ConnectionEndpoints.
4. When a ServerConnectionEndpoint closes, it unregisters itself from the JMSDispatcher.
Now, the following unlikely sequence of events has been observed.
1. When BrowserTest concludes and its JVM terminates, the Remoting LeasePinger stops, leading to an eventual detection of a Remoting connection failure.
2. The connection failure is reported to SimpleConnectionManager, which terminates the associated Messaging Connection. When the ServerConnectionEndpoint unregisters itself from the JMSDispatcher, it actually unregisters a different object with the same object Id.
3. A subsequent test fails with the messages:
main 14:52:27,968 ERROR [ExceptionInterceptor] Caught Exception:
org.jboss.aop.NotFoundInDispatcherException: Object with oid: -2147483539 was not found in the Dispatcher
--
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
18 years, 3 months
[JBoss JIRA] Created: (JBSEAM-332) javabeans in session are not distributable
by Keith Naas (JIRA)
javabeans in session are not distributable
------------------------------------------
Key: JBSEAM-332
URL: http://jira.jboss.com/jira/browse/JBSEAM-332
Project: JBoss Seam
Issue Type: Bug
Components: Core
Environment: Seam 1.0, JBoss 4.0.4GA, Windows Server 2003, Cluster of 4 nodes on 2 machines.
Reporter: Keith Naas
We have an application that makes use of JavaBeans for a lot of our JSF "actions". When one of our nodes is brought down, the session should Seamlessly failover to another node. The user is sent to a different node, but the entire session appears to be in a clean state. We looked through the server logs and saw the following:
2006-08-15 10:47:36,658 ERROR [org.jboss.web.tomcat.tc5.session.JBossCacheService] [.......] loadSession(): id: GWrcdSJEASvXSJnX6fNHNg**exception occurred during serialization: java.lang.ClassNotFoundException: No ClassLoaders found for: com.ourapp.web.beans.WorksheetBean$$EnhancerByCGLIB$$bf40374c
All of our beans are Serializable, but it appears that there is an issue with the cache sync of the CGLib proxy classes. This specific bean does have some service properties that are transients. It also has properties that refer to other Web JavaBeans.
We will be investigating this some more, but we wanted to get this logged since it appears to be a major issue that prevents us from clustering our Seam apps.
--
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
18 years, 3 months