ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker Supportmqsistopmsgflow reports timeout - but there is no timeout

Post new topicReply to topic
mqsistopmsgflow reports timeout - but there is no timeout View previous topic :: View next topic
Author Message
dziku007
PostPosted: Mon Dec 23, 2019 4:06 am Post subject: mqsistopmsgflow reports timeout - but there is no timeout Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

Hi,

I have strange effect during execution of shell script. This is command execution and response:
Code:

mqsistopmsgflow AP_BRK -e eP -k TestApp -m x.y.testapp -w 300
BIP1028I: Stopping message flow 'x.y.testapp' on execution group 'eP' (Application 'TestApp', Library '')...
BIP1047E: The operation timed out waiting for a response.


This is how it looks in messages log in /var/log:
Code:

2019-12-23T10:25:49.404693+01:00 sap-lnx-621 IIB[14438]: IBM Integration Bus v90010 (AP_BRK.eP) [Thread 16700] (Msg 1/1) BIP2155I: About to 'stop ' the deployed resource 'x.y.testapp' of type '.MSGFLOW'.
2019-12-23T10:25:50.904475+01:00 sap-lnx-621 IIB[14438]: IBM Integration Bus v90010 (AP_BRK.eP) [Thread 16700] (Msg 1/1) BIP2271I: Deployed resource 'x.y.testapp' (uuid='fa2df032-6501-0000-0080-9d353e70cc70',type='.MSGFLOW') successfully stopped.


The question is: why mqsistopmsgflow command (with -w 300 param) returns timeout while messages log shows that flow stopped in nearly 1 second?

mqsistopmsgflow command is executed in shell script, which looks like here:
Code:
mqsistopmsgflow AP_BRK -e $GROUP -k $APPNAME -m $FLOW -w 300
execcode=$?

if [ $execcode -eq 0 ]; then
# some processing
else
echo "Trouble with flow: "$FLOW
exit 2
fi


After timeout, my script goes into exit 2 statement. This behavior is not deterministic - it almost always work (no timeout), but sometimes not.
Thanks in advance for any suggestion that my help me find the reason for that.

best regards
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Mon Dec 23, 2019 5:26 am Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20341
Location: LI,NY

Have you considered extending the timeout to allow the flow to finish processing in flight messages? Like -w 500?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
dziku007
PostPosted: Mon Dec 23, 2019 6:04 am Post subject: Reply with quote

Apprentice

Joined: 26 Jul 2012
Posts: 32

Could You explain what do You mean saying "in flight messages"? Timeout happens on flows that are synchronous services with its own timeout much less than 300 sec. 300 seconds seems to be a lot of time to finish any in flight messages. And the messages log shows that flow stops in a few seconds which is weird.

Anyway thanks for Your attention.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker Supportmqsistopmsgflow reports timeout - but there is no timeout
Jump to:



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
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.