February 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-831) Simple (non-clustered) smoke test fails with Remoting exceptions on client and server-side

by Ovidiu Feodorov (JIRA)

Simple (non-clustered) smoke test fails with Remoting exceptions on client and server-side ------------------------------------------------------------------------------------------ Key: JBMESSAGING-831 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-831 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ron Sigal Priority: Blocker Fix For: 1.2.0.CR1 Client-side: [java] 01:18:59,984 ERROR @main [SocketClientInvoker] Got marshalling exception, exiting [java] java.net.SocketException: end of file [java] at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:555) [java] at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) [java] at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:257) [java] at org.jboss.remoting.LeasePinger.addClient(LeasePinger.java:107) [java] at org.jboss.remoting.MicroRemoteClientInvoker.establishLease(MicroRemoteClientInvoker.java:390) [java] at org.jboss.remoting.Client.setupClientLease(Client.java:1405) [java] at org.jboss.remoting.Client.connect(Client.java:1284) [java] at org.jboss.remoting.Client.connect(Client.java:431) [java] at org.jboss.jms.client.remoting.JMSRemotingConnection.start(JMSRemotingConnection.java:227) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:149) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) [java] at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:86) [java] at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect0.invoke(StateCreationAspect0.java) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) [java] at org.jboss.jms.client.container.ExceptionInterceptor.invoke(ExceptionInterceptor.java:71) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) [java] at org.jboss.jms.client.container.ClientLogInterceptor.invoke(ClientLogInterceptor.java:107) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.invokeNext(ClientConnectionFactoryDelegate$createConnectionDelegate_4579211046834694258.java) [java] at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java) [java] at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:212) [java] at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:88) [java] at org.jboss.jms.client.JBossConnectionFactory.createConnection(JBossConnectionFactory.java:83) [java] at org.jboss.example.jms.queue.QueueExample.example(QueueExample.java:71) [java] at org.jboss.example.jms.common.ExampleSupport.run(ExampleSupport.java:137) [java] at org.jboss.example.jms.queue.QueueExample.main(QueueExample.java:137) [java] 01:19:00,000 WARN @main [LeasePinger] LeasePinger[SocketClientInvoker[d09ad3, socket://10.11.14.105:4457](abe2x-uu4gkp-ey44if5q-1-ey44ifkh-5)] failed to ping to server: Failed to communicate. Problem during marshalling/unmarshalling; nested exception is: [java] java.net.SocketException: end of file Server-side: 01:18:59,968 ERROR [ServerThread] failed java.io.IOException: org.jboss.remoting.ClientHolder at java.net.URLClassLoader$1.run(URLClassLoader.java:199) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) at java.lang.ClassLoader.loadClass(ClassLoader.java:289) at java.lang.ClassLoader.loadClass(ClassLoader.java:235) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:302) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:219) at java.io.ObjectInputStream.resolveClass(ObjectInputStream.java:558) at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1513) at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1435) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1626) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1218) 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:324) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1218) 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:324) at java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:838) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1746) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1845) at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1769) at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1646) at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1274) at java.io.ObjectInputStream.readObject(ObjectInputStream.java:324) at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:78) at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:314) at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:640) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:522) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159) 01:18:59,984 ERROR [ServerThread] Worker thread initialization failure -- 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

19 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBAS-3583) HAPartition should use its Marshaller for marshalling RPC responses

by Brian Stansberry (JIRA)

HAPartition should use its Marshaller for marshalling RPC responses ------------------------------------------------------------------- Key: JBAS-3583 URL: http://jira.jboss.com/jira/browse/JBAS-3583 Project: JBoss Application Server Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Clustering Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: JBossAS-5.0.0.CR1 JGroups 2.4 adds the ability to marshal RPC responses in addition to requests. Need to update the Marshaller used by HAPartition to take advantage of this so arbitrary classes can be return values for RPC calls. -- 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

19 years, 2 months

3
2
0 / 0

[JBoss JIRA] Updated: (JBAS-2823) Upgrade commons-logging to v1.1

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ] Dimitris Andreadis updated JBAS-2823: ------------------------------------- Comment: was deleted > Upgrade commons-logging to v1.1 > ------------------------------- > > Key: JBAS-2823 > URL: http://jira.jboss.com/jira/browse/JBAS-2823 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Environment: Windows XP Professional, JDK 1.5.0 > Reporter: Martin Lui > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.0.CR1 > > > The Apache commons-logging package has release version 1.1.0. > Please upgrade this library to take advantage of items listed in the release notes: > http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt > It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library. > Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286) > Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet). -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-2823) Upgrade commons-logging to v1.1

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ] Dimitris Andreadis closed JBAS-2823. ------------------------------------ Resolution: Done > Upgrade commons-logging to v1.1 > ------------------------------- > > Key: JBAS-2823 > URL: http://jira.jboss.com/jira/browse/JBAS-2823 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Environment: Windows XP Professional, JDK 1.5.0 > Reporter: Martin Lui > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.0.CR1 > > > The Apache commons-logging package has release version 1.1.0. > Please upgrade this library to take advantage of items listed in the release notes: > http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt > It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library. > Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286) > Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet). -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBAS-2823) Upgrade commons-logging to v1.1

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2823?page=all ] Dimitris Andreadis reopened JBAS-2823: -------------------------------------- Scott, there is still a failing test: testWarCommonsLoggingLog4jOverrides Error Server returned HTTP response code: 500 for URL: http://10.16.68.127:8080/common-logging/Log4jServlet/ java.io.IOException: Server returned HTTP response code: 500 for URL: http://10.16.68.127:8080/common-logging/Log4jServlet/ at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1174) at java.net.URLConnection.getContent(URLConnection.java:682) at java.net.URL.getContent(URL.java:1021) at org.jboss.test.classloader.test.ScopingUnitTestCase.testWarCommonsLoggingLog4jOverrides(ScopingUnitTestCase.java:147) > Upgrade commons-logging to v1.1 > ------------------------------- > > Key: JBAS-2823 > URL: http://jira.jboss.com/jira/browse/JBAS-2823 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Logging > Affects Versions: JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1 > Environment: Windows XP Professional, JDK 1.5.0 > Reporter: Martin Lui > Assigned To: Scott M Stark > Fix For: JBossAS-4.2.0.CR1 > > > The Apache commons-logging package has release version 1.1.0. > Please upgrade this library to take advantage of items listed in the release notes: > http://jakarta.apache.org/commons/logging/RELEASE-NOTES.txt > It would be helpful if this upgrade can be done to upgrade the server libraries since individual EAR files cannot overwrite this particular library. > Also, looking through the notes and searching for information on the 1.0.4 patch, it appears that the WeakHashTables memory-leak fix is included in 1.1.0. (Bug 31286: http://issues.apache.org/bugzilla/show_bug.cgi?id=31286) > Depending on how JBoss uses this package, upgrading should be as simple as replacing the current package (though I admit I had not try doing so yet). -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4079) failing org.jboss.test.tm.test.Simple*LocalStressTestCase

by Dimitris Andreadis (JIRA)

failing org.jboss.test.tm.test.Simple*LocalStressTestCase --------------------------------------------------------- Key: JBAS-4079 URL: http://jira.jboss.com/jira/browse/JBAS-4079 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Test Suite Environment: Java Version 1.5.0_10 Java Vendor Sun Microsystems Inc. Java VM Name Java HotSpot(TM) Client VM Java VM Version 1.5.0_10-b03 Java VM Info mixed mode OS Name Linux OS Version 2.6.9-42.0.2.EL OS Arch i386 Reporter: Dimitris Andreadis Assigned To: Jonathan Halliday Fix For: JBossAS-4.2.0.CR1 e.g. testSimpleTransactionLocalStressTestcase Error not supported javax.transaction.SystemException: not supported at org.jboss.cache.transaction.DummyBaseTransactionManager.setTransactionTimeout(DummyBaseTransactionManager.java:149) at org.jboss.test.tm.test.SimpleNoLockTransactionLocalStressTestCase.testSimpleTransactionLocalStressTestcase(SimpleNoLockTransactionLocalStressTestCase.java:36) -- 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

19 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-744) org.jboss.test.messaging.jms.QueueTest fails if executed using Clustering configuration

by Clebert Suconic (JIRA)

org.jboss.test.messaging.jms.QueueTest fails if executed using Clustering configuration --------------------------------------------------------------------------------------- Key: JBMESSAGING-744 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-744 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta1, 1.2.0.Beta2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.CR1 That might be because of stopServerPeer not properly shutting down something, or it's a real bug. We should investigate. -- 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

19 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBFORUMS-171) Add SubscribeTopicVIew

by Ryszard Kozmik (JIRA)

Add SubscribeTopicVIew ---------------------- Key: JBFORUMS-171 URL: http://jira.jboss.com/jira/browse/JBFORUMS-171 Project: JBoss Forums Issue Type: Sub-task Components: Forum View Layer Reporter: Ryszard Kozmik Assigned To: Ryszard Kozmik Fix For: 1.0.1 RC Add subscribe to topic view with new design. -- 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

19 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-816) Verify if pre-configured IDs are throwing an exception properly.

by Clebert Suconic (JIRA)

Verify if pre-configured IDs are throwing an exception properly. ---------------------------------------------------------------- Key: JBMESSAGING-816 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-816 Project: JBoss Messaging Issue Type: Bug Affects Versions: 1.2.0.Beta2 Reporter: Clebert Suconic Assigned To: Clebert Suconic Fix For: 1.2.0.CR1 DuplicateClientIDTest::testPreconfiguredDuplicateClientID is failing for this but this might be a configuration issue of the testsuite. So.. .we have to check this. -- 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

19 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1218) Listing users will always display an even number of lines

by Thomas Heute (JIRA)

Listing users will always display an even number of lines --------------------------------------------------------- Key: JBPORTAL-1218 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1218 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.Alpha1 Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.Beta1 When searching for users, the GUI will always show an even number of line, adding an emply line if the list contains an odd number of users. -- 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

19 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2007