RE: [JBoss-user] JMS ping timeout exception
Sorry, I was working against head, and wasn't even aware that this fix existed. Wish I had known, since I spent the better part of a day finding the old deadlock. Shame on me for not looking at 3.2 I guess. On the positive side, the current implementation looks slick to me. Much better than the bandaid I was trying to apply. Thanks, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Scott M Stark Sent: Tuesday, January 21, 2003 9:23 PM To: [EMAIL PROTECTED] Subject: Re: [JBoss-user] JMS ping timeout exception Main never had the UIL deadlock fix ported from 3.0 and 3.2 so this really does not apply here. I need to see the thread dump of the main deadlock or else I'm just going to update main with the 3.2 changes. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: John Fawcett [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 1:04 PM Subject: RE: [JBoss-user] JMS ping timeout exception Hi, There is a deadlock bug in the org.jboss.mq.il.uil.multiplexor package. I submitted a patch to this a few days ago, and this is the behavior that lead me to it. I don't know whether the patch is, was or will be applied. Good luck, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sebastian Hauer Sent: Tuesday, January 21, 2003 1:20 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] JMS ping timeout exception Hi, Lately we experience more of these JMS ping timeouts in one of our almost production installations. We get these exceptions on the client side. On the server side we use JBoss 3.0.5 with the UIL IL. Here is the exception: - 17:47:39,093 WARN Connection - Connection failure: org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.) at org.jboss.mq.Connection.asynchFailure(Connection.java:606) at org.jboss.mq.Connection$PingTask.run(Connection.java:1190) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) + nested throwable: java.io.IOException: ping timeout. at org.jboss.mq.Connection$PingTask.run(Connection.java:1182) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) - The client still seems to work, except that we see a lot of these messages in the log output. What could be a cause of this? Could it be related to a slow network? And finally will JMS continue to work reliably? Regards, Sebastian --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
RE: [JBoss-user] JMS ping timeout exception
Hi, There is a deadlock bug in the org.jboss.mq.il.uil.multiplexor package. I submitted a patch to this a few days ago, and this is the behavior that lead me to it. I don't know whether the patch is, was or will be applied. Good luck, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sebastian Hauer Sent: Tuesday, January 21, 2003 1:20 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] JMS ping timeout exception Hi, Lately we experience more of these JMS ping timeouts in one of our almost production installations. We get these exceptions on the client side. On the server side we use JBoss 3.0.5 with the UIL IL. Here is the exception: - 17:47:39,093 WARN Connection - Connection failure: org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.) at org.jboss.mq.Connection.asynchFailure(Connection.java:606) at org.jboss.mq.Connection$PingTask.run(Connection.java:1190) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) + nested throwable: java.io.IOException: ping timeout. at org.jboss.mq.Connection$PingTask.run(Connection.java:1182) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) - The client still seems to work, except that we see a lot of these messages in the log output. What could be a cause of this? Could it be related to a slow network? And finally will JMS continue to work reliably? Regards, Sebastian --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
Re: [JBoss-user] JMS ping timeout exception
Main never had the UIL deadlock fix ported from 3.0 and 3.2 so this really does not apply here. I need to see the thread dump of the main deadlock or else I'm just going to update main with the 3.2 changes. Scott Stark Chief Technology Officer JBoss Group, LLC - Original Message - From: John Fawcett [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, January 21, 2003 1:04 PM Subject: RE: [JBoss-user] JMS ping timeout exception Hi, There is a deadlock bug in the org.jboss.mq.il.uil.multiplexor package. I submitted a patch to this a few days ago, and this is the behavior that lead me to it. I don't know whether the patch is, was or will be applied. Good luck, fawce -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Sebastian Hauer Sent: Tuesday, January 21, 2003 1:20 PM To: [EMAIL PROTECTED] Subject: [JBoss-user] JMS ping timeout exception Hi, Lately we experience more of these JMS ping timeouts in one of our almost production installations. We get these exceptions on the client side. On the server side we use JBoss 3.0.5 with the UIL IL. Here is the exception: - 17:47:39,093 WARN Connection - Connection failure: org.jboss.mq.SpyJMSException: Connection Failed; - nested throwable: (java.io.IOException: ping timeout.) at org.jboss.mq.Connection.asynchFailure(Connection.java:606) at org.jboss.mq.Connection$PingTask.run(Connection.java:1190) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) + nested throwable: java.io.IOException: ping timeout. at org.jboss.mq.Connection$PingTask.run(Connection.java:1182) at EDU.oswego.cs.dl.util.concurrent.ClockDaemon$RunLoop.run(ClockDaemon.jav a:364) at java.lang.Thread.run(Unknown Source) - The client still seems to work, except that we see a lot of these messages in the log output. What could be a cause of this? Could it be related to a slow network? And finally will JMS continue to work reliably? Regards, Sebastian --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user --- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp ___ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
