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 » Debugging session with error messages

Post new topic  Reply to topic
 Debugging session with error messages « View previous topic :: View next topic » 
Author Message
svu
PostPosted: Thu Apr 20, 2006 3:03 am    Post subject: Debugging session with error messages Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

Hi all

Trying to debug the messages in WSMB Toolkit (version 5), I am constantly getting series of error messages after GUI is attached to the broker. The messages say:

Cannot communicate with flow engine.
Agent is inactive.
Contact your IBM support center.

After 3 messages, debugging works ok. But it is annoying a bit:)

What could this be?
Back to top
View user's profile Send private message
sirsi
PostPosted: Thu Apr 20, 2006 10:55 am    Post subject: Reply with quote

Disciple

Joined: 11 Mar 2005
Posts: 177

Which CSD have u applied?

always start the Agent controller first and then the broker

this might help you:-

http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.etools.mft.doc/au16610_.htm
Back to top
View user's profile Send private message
wbibrk
PostPosted: Thu Apr 20, 2006 12:41 pm    Post subject: Reply with quote

Apprentice

Joined: 09 Jul 2005
Posts: 46

The Agent is inactive message typically means that the DFE is not available for RAC to connect to. Make sure you start RAC first and then the broker and then attach to the DFE
Back to top
View user's profile Send private message Send e-mail
svu
PostPosted: Fri Apr 21, 2006 12:15 am    Post subject: Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

I don't really know how to check it. IIRC it is CSD07.

The article asks to check whether Agent Controller is running - but I know for a fact it is (according to the MS Windows "Services" management panel). That was the first thing I actually checked;)
Back to top
View user's profile Send private message
svu
PostPosted: Fri Apr 21, 2006 12:17 am    Post subject: Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

wbibrk wrote:
The Agent is inactive message typically means that the DFE is not available for RAC to connect to. Make sure you start RAC first and then the broker and then attach to the DFE


RAC is started (I am not sure whether it was started first since the services start automatically - and I do not know how to add dependencies manually.
Back to top
View user's profile Send private message
JT
PostPosted: Fri Apr 21, 2006 5:35 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Quote:
I don't really know how to check it. IIRC it is CSD07.

Issue the mqsiservice -v command or view the memo.ptf file

Quote:
RAC is started (I am not sure whether it was started first since the services start automatically

There's a RAC log file (servicelog.log) that details what EGs have been registered & when they were connected.

Quote:
I do not know how to add dependencies manually.

Issuing an mqsireload of the execution group will cause it to re-atached to the Agent Controller
Back to top
View user's profile Send private message
svu
PostPosted: Fri Apr 21, 2006 5:47 am    Post subject: Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

JT wrote:

Issue the mqsiservice -v command or view the memo.ptf file

OK, then it is really CSD07, from memo.ptf

JT wrote:
There's a RAC log file (servicelog.log) that details what EGs have been registered & when they were connected.

There are no errors in this file - it just registers broker and other services (and the latest records are about today). What should I look specifically for?

JT wrote:
Issuing an mqsireload of the execution group will cause it to re-atached to the Agent Controller

It works ok - but no changes (except for new rows in servicelog.log)
Back to top
View user's profile Send private message
JT
PostPosted: Fri Apr 21, 2006 5:52 am    Post subject: Reply with quote

Padawan

Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.

Quote:
What should I look specifically for?

You should verify that the EG where you msgflow resides has been registered (no errors) to the Controller. If the EG is registered properly, then I would restart your toolkit.
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Fri Apr 21, 2006 5:53 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

Am I not following what's being discussed, or is the actual issue that debugging works, but it complains first?
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
svu
PostPosted: Fri Apr 21, 2006 6:06 am    Post subject: Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

jefflowrey wrote:
Am I not following what's being discussed, or is the actual issue that debugging works, but it complains first?

Yes. It complaints (3 times) on attaching, and also it complains (2 times) on detaching. Between these events it generally works.
Back to top
View user's profile Send private message
svu
PostPosted: Fri Apr 21, 2006 6:09 am    Post subject: Reply with quote

Voyager

Joined: 30 Jan 2006
Posts: 99

JT wrote:
Quote:
What should I look specifically for?

You should verify that the EG where you msgflow resides has been registered (no errors) to the Controller. If the EG is registered properly, then I would restart your toolkit.

Well, I see a lot of messages like:
<SERVER_MSG time="2006:4:21:9:33:50" severity="WARNING" text="Incoming connection request from agent TBROKER:default in process 3892 with uuid e2b61a3e-b94e-4bac-b4f8-9f2d01ae4a7f"/>
<SERVER_MSG time="2006:4:21:9:33:50" severity="WARNING" text="Registered Agent e2b61a3e-b94e-4bac-b4f8-9f2d01ae4a7f."/>

The broker name is TBROKER, the EG is default. No errors - so I presume it is ok. And I restarted the toolkit many many times since this annoying thing started to happen...
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 » Debugging session with error messages
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.