Hi Peter, >>>Do MDBs not allow this? Will I have to insure that all MDBs are >>>ended before I bring down the QM, or if the QM ends before the MDBs >>>come down, then I have to kill them before trying to bring up the QM?
Hmmm. I don't know whether there is anything in the MDB spec that precludes this working. There is no explicit support for it, though, just like there is no explicit support for FAIL_IF_QUIESCING in the JMS spec, it's something unique to WMQ implementation. If I had to guess I would say that it's something the MDB container would have to "honor" - perhaps WL does not? Is there a way to define "custom properties" associated with the MDB, as there is in WAS? Or perhaps WL is using an older version of the WMQ JMS libraries that does not support the FAIL_IF_QUIESCING property? You should be certain that the WMQ V5.3 JMS libraries are being used, and are at least at the CSD03 level, because I know there were some fixes to the FAIL_IF_QUIESCING code in CSD03. You could run a trace and see if the FAIL_IF_QUIESCING property is being set when the MDB starts. I'm afraid that's about all I can tell you, as I know nothing about WLs MDB implementation. Sorry not to be of more help. Regards, Christopher Frank Certified I/T Specialist - WebSphere Software IBM Certified Solutions Expert - Websphere MQ & MQ Integrator -------------------------------------- Phone: 612-397-5532 (t/l 653-5532) mobile: 612-669-3008 e-mail: [EMAIL PROTECTED] 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
