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 Index » WebSphere Message Broker (ACE) Support » Message flows are not responding to commands.

Post new topic  Reply to topic
 Message flows are not responding to commands. « View previous topic :: View next topic » 
Author Message
cvag
PostPosted: Tue Aug 11, 2009 4:41 am    Post subject: Message flows are not responding to commands. Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

Hi All,
Having the problem with the message flow running.

Developed the flow and successfully deployed on to the broker. But the message flow is not able to pick the messages from input queue, flow is not able to trigger.

The error at log is:
Execution Group [EG_MYM_06] failed to return an internal configuration Start message response within a 60 second time period.

Tried with all options in
1) Restaring the broker
2) Tracing the flow at broker level (same error response time out)
3) And thinking that this issue is due to memory, stopped all the services and increased the javaheap memory.

When trying to undeploy the flows inorder to redeploy ..the messageflows are not responding to stop.

Message flow are not responding to any of the admin commands.

Can you please give any suggestions..

Thanks in Advance
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Aug 11, 2009 4:49 am    Post subject: Re: Message flows are not responding to commands. Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

cvag wrote:
Hi All,
Developed the flow and successfully deployed on to the broker.


I would say that you have not done this successfully.

Flows are not triggered, they will open the input queue and issue MQGET with MQGMO_WAIT on it.

If the input open count of the queue is zero, the flow has not deployed properly as it will automatically start (if it is a new flow anyway).

----------------

Are any of these system queues non-zero depth?

– SYSTEM.BROKER.CONFIG.QUEUE (CMP to CM)
– SYSTEM.BROKER.CONFIG.REPLY (CM to CMP)
– SYSTEM.BROKER.ADMIN.QUEUE (CM to Admin Agent)
– SYSTEM.BROKER.ADMIN.REPLY (Admin Agent to CM)
– SYSTEM.BROKER.EXECUTIONGROUP.QUEUE (Admin Agent to EG)
– SYSTEM.BROKER.EXECUTIONGROUP.REPLY (EG to Admin Agent)
Back to top
View user's profile Send private message
cvag
PostPosted: Tue Aug 11, 2009 4:56 am    Post subject: Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

I think the flows are deployed properly.. as per your statement the Queue depth is not '0' the queue depth is increasing on input queue how many times i put the message.
Back to top
View user's profile Send private message
cvag
PostPosted: Tue Aug 11, 2009 4:57 am    Post subject: Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

Sorry forgot to mention in the above statments .. Broker version is 5.0
Back to top
View user's profile Send private message
zpat
PostPosted: Tue Aug 11, 2009 5:00 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Don't confuse the queue input open count with the queue message depth.
Back to top
View user's profile Send private message
cvag
PostPosted: Tue Aug 11, 2009 5:03 am    Post subject: Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

SYSTEM.BROKER.CONFIG.QUEUE Queuedepth is 1
SYSTEM.BROKER.CONFIG.REPLY Queuedepth is 0
SYSTEM.BROKER.ADMIN.QUEUE Queuedepth is 1
SYSTEM.BROKER.ADMIN.REPLY Queuedepth is 0
SYSTEM.BROKER.EXECUTIONGROUP.QUEUE Queuedepth is 0
SYSTEM.BROKER.EXECUTIONGROUP.REPLY Queuedepth is 0

As the messages are not more in the queue, do i need to empty the queue having queuedepth 1 also.

Please suggest.
Back to top
View user's profile Send private message
cvag
PostPosted: Tue Aug 11, 2009 5:13 am    Post subject: Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

Thanks zpat i got your point..
Sorry for making confusion..

OpenInputCount is 0 for the input queue.

Any suggestion pls..
Back to top
View user's profile Send private message
smdavies99
PostPosted: Tue Aug 11, 2009 5:51 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Are there any Broker errors being reported in the System Event Log?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
cvag
PostPosted: Tue Aug 11, 2009 5:56 am    Post subject: Reply with quote

Centurion

Joined: 17 Mar 2008
Posts: 127

yes that was the strange, i did not get any errors at Broker Event log and event viewer as well.

And now i'm getting the error while disconnecting and connecting to the domain and also while refreshing the execution group

Error: PubSubTopology information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'p14149@myer' does not have authority to view the object. (UUID='PubSubTopology', required attribute='name')

But the user is added in all the groups mqm and brk groups.

Any suggestions pls.
Back to top
View user's profile Send private message
Bravo
PostPosted: Tue Aug 11, 2009 12:10 pm    Post subject: Reply with quote

Centurion

Joined: 03 Oct 2005
Posts: 146

Check ConfigMgr DB CBROKER where CSECTION='DPLING' ..

if it returns value of 1 then try to remove and redeploy the msgflow

Be careful..your using out of support product WBIMB 5.0
_________________
Bravo
Back to top
View user's profile Send private message
mqjeff
PostPosted: Tue Aug 11, 2009 12:27 pm    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

Please ignore most of Bravo's advice, it appears to be fairly irrelevant.

The one piece that is important is that you are indeed using an out of support version of the product, and so unless you have extended maintenance you can not open a PMR.

The error you have posted indicates that your ConfigMgr may not be running. Have you confirmed that it is? Have you confirmed that you have supplied the correct infomration in the Connection document to connect to the proper queue manager for the ConfigMgr?

Have you confirmed that the ConfigMgr has not lost it's connection to the security domain, by examining in detail all of the messages in the system log on the machine hosting the ConfigMgr? Have you attempted to restart the ConfigMgr?

Have you confirmed that you have added the specific user 'p14149@pmyer' to the proper mqm and mqbrkrs groups on the ConfigMgr machine? Have you confirmed that you have performed any other necessary steps to grant access control to that user on the ConfigMgr?
Back to top
View user's profile Send private message
Bravo
PostPosted: Tue Aug 11, 2009 12:55 pm    Post subject: Reply with quote

Centurion

Joined: 03 Oct 2005
Posts: 146

mqjeff we had similar kind of issue while back and I removed entry from the table that resolved issue.

Lets cvag check whether an entry exists in the table and its upto cvag to proceed what to do next.
_________________
Bravo
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message flows are not responding to commands.
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.