May 2008 - jboss-remoting-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBREM-633) Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-633?page=all ] Ron Sigal closed JBREM-633. --------------------------- Resolution: Won't Fix > Investigate timeout during org.jboss.test.remoting.transport.multiplex.invoker.MultiplexInvokerTestCase > ------------------------------------------------------------------------------------------------------- > > Key: JBREM-633 > URL: http://jira.jboss.com/jira/browse/JBREM-633 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Occurred on 11/4/06 and 11/5/06 for jdk 1.4. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-628) Find source of EOFException in multiplex unit tests on cruisecontrol.

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-628?page=all ] Ron Sigal closed JBREM-628. --------------------------- Resolution: Won't Fix > Find source of EOFException in multiplex unit tests on cruisecontrol. > --------------------------------------------------------------------- > > Key: JBREM-628 > URL: http://jira.jboss.com/jira/browse/JBREM-628 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Some multiplex unit tests, seemingly at random, are failing with EOFException. > E.g., org.org.jboss.test.remoting.transport.multiplex.config.ConfigurationByMapDiffStaticObjectsTestServer. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-577) Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-577?page=all ] Ron Sigal reopened JBREM-577: ----------------------------- > Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-577 > URL: http://jira.jboss.com/jira/browse/JBREM-577 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.GA (Boon) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > This test is failing rather consistently in testRule4ServerFirst() on cruisecontrol, even though this particular failure can't be reproduced on any other environment. In case the problem is more than environmental, i.e., a real problem in Multiplex, some additional log statements will be added to MultiplexServerInvoker and OutputMultiplexor. > What is happening is that in runPushCallbackTests(), the message "stopped callback Connector" appears, but then the test dies before the callback Connector completes its shut down. It would be nice to believe that there is a deadlock, but none is evident, unless it's due to a problem with Collections.synchronizedMap in jdk 1.4. Note that this problem never occurs in the jdk 1.5 cruisecontrol tests. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-577) Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-577?page=all ] Ron Sigal updated JBREM-577: ---------------------------- Fix Version/s: (was: 2.4.0.Beta2 (Pinto)) Removed fix version. > Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-577 > URL: http://jira.jboss.com/jira/browse/JBREM-577 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.GA (Boon) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > This test is failing rather consistently in testRule4ServerFirst() on cruisecontrol, even though this particular failure can't be reproduced on any other environment. In case the problem is more than environmental, i.e., a real problem in Multiplex, some additional log statements will be added to MultiplexServerInvoker and OutputMultiplexor. > What is happening is that in runPushCallbackTests(), the message "stopped callback Connector" appears, but then the test dies before the callback Connector completes its shut down. It would be nice to believe that there is a deadlock, but none is evident, unless it's due to a problem with Collections.synchronizedMap in jdk 1.4. Note that this problem never occurs in the jdk 1.5 cruisecontrol tests. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-577) Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-577?page=all ] Ron Sigal closed JBREM-577. --------------------------- Resolution: Won't Fix > Investigate failure of org.jboss.test.remoting.transport.multiplex.MultiplexInvokerTestCase, jdk 1.4, on cruisecontrol > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBREM-577 > URL: http://jira.jboss.com/jira/browse/JBREM-577 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.0.0.GA (Boon) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > This test is failing rather consistently in testRule4ServerFirst() on cruisecontrol, even though this particular failure can't be reproduced on any other environment. In case the problem is more than environmental, i.e., a real problem in Multiplex, some additional log statements will be added to MultiplexServerInvoker and OutputMultiplexor. > What is happening is that in runPushCallbackTests(), the message "stopped callback Connector" appears, but then the test dies before the callback Connector completes its shut down. It would be nice to believe that there is a deadlock, but none is evident, unless it's due to a problem with Collections.synchronizedMap in jdk 1.4. Note that this problem never occurs in the jdk 1.5 cruisecontrol tests. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-628) Find source of EOFException in multiplex unit tests on cruisecontrol.

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-628?page=all ] Ron Sigal reopened JBREM-628: ----------------------------- > Find source of EOFException in multiplex unit tests on cruisecontrol. > --------------------------------------------------------------------- > > Key: JBREM-628 > URL: http://jira.jboss.com/jira/browse/JBREM-628 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Some multiplex unit tests, seemingly at random, are failing with EOFException. > E.g., org.org.jboss.test.remoting.transport.multiplex.config.ConfigurationByMapDiffStaticObjectsTestServer. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-628) Find source of EOFException in multiplex unit tests on cruisecontrol.

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-628?page=all ] Ron Sigal updated JBREM-628: ---------------------------- Fix Version/s: (was: 2.4.0.Beta2 (Pinto)) Removed fix version. > Find source of EOFException in multiplex unit tests on cruisecontrol. > --------------------------------------------------------------------- > > Key: JBREM-628 > URL: http://jira.jboss.com/jira/browse/JBREM-628 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 2.2.0.Beta1 (Bluto) > Reporter: Ron Sigal > Assigned To: Ron Sigal > > Some multiplex unit tests, seemingly at random, are failing with EOFException. > E.g., org.org.jboss.test.remoting.transport.multiplex.config.ConfigurationByMapDiffStaticObjectsTestServer. -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBREM-549) remove dependancy on concurrent.jar within remoting client

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-549?page=all ] Ron Sigal updated JBREM-549: ---------------------------- Fix Version/s: (was: 2.4.0.Beta2 (Pinto)) Removed fix version. > remove dependancy on concurrent.jar within remoting client > ---------------------------------------------------------- > > Key: JBREM-549 > URL: http://jira.jboss.com/jira/browse/JBREM-549 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > > Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id. Problem is that org.jboss.util.id.GUID is what requires concurrent.jar. So will either need to modify the code within jboss common repository or find another class to use for generating the client session id. > java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong > at org.jboss.util.id.UID.<clinit>(UID.java:56) > at org.jboss.util.id.VMID.create(VMID.java:259) > at org.jboss.util.id.VMID.getInstance(VMID.java:223) > at org.jboss.util.id.GUID.<init>(GUID.java:65) > at org.jboss.remoting.Client.<init>(Client.java:133) > at org.jboss.remoting.Client.<init>(Client.java:210) > at org.jboss.remoting.Client.<init>(Client.java:191) > at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80) -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBREM-549) remove dependancy on concurrent.jar within remoting client

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-549?page=all ] Ron Sigal closed JBREM-549. --------------------------- Resolution: Won't Fix > remove dependancy on concurrent.jar within remoting client > ---------------------------------------------------------- > > Key: JBREM-549 > URL: http://jira.jboss.com/jira/browse/JBREM-549 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > > Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id. Problem is that org.jboss.util.id.GUID is what requires concurrent.jar. So will either need to modify the code within jboss common repository or find another class to use for generating the client session id. > java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong > at org.jboss.util.id.UID.<clinit>(UID.java:56) > at org.jboss.util.id.VMID.create(VMID.java:259) > at org.jboss.util.id.VMID.getInstance(VMID.java:223) > at org.jboss.util.id.GUID.<init>(GUID.java:65) > at org.jboss.remoting.Client.<init>(Client.java:133) > at org.jboss.remoting.Client.<init>(Client.java:210) > at org.jboss.remoting.Client.<init>(Client.java:191) > at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80) -- 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

15 years, 11 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBREM-549) remove dependancy on concurrent.jar within remoting client

by Ron Sigal (JIRA)

[ http://jira.jboss.com/jira/browse/JBREM-549?page=all ] Ron Sigal reopened JBREM-549: ----------------------------- > remove dependancy on concurrent.jar within remoting client > ---------------------------------------------------------- > > Key: JBREM-549 > URL: http://jira.jboss.com/jira/browse/JBREM-549 > Project: JBoss Remoting > Issue Type: Task > Security Level: Public(Everyone can see) > Components: general > Affects Versions: 2.0.0.Beta2 (Boon) > Reporter: Tom Elrod > Fix For: 2.4.0.Beta2 (Pinto) > > > Currently, the remoting clients will require concurrent.jar to be on the classpath because org.jboss.util.id.GUID is used to create the client session id. Problem is that org.jboss.util.id.GUID is what requires concurrent.jar. So will either need to modify the code within jboss common repository or find another class to use for generating the client session id. > java.lang.NoClassDefFoundError: EDU/oswego/cs/dl/util/concurrent/SynchronizedLong > at org.jboss.util.id.UID.<clinit>(UID.java:56) > at org.jboss.util.id.VMID.create(VMID.java:259) > at org.jboss.util.id.VMID.getInstance(VMID.java:223) > at org.jboss.util.id.GUID.<init>(GUID.java:65) > at org.jboss.remoting.Client.<init>(Client.java:133) > at org.jboss.remoting.Client.<init>(Client.java:210) > at org.jboss.remoting.Client.<init>(Client.java:191) > at org.jboss.test.remoting.transport.InvokerClientTest.init(InvokerClientTest.java:80) -- 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

15 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

jboss-remoting-issues May 2008