October 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBMESSAGING-1057) java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment

by gerald zhou (JIRA)

java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment ------------------------------------------------------------------------------- Key: JBMESSAGING-1057 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1057 Project: JBoss Messaging Issue Type: Bug Components: JMS Remoting Affects Versions: 1.2.0.SP1 Environment: boss-4.0.5.GA, java 1.4.2_07 , jboss messaging 1.2.0.SP1 Reporter: gerald zhou Assigned To: Tim Fox java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1054) at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1224) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1050) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.defaultWriteObject(ObjectOutputStream.java:367) at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.writeObject(Unknown Source) 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.invokeWriteObject(ObjectStreamClass.java:809) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1296) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1332) at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1304) at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1247) at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1052) at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:278) at org.jboss.jms.wireformat.SerializedPacket.write(SerializedPacket.java:80) at org.jboss.jms.server.remoting.JMSWireFormat.write(JMSWireFormat.java:245) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.versionedWrite(MicroSocketClientInvoker.java:958) at org.jboss.remoting.transport.socket.MicroSocketClientInvoker.transport(MicroSocketClientInvoker.java:552) at org.jboss.remoting.transport.bisocket.BisocketClientInvoker.transport(BisocketClientInvoker.java:339) at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:122) at org.jboss.remoting.LeasePinger.sendClientPing(LeasePinger.java:283) at org.jboss.remoting.LeasePinger.access$000(LeasePinger.java:20) at org.jboss.remoting.LeasePinger$LeaseTimerTask.run(LeasePinger.java:315) at java.util.TimerThread.mainLoop(Timer.java:432) at java.util.TimerThread.run(Timer.java:382) -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1003) Update queue and topic smoke tests to work with new message redistribution

by Tim Fox (JIRA)

Update queue and topic smoke tests to work with new message redistribution -------------------------------------------------------------------------- Key: JBMESSAGING-1003 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1003 Project: JBoss Messaging Issue Type: Task Reporter: Tim Fox Assigned To: Tim Fox -- 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

17 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1064) MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA

by Daniel Bevenius (JIRA)

MessageID changes when the message is transfered over the cluster with JBM 1.3.0GA ---------------------------------------------------------------------------------- Key: JBMESSAGING-1064 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1064 Project: JBoss Messaging Issue Type: Bug Components: JMS Clustering Affects Versions: 1.3.0.GA Reporter: Daniel Bevenius Assigned To: Tim Fox I'm seeing the same bug that was reported by JIRA:http://jira.jboss.com/jira/browse/JBMESSAGING-1063 with JBM 1.3.0GA. -- 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

17 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-965) JBoss Messaging client fails to reconnect after restart of the server

by pgervais (JIRA)

JBoss Messaging client fails to reconnect after restart of the server --------------------------------------------------------------------- Key: JBMESSAGING-965 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-965 Project: JBoss Messaging Issue Type: Bug Reporter: pgervais Assigned To: Tim Fox There seem to be a clean up problem with the client JBoss Messaging QueueConnection. When following these steps, everything works fine: 1. create a QueueConnection 2. create a QueueSender 3. send a message 4. create QueueReceiver (on the same queue as the QueueSender) 5. receive the sent message 6. close the connection 7. shutdown the JBoss server 8. restart the JBoss server 9. execute step 1-6 Everything works fine But following these steps: 1. create a QueueConnection 2. create a QueueSender 3. send a message 4. create QueueReceiver (on the same queue as the QueueSender) 5. receive the sent message 6. shutdown the JBoss server 7. close the connection (I get an exception, it should be normal) 8. restart the JBoss server 9. execute step 1, I get an exception, this should not be normal After investigating, I think that the problem happens when the close is executed in the second case. It seems that an exception is thrown before all the clean up has been done, because I see a thread named WorkerThread#1[142.117.14.44:3421] (which is my machine address and what seems to be the port on which the thread is listening). That thread was not present in the first case, it disappeared after executing close on the QueueConnection. After further investigation, it seems that the problem is due to a clean up problem with the org.jboss.remoting.InvokerRegistry. The client invoker and server invoker from the previously created connection are not unregistered when the close method fails. -- 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

17 years, 2 months

2
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-634) If Server is restarted, client leases IDs might be out of sync

by Clebert Suconic (JIRA)

If Server is restarted, client leases IDs might be out of sync -------------------------------------------------------------- Key: JBMESSAGING-634 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-634 Project: JBoss Messaging Issue Type: Bug Reporter: Clebert Suconic Assigned To: Ovidiu Feodorov This is the scenario I have: I start the server... I have clients opening/closing connections in a loop... I kill the server... (will ignore the errors on client until I get restarted) I restart the server.... I will get a bunch of errors on client, regarding not being able to find ClientIds on Lease operations (Just WARNs) Kill the client... after some time.. .the server gets into an unexpected state, after we have seen this exception: 20:59:37,765 ERROR [STDERR] java.lang.NullPointerException 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease.notifyClientLost(Lease.java:211) 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease.access$300(Lease.java:39) 20:59:37,765 ERROR [STDERR] at org.jboss.remoting.Lease$LeaseTimerTask.run(Lease.java:242) 20:59:37,765 ERROR [STDERR] at java.util.TimerThread.mainLoop(Timer.java:512) 20:59:37,765 ERROR [STDERR] at java.util.TimerThread.run(Timer.java:462) I consider the description of this JIRA issue very subjective, we should rename it as soon as we have found the real cause. -- 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

17 years, 2 months

2
5
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-923) Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar

by Elias Ross (JIRA)

Creating queue/topic with JNDI subcontexts fails, e.g. names such as queue/foo/bar ---------------------------------------------------------------------------------- Key: JBMESSAGING-923 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-923 Project: JBoss Messaging Issue Type: Bug Reporter: Elias Ross Assigned To: Ovidiu Feodorov The following service.xml will generate an exception: <server> <loader-repository> jboss.messaging:loader=ScopedLoaderRepository <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> <mbean code="org.jboss.jms.server.destination.QueueService" name="jboss.messaging.destination:service=Queue,name=ppm/mt" xmbean-dd="xmdesc/Queue-xmbean.xml"> <depends optional-attribute-name="ServerPeer">jboss.messaging:service=Se rverPeer</depends> <depends>jboss.messaging:service=PostOffice</depends> </mbean> </server> 15:46:12,205 ERROR [ExceptionUtil] Queue[/queue/ppm/bridge/mqube, name=ppm/bridg e/mqube] startService javax.naming.NameNotFoundException: ppm not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:529) at org.jnp.server.NamingServer.getBinding(NamingServer.java:537) at org.jnp.server.NamingServer.getObject(NamingServer.java:543) at org.jnp.server.NamingServer.rebind(NamingServer.java:165) at org.jnp.server.NamingServer.rebind(NamingServer.java:168) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:510) at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477) at org.jboss.jms.server.DestinationJNDIMapper.registerDestination(Destin ationJNDIMapper.java:146) at org.jboss.jms.server.destination.QueueService.startService(QueueServi ce.java:142) -- 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

17 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAOP-474) Synchronize jar file names in distribution zip and maven repo

by Anders Hammar (JIRA)

Synchronize jar file names in distribution zip and maven repo ------------------------------------------------------------- Key: JBAOP-474 URL: http://jira.jboss.com/jira/browse/JBAOP-474 Project: JBoss AOP Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.beta1 Environment: n/a Reporter: Anders Hammar To avoid confusion, the jar file names in the distribution zip and the artifacts in the maven repository should be the same. In the distribution file, the aop jar file for jdk1.4 is called "jboss-aop.jar" and the one for jdk5.0 is called "jboss-aop-jdk50.jar". However, in the maven repo the artifact "jboss-aop" refers to the jdk5.0 jar (and there is no jdk1.4 artifact). -- 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

17 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-4801) HomeHandleImplIIOP not using the HandleDelegate

by Adrian Brock (JIRA)

HomeHandleImplIIOP not using the HandleDelegate ----------------------------------------------- Key: JBAS-4801 URL: http://jira.jboss.com/jira/browse/JBAS-4801 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: IIOP service Affects Versions: JBossAS-4.2.1.GA, JBossAS-5.0.0.Beta2 Reporter: Adrian Brock Assigned To: Adrian Brock Fix For: JBossAS-5.0.0.Beta3, JBossAS-4.2.2.GA The class org.jboss.proxy.ejb.HomeHandleIIOPImpl is not using the HandleDelegate for serialization. This is because the read/writeObject methods are public when they should be private to be invoked by Serialization. Since fixing this will change the serialization of the class (it will write the home stub to the stream instead of currently writing the ior), we need a system property such that people can revert to the previous serialization if it causes them problems. -- 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

17 years, 2 months

3
7
0 / 0

[JBoss JIRA] Created: (EJBTHREE-899) WebServiceRef injection from DD doesn't work

by Carlo de Wolf (JIRA)

WebServiceRef injection from DD doesn't work -------------------------------------------- Key: EJBTHREE-899 URL: http://jira.jboss.com/jira/browse/EJBTHREE-899 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC10 - FD Reporter: Carlo de Wolf -- 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

17 years, 2 months

3
9
0 / 0

[JBoss JIRA] Created: (JBAS-4803) Transaction Manager issue in JBOss Application Server 4.2.1

by kavipriya gnanasambandam (JIRA)

Transaction Manager issue in JBOss Application Server 4.2.1 ----------------------------------------------------------- Key: JBAS-4803 URL: http://jira.jboss.com/jira/browse/JBAS-4803 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Transaction Manager Affects Versions: JBossAS-4.2.1.GA Environment: JBoss Application Server 4.2.1 with Spring and Hibernate Reporter: kavipriya gnanasambandam Assigned To: Adrian Brock Priority: Critical I am running an audited transaction in JBoss Application Server 4.2.1 with Spring and Hibernate. I am getting failures in my testcases stating that org.springframework.transaction.NoTransactionException: No active JTA transaction. Please find the below log org.springframework.transaction.NoTransactionException: No active JTA transaction 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.jta.JtaTransactionManager.registerAfterCompletionWithExistingTransaction(JtaTransactionManager.java:834) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.support.AbstractPlatformTransactionManager.triggerAfterCompletion(AbstractPlatformTransactionManager.java:871) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.support.AbstractPlatformTransactionManager.processRollback(AbstractPlatformTransactionManager.java:774) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.support.AbstractPlatformTransactionManager.rollback(AbstractPlatformTransactionManager.java:722) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.interceptor.TransactionAspectSupport.completeTransactionAfterThrowing(TransactionAspectSupport.java:325) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:111) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176) 2007-10-04 11:40:15,309 ERROR [STDERR] at com.taxware.twe.common.storage.StorageNotificationInterceptor.invoke(StorageNotificationInterceptor.java:91) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:176) 2007-10-04 11:40:15,309 ERROR [STDERR] at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:210) 2007-10-04 11:40:15,309 ERROR [STDERR] at $Proxy86.isAborted(Unknown Source) -- 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

17 years, 2 months

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2007