This is an application issue. What should Swift do for you?
Throw the message away? What's if it's really a good message (in production)
and you just forgot to deploy the new class? You'd want to keep the
message, deploy the new class, and continue.
This is not an easy issue to deal with (no silver bullets here).
We have the same issues with our ecommerce application. When an
exception occurs, how do we differentiate between bad data (from new development)
, bad deployment (oops, I forgot to copy that class), system failures (db down),
and how to not loose orders....
-----Original Message-----
From: Duke, Brian [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 10, 2001 10:19 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.
Thanks,
Brian
------------------------------------------------------
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 developersArchive: http://www.mail-archive.com/[email protected]/
