| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| JMSAdmin and FAILIFQUIESCE |
« View previous topic :: View next topic » |
| Author |
Message
|
| meekings |
 Posted: Tue Apr 22, 2003 11:37 am Post subject: JMSAdmin and FAILIFQUIESCE |
 |
|
Voyager
Joined: 28 Jun 2001
Posts: 86
Location: UK, South West
|
Why is the FAILIFQUIESCE property of a QCF not documented anywhere in the JMSAdmin documentation (at least, I can't find it)? It defaults to YES, but it's possible to change it to NO. Maybe because it doesn't make sense to set it to NO?
Is there ever a valid reason (JMS or MQI) not to set fail-if-quiescing?
_________________
Brian Meekings
Information Design, Inc. |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue Apr 22, 2003 12:26 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
It is documented in "USing Java" manual chapter 5.
http://www-3.ibm.com/software/integration/library/manualsa/
FAILIFQUIESCE FIQ Yes - Applications return from a method call if the queue manager has entered a controlled shutdown.
No - Applications continue to carry out operations against a quiescing queue manager, preventing that queue manager's shutdown.
-------
Venny |
|
| Back to top |
|
|
| meekings |
| Posted: Wed Apr 23, 2003 3:53 am Post subject: |
|
|
Voyager
Joined: 28 Jun 2001
Posts: 86
Location: UK, South West
|
Thanks Venny - I must have old documentation. But I'd still like to know if there's ever a valid reason NOT to set this to yes (from any API).
_________________
Brian Meekings
Information Design, Inc. |
|
| Back to top |
|
|
| bower5932 |
| Posted: Wed Apr 23, 2003 7:18 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
I found this in the Application Programming Guide:
| Quote: |
If the queue manager is stopped by an operator while an application is running, the quiesce option is normally used. The queue manager enters a quiescing state in which applications can continue to do work, but they should terminate as soon as it is convenient. Small, quick applications can probably ignore the quiescing state and continue until they terminate as normal. Longer running applications, or ones that wait for messages to arrive, should use the fail if quiescing option when they use the MQOPEN, MQPUT, MQPUT1, and MQGET calls. These options mean that the calls fail when the queue manager quiesces, but the application may still have time to terminate cleanly by issuing calls that ignore the quiescing state. Such
applications could also commit, or back out, changes they have made, and then terminate. |
|
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
