From: Preston <mcf...@po...> - 2004-04-26 15:38:45
|
HI Cedric, Have you tried using a profiler so you can see what all the threads are doing? I ask because I'm wondering if their all in a wait state and the exception causes the notify all to be skipped or something similar. If you don't have a profiler, a good one to try is www.jprofiler.com. I've used it and OptemizeIt to track down several problems with OpenJMS. Preston -----Original Message----- From: ope...@li... [mailto:ope...@li...] On Behalf Of C=E9dric Braem Sent: Monday, April 26, 2004 5:08 AM To: ope...@li... Subject: RE: [openjms-user] Lock in the publishing... Before the system locks in the publishing, I receive the following exception: 10:41:12 ERROR [Thread-76645] (queue.MessagingCommand) - An error occurs when adding the message to the topic [datasynchronization]: Operation sendMessage failed: java.io.InterruptedIOException: Empty packet was returned javax.jms.JMSException: Operation sendMessage failed: java.io.InterruptedIOException: Empty packet was returned at org.exolab.jms.client.mipc.IpcJmsSessionStub.checkReply(IpcJmsSessionStu b.ja va:844) at org.exolab.jms.client.mipc.IpcJmsSessionStub.sendMessage(IpcJmsSessionSt ub.j ava:217) at org.exolab.jms.client.JmsSession.sendMessage(JmsSession.java:867) at org.exolab.jms.client.JmsMessageProducer.sendMessage(JmsMessageProducer. java :285) at org.exolab.jms.client.JmsTopicPublisher.publish(JmsTopicPublisher.java:1 44) at org.exolab.jms.client.JmsTopicPublisher.publish(JmsTopicPublisher.java:9 9) at be.lyncos.base.jms.topic.JmsTopicPublisherManager.publish(Unknown Source) at be.lyncos.ivista.base.queue.MessagingCommand.addMessageToTopic(Unknown Source) at be.lyncos.ivista.base.queue.MessagingCommand.addSynchronizationMessageTo pic( Unknown Source)=20 I presume that this exception is linked with the locking. Any idea? I'm looking for a clue to resolve my problem... C=E9dric > -----Original Message----- > From: ope...@li...=20 > [mailto:ope...@li...] On Behalf=20 > Of C=E9dric Braem > Sent: mercredi 21 avril 2004 9:47 > To: ope...@li... > Subject: RE: [openjms-user] Lock in the publishing... >=20 > Sorry but I don't have Stack trace because it only locks=20 > without generating exception. > I just put the DEBUG level on JMS to obtain more information. >=20 > > -----Original Message----- > > From: ope...@li... > > [mailto:ope...@li...] On Behalf Of Jim=20 > > Alateras > > Sent: lundi 19 avril 2004 22:25 > > To: ope...@li... > > Subject: RE: [openjms-user] Lock in the publishing... > >=20 > > Can you get a stack trace when the polisher locks so we=20 > have an idea=20 > > where it is happening. In OpenJMS you can not specify a=20 > timeout on the=20 > > Connection or Session > >=20 > > Cheers > > </jima> > >=20 > > > -----Original Message----- > > > From: ope...@li... > > [mailto:openjms-user- > > > ad...@li...] On Behalf Of C=E9dric Braem > > > Sent: Monday, April 19, 2004 11:43 PM > > > To: ope...@li... > > > Subject: [openjms-user] Lock in the publishing... > > >=20 > > > I need some help... > > > I have a problem when using OpenJMS but not always !!! > > > Configuration: OpenJms 0.7.6 > > > I have the following method to publish message: > > >=20 > > > public void publish(SynchronizationMessage message, String > > destination) > > > throws JMSException, TechnicalException { > > >=20 > > > JmsTopicConnection connection =3D (JmsTopicConnection)=20 > > > pool.borrowConnection(); > > > Log.info(this.getClass(), "Borrow connection..."); > > > try { > > > TopicSession session =3D connection.getSession(); > > > TextMessage msg =3D > > > session.createTextMessage(message.getXmlmsg()); > > > msg.setJMSType(destination); > > > TopicPublisher topicPublisher =3D > > connection.getPublisher(); > > > > > topicPublisher.setDeliveryMode(DeliveryMode.NON_PERSISTENT); > > > topicPublisher.publish(msg); > > > } finally { > > > pool.releaseConnection(connection); > > > Log.info(this.getClass(), "Release connection...") > > > } > > > } > > >=20 > > > Sometime the system blocks on the publish instruction...=20 > > Like as lock > > on > > > the > > > publish and it doesn't respond (no exception, no error, ...). The > > system > > > treats 200 messages per minute and this locking occurs once a day. > > >=20 > > > My questions: > > > 1. Is somebody has the same problem or similar? > > > 2. Is it possible to put a timeout on a connection or on a > > queue/topic > > or > > > on > > > session? > > >=20 > > > Thank in advance > > >=20 > > > C=E9dric > > >=20 > > >=20 > > >=20 > > >=20 > > > ------------------------------------------------------- > > > This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux=20 > > > tutorial presented by Daniel Robbins, President and CEO of GenToo=20 > > > technologies. Learn everything from fundamentals to system=20 > > > administration.http://ads.osdn.com/?ad_id=1470&alloc_id638&op=CCk > > > _______________________________________________ > > > openjms-user mailing list > > > ope...@li... > > > https://lists.sourceforge.net/lists/listinfo/openjms-user > >=20 > >=20 > >=20 >=20 ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ openjms-user mailing list ope...@li... https://lists.sourceforge.net/lists/listinfo/openjms-user |