It's the destination router that gets stuck. We have remote routers
connected to a central router which is then bridged to WebLogic. The
messages were flowing into the central router and backing up there. They
were not getting bridged. Perhaps the problem is in the bridge?
-----Original Message-----
From: Andreas Mueller [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 10, 2001 11:20 AM
To: [EMAIL PROTECTED]
Subject: [developers] SwiftMQ backed up
> In our usage of SwiftMQ, we send a lot of serialized object messages.
> Friday
> afternoon, I accidentally sent a new object message to our production
> SwiftMQ server that wasn't in it's classpath. As a result, SwiftMQ got
> "stuck" trying to process this message and about 10000 messages got
> backed
> up behind this bad message. I removed the message this morning and
> everything worked just fine. My question is should this happen? It
> seems
> like a possible bug that a bad message should essentially halt the
> whole
> system.
The router doesn't need the class in the classpath. The object is
serialized at the source client and then a byte stream is transferred.
Only the destination client needs the class. Who stucks - the client or
the router?
--
Andreas Mueller, IIT GmbH, Bremen/Germany, http://www.iit.de
SwiftMQ - JMS Enterprise Messaging System, http://www.swiftmq.com
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/[email protected]/
------------------------------------------------------
SwiftMQ developers mailing list * http://www.swiftmq.com
To unsubscribe from this list, send an eMail to
[EMAIL PROTECTED] and write in the body of your message:
UNSUBSCRIBE developers <your-email-address>
Archive: http://www.mail-archive.com/[email protected]/
