tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Caldarale, Charles R" <>
Subject RE: [OT] Multi processor issue
Date Wed, 13 Dec 2006 16:05:18 GMT
> From: Christopher Schultz [] 
> Subject: Re: [OT] Multi processor issue
> In that case, the OP could wrap their own request objects to actually
> prevent their bug in production while researching it in dev/test,

The problem with doing so in this case is that while it might avoid this
particular crash of the application, it would not have actually
prevented the bug, and might well contribute to data corruption.  Since
synchronizing on the Request object could result in a request being
processed twice, think what would happen if that were perhaps a funds
transfer operation?  I view such band aids rather skeptically, something
akin to removing asserts because they keep going off...

There's also the matter of the request the second thread was supposed to
be working on, which must have gotten lost somewhere.  For non-critical
applications (and this may well be), it may not matter if you compromise
integrity in the interest of stability; but if you get into a habit of
programming that way, you're at risk of continuing to do so when
correctness is absolutely mandatory.

 - Chuck

MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

To start a new topic, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message