Hi ,
The first message after the Database restart will throw exceptions , later
on after the exception the Broker recovers itself but to handle this
condition you should allow the message to be backed out to the input queue
with Backout threshhold greater than 1 so that the broker tries to
re-prcess the data one more time .
Hope this helps
-Jas
MANPOWER
"Kulbir S. Thind" To
Sent by: MQSeries [EMAIL PROTECTED]
List cc
<[EMAIL PROTECTED]
.AT> Subject
WBIMB Broker restart without
11/16/2004 10:38 AM Broker restart
Please respond to
MQSeries List
<[EMAIL PROTECTED]
.AT>
Hi,
In a scenario where the WBIMB broker database is restarted without the
WBIMB broker being restarted we find that flows throw exceptions when
processing messages as the connection handle for the database is not valid.
Eventually, however the broker manages to re-establish connection with the
broker and continue processing as normal.
Ideally we should be re-starting the broker if the underlying database is
restarted, however for various reasons we want to be able to handle the
scenario above. Is there a way of tuning WBIMB so that it refreshes its
connection handles more regularly?
Also, please note that the database used serves two purposes, its the
broker internal database and the database used by the message flows for
lookups, etc.
TIA,
Kulbir.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
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
