[JBoss JIRA] Created: (JBMESSAGING-977) JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
by Ron Sigal (JIRA)
JMSRemotingConnection.setFailed() has a redundant call to org.jboss.remoting.Client.disconnect()
------------------------------------------------------------------------------------------------
Key: JBMESSAGING-977
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-977
Project: JBoss Messaging
Issue Type: Bug
Reporter: Ron Sigal
Assigned To: Tim Fox
Priority: Minor
The call client.disconnect() occurs twice, and the first one should be removed. The result of the first call is that the subsequent call to client.removeListener(callbackManager) fails:
2007-05-25 11:52:12,956 415134 DEBUG [org.jboss.jms.client.remoting.JMSRemotingConnection] (Thread-353:) JMSRemotingConnection[bisocket://10.5.2.224:4457/?NumberOfCallRetries=10&clientMaxPoolSize=100&clientSocketClass=org.jboss.jms.client.remoting.ClientSocketWrapper&dataType=jms&marshaller=org.jboss.jms.server.remoting.JMSWireFormat&numberOfRetries=5&serializationtype=jms&socket.check_connection=false&unmarshaller=org.jboss.jms.server.remoting.JMSWireFormat] failed to cleanly remove callback manager from the client
java.lang.Exception: Can not remove callback listener as remoting client is not connected to server.
at org.jboss.remoting.Client.removeListener(Client.java:1090)
at org.jboss.jms.client.remoting.JMSRemotingConnection.setFailed(JMSRemotingConnection.java:340)
at org.jboss.jms.client.FailoverCommandCenter.failureDetected(FailoverCommandCenter.java:100)
at org.jboss.jms.client.container.ConnectionFailureListener.handleConnectionException(ConnectionFailureListener.java:57)
at org.jboss.jms.client.remoting.ConsolidatedRemotingConnectionListener.handleConnectionException(ConsolidatedRemotingConnectionListener.java:83)
at org.jboss.remoting.ConnectionValidator$1.run(ConnectionValidator.java:346)
--
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, 2 months
[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
18 years, 2 months
[JBoss JIRA] Created: (JBMESSAGING-927) java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
by David (JIRA)
java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
------------------------------------------------------------------------------------------------------------------
Key: JBMESSAGING-927
URL: http://jira.jboss.com/jira/browse/JBMESSAGING-927
Project: JBoss Messaging
Issue Type: Bug
Components: JMS Remoting
Affects Versions: 1.2.0.GA
Environment: jboss 4.2.0CR1, java 1.5, jboss messaging 1.2.0ga
Reporter: David
Assigned To: Ovidiu Feodorov
09:58:12,495 ERROR [ServerThread] failed
java.io.IOException: EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment; class invalid for deserialization
at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:571)
at java.io.ObjectInputStream.readNonProxyDesc(ObjectInputStream.java:1552)
at java.io.ObjectInputStream.readClassDesc(ObjectInputStream.java:1466)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1699)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readArray(ObjectInputStream.java:1634)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1299)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.defaultReadObject(ObjectInputStream.java:479)
at EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap.readObject(ConcurrentHashMap.java:1205)
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 java.io.ObjectStreamClass.invokeReadObject(ObjectStreamClass.java:946)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1809)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.defaultReadFields(ObjectInputStream.java:1908)
at java.io.ObjectInputStream.readSerialData(ObjectInputStream.java:1832)
at java.io.ObjectInputStream.readOrdinaryObject(ObjectInputStream.java:1719)
at java.io.ObjectInputStream.readObject0(ObjectInputStream.java:1305)
at java.io.ObjectInputStream.readObject(ObjectInputStream.java:348)
at org.jboss.jms.wireformat.SerializedPacket.read(SerializedPacket.java:72)
at org.jboss.jms.server.remoting.JMSWireFormat.read(JMSWireFormat.java:307)
at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:641)
at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:523)
at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:377)
at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:159)
09:58:14,711 WARN [Lease] Tried to terminate lease for session id 5c4o1w13-o9260j-ezjuc4ur-1-ezjuc5w1-4, but no collection of clients have been set.
09:58:14,711 WARN [Lease] Tried to terminate lease for session id null, but no collection of clients have been set.
That exception can be caused when using the jboss-messaging-client.jar that ships with the jboss-messaging release. The jboss-messaging-client.jar contains a version of EDU.oswego.cs.dl.util.concurrent.ConcurrentHashMap$Segment that implements Serializable. However, the jboss app server contains a "concurrent.jar" that has a version of ConcurrentHashMap$Segment that does not implement Serializable. Replacing the version of lib/concurrent.jar with a version of concurrent.jar that contains a ConcurrentHashMap$Segment that implements Serializable will solve this issue.
This situation occurs when you have a remote client that sends a message to a Queue.
--
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, 2 months
[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
18 years, 2 months
[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
18 years, 2 months
[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
18 years, 2 months
[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
18 years, 2 months