Rick,
I'd anticipate treating the apps with small buffers as non destructive
getter's and waking them all in the event that I couldn't find a true
destructive get for the message.
Andy.
Richard Brunette <[EMAIL PROTECTED]>@AKH-WIEN.AC.AT> on
05/30/2002 05:33:10 PM
Please respond to MQSeries List <[EMAIL PROTECTED]>
Sent by: MQSeries List <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
cc:
Subject: Re: Problem receiving messages from a restarted client
application.
Andy
Please keep in mind when you are deciding what to wake, that in the
original problem both applications had the same size buffer. Both where
surrogates of two instances of the same Java application. Both start their
gets with a 4096 buffer and when it/if fails the Java internals come back
to the surrogate with a larger buffer. The difference between the two is
one had crashed so only the surrogate was left around. The instance that
was started to replace it was waiting with the same initial buffer. As this
is common in the object interfaces, we would like to see a solution that
with let a waiting second client process even if at first glance this
client does not appear any more capable of handling the message. In reality
it was.
Thanks,
Rick
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
Instructions for managing your mailing list subscription are provided in
the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://vm.akh-wien.ac.at/MQSeries.archive
