Re: Server deadlock
Tim Anderson <[email protected]> Sat, 04 Nov 2006 22:02:22 +1100
| Newsgroups | gmane.comp.java.openjms.user |
|---|---|
| Message-ID | <[email protected]> |
Hard to say. The stack trace looks given suggests you have a version taken around the openjms-0.7.7-alpha 1 release. A deadlock was corrected in the alpha-3 release - try upgrading to this, or grab the latest from CVS. -Tim Marco Lettere wrote: > We experience a strange behaviour of our openjms 0.7.7-dev server. For a > strange reason all receivers registered on any destination stop > receiving messages simultaneously. OnMessge method is not called and > messages remain on the server (message producers continue working as > expected). Only after a complete server restart, messages (also the ones > that where lost) get consumed again. > We use a Athlon SMP (Bi-processor) with Linux Fedora core 4 and java 1.4. > The only hint we have is related to the fact that this behaviour occurs > with intense http-tunnel usage and today, few minutes before the hang-up > the exception reported at the end of the mail was logged on console by > the server. I cannot understand the nature of this exception and if this > can be related to our hang-up problem. > Any suggestions are warmly welcome! > Thank you, > M. > > 2006-11-02 12:20:34,087 ERROR [Scheduler-Worker-1] - > java.rmi.RemoteException: Connection timed out: connect; nested > exception is: > java.net.ConnectException: Connection timed out: connect > java.rmi.RemoteException: Connection timed out: connect; nested > exception is: > java.net.ConnectException: Connection timed out: connect > at > org.exolab.jms.client.net.JmsSessionStubImpl__Proxy.onMessage(JmsSessionStubImpl__Proxy.java:249) > at > org.exolab.jms.server.JmsServerSession.onMessage(JmsServerSession.java:696) > at > org.exolab.jms.messagemgr.QueueConsumerEndpoint.deliverMessages(QueueConsumerEndpoint.java:266) > at > org.exolab.jms.messagemgr.AbstractConsumerEndpoint.run(AbstractConsumerEndpoint.java:309) > at > org.exolab.jms.common.threads.ThreadPoolWorker.runIt(ThreadPoolWorker.java:192) > at > org.exolab.jms.common.threads.ThreadPoolWorker.runWork(ThreadPoolWorker.java:177) > at > org.exolab.jms.common.threads.ThreadPoolWorker.access$000(ThreadPoolWorker.java:64) > at > org.exolab.jms.common.threads.ThreadPoolWorker$1.run(ThreadPoolWorker.java:119) > at java.lang.Thread.run(Thread.java:534) > Caused by: java.net.ConnectException: Connection timed out: connect > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.PlainSocketImpl.doConnect(Unknown Source) > at java.net.PlainSocketImpl.connectToAddress(Unknown Source) > at java.net.PlainSocketImpl.connect(Unknown Source) > at java.net.Socket.connect(Unknown Source) > at java.net.Socket.connect(Unknown Source) > at sun.net.NetworkClient.doConnect(Unknown Source) > at sun.net.www.http.HttpClient.openServer(Unknown Source) > at sun.net.www.http.HttpClient.openServer(Unknown Source) > at sun.net.www.http.HttpClient.<init>(Unknown Source) > at sun.net.www.http.HttpClient.New(Unknown Source) > at sun.net.www.http.HttpClient.New(Unknown Source) > at > sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) > at > sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) > at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown > Source) > at > sun.net.www.protocol.http.HttpURLConnection.getOutputStream(Unknown Source) > at > org.exolab.jms.net.http.HTTPOutputStream.doWrite(HTTPOutputStream.java:189) > at > org.exolab.jms.net.http.HTTPOutputStream.doWrite(HTTPOutputStream.java:166) > at > org.exolab.jms.net.http.HTTPOutputStream.flush(HTTPOutputStream.java:119) > at java.io.DataOutputStream.flush(Unknown Source) > at > org.exolab.jms.net.multiplexer.Multiplexer.send(Multiplexer.java:292) > at > org.exolab.jms.net.multiplexer.MultiplexInputStream.notifyRead(MultiplexInputStream.java:383) > at > org.exolab.jms.net.multiplexer.MultiplexInputStream.copy(MultiplexInputStream.java:369) > at > org.exolab.jms.net.multiplexer.MultiplexInputStream.read(MultiplexInputStream.java:217) > at java.io.ObjectInputStream$PeekInputStream.read(Unknown Source) > at java.io.ObjectInputStream$PeekInputStream.readFully(Unknown > Source) > at > java.io.ObjectInputStream$BlockDataInputStream.readUTFBody(Unknown Source) > at > java.io.ObjectInputStream$BlockDataInputStream.readUTF(Unknown Source) > at java.io.ObjectInputStream.readString(Unknown Source) > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.readObject(Unknown Source) > at > org.exolab.jms.message.TextMessageImpl.readExternal(TextMessageImpl.java:124) > at java.io.ObjectInputStream.readExternalData(Unknown Source) > at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source) > at java.io.ObjectInputStream.readObject0(Unknown Source) > at java.io.ObjectInputStream.readObject(Unknown Source) > at > org.exolab.jms.net.util.SerializationHelper.read(SerializationHelper.java:137) > at org.exolab.jms.net.connector.Request.readArgs(Request.java:189) > at > org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:436) > at > org.exolab.jms.net.orb.DefaultORB$Handler.invoke(DefaultORB.java:468) > at > org.exolab.jms.net.connector.ContextInvocationHandler.invoke(ContextInvocationHandler.java:108) > > atorg.exolab.jms.net.multiplexer.MultiplexedManagedConnection.request(MultiplexedManagedConnection.java:332) > at > org.exolab.jms.net.multiplexer.Multiplexer$1.run(Multiplexer.java:653) > at > EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source) > at java.lang.Thread.run(Unknown Source) > ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642