I'm using Tomcat standalone and JBossMQ with Jetty which I do not use. I suspect I need to add some code to catch the exception and try to reconnect, but the problem is it's hard to distinguis a "i'm not connected" exception from a normal JMS exception.
> -----Original Message----- > From: Vernon Wu [mailto:[EMAIL PROTECTED]] > Sent: mercredi 16 octobre 2002 12:52 > To: Jakarta Commons Users List > Subject: Re: [Messenger] Problems when JMS servers goes down > > > Hi, Michael, > > I don't have an answer for your question. I, however, would > like to know what JMS server you use to integrated with > TC. From the error messages you provided, it seems that you > use JBossMS. Do you integrate TC with JBossMS only, or > with JBoss? > > Thanks, > > Vernon > > 10/16/2002 6:49:02 AM, "Michael" <[EMAIL PROTECTED]> wrote: > > >If my JMS server is running (and continues to run) before I start > >Tomcat, everything is OK. But if the JMS server goes down my > >application stops working even after the JMS server goes back up. > > > >Here is the exception I get: > > > >15:36:35,671 WARN MessageService - JMSException while > posting status: > >org.jboss.mq.SpyJMSException: Cannot send a message to the > JMS server; > >- nested throwable: (java.net.SocketException: Connection reset by > >peer: socket write error) > >org.jboss.mq.SpyJMSException: Cannot send a message to the > JMS server; > >- nested throwable: (java.net.SocketException: Connection reset by > >peer: socket write error) > > at org.jboss.mq.Connection.sendToServer(Connection.java:1127) > > at org.jboss.mq.SpySession.sendMessage(SpySession.java:562) > > at > >org.jboss.mq.SpyTopicPublisher.internalPublish(SpyTopicPublis > her.java:1 > >2 > >0) > > at > >org.jboss.mq.SpyTopicPublisher.publish(SpyTopicPublisher.java:68) > > at > >org.apache.commons.messenger.MessengerSupport.send(MessengerS > upport.java > >:138) > > at > >com.idtect.detector.message.MessageService.postStatus(Message > Service.jav > >a:62) > > at > >com.idtect.detector.message.MessageService$myTask.run(Message > Service.jav > >a:101) > > at java.util.TimerThread.mainLoop(Timer.java:432) > > at java.util.TimerThread.run(Timer.java:382) > >Caused by: java.net.SocketException: Connection reset by peer: socket > >write error > > at java.net.SocketOutputStream.socketWrite0(Native Method) > > at > >java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92) > > at > >java.net.SocketOutputStream.write(SocketOutputStream.java:136) > > at > >java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream > .java:69) > > at > >java.io.BufferedOutputStream.write(BufferedOutputStream.java:108) > > at > >java.io.ObjectOutputStream$BlockDataOutputStream.drain(Object > OutputStrea > >m.java:1637) > > at > >java.io.ObjectOutputStream$BlockDataOutputStream.writeByte(Ob > jectOutputS > >tream.java:1675) > > at > >java.io.ObjectOutputStream.writeByte(ObjectOutputStream.java:684) > > at > >org.jboss.mq.il.oil.OILServerIL.addMessage(OILServerIL.java:217) > > at org.jboss.mq.Connection.sendToServer(Connection.java:1119) > > ... 8 more > > > > > > > > > > > >-- > >To unsubscribe, e-mail: > <mailto:commons-user-> [EMAIL PROTECTED]> > >For > additional commands, > e-mail: > ><mailto:[EMAIL PROTECTED]> > > > > > > > > > -- > To unsubscribe, e-mail: > <mailto:commons-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
