| Author |
Message
|
| waugh |
 Posted: Wed Mar 24, 2004 3:21 pm Post subject: WBIMB - DEBUG from client failed. |
 |
|
Master
Joined: 19 Feb 2004
Posts: 225
|
when i try to debug a flow on server from my development machine getting following error...
client is
cannot communicate with flow engine
Reason: Agent is inactive.
any idea?
I have my agent controller running. This is what i found in service log on server
"connected to client failed with error major=53 minor=10060" |
|
| Back to top |
|
 |
| waugh |
| Posted: Wed Mar 24, 2004 3:27 pm Post subject: nothing in client's service log... |
|
|
Master
Joined: 19 Feb 2004
Posts: 225
|
| just want to confirm nothing in client service log and i am able to debug the flow deployed on development machine. |
|
| Back to top |
|
|
| djohnsson |
| Posted: Wed Feb 01, 2006 3:01 pm Post subject: Have you found a resolution |
|
|
Newbie
Joined: 01 Feb 2006
Posts: 8
|
Hi,
I am getting exactly the same error. Did you end up finding a resolution?
Thanks |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 01, 2006 3:35 pm Post subject: Re: WBIMB - DEBUG from client failed. |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| waugh wrote: |
cannot communicate with flow engine
Reason: Agent is inactive.
|
Your reason is there. Make sure the rational agent is started on the target/source machine. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| JT |
| Posted: Wed Feb 01, 2006 4:08 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Have you reviewed the contents of the Agent Controlller log for details? |
|
| Back to top |
|
|
| selfown |
| Posted: Fri Feb 03, 2006 3:59 am Post subject: |
|
|
Apprentice
Joined: 07 Jan 2005
Posts: 39
|
| What are the platforms for the broker and the toolkit? |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Feb 03, 2006 4:17 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Was it working before?
Did you recently apply a CSD to the broker? You might need to upgrade RAC
_________________
-wayne |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Tue Feb 07, 2006 12:38 pm Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
One of our developpers can able to debug all execution groups,But only one execution group throwing the same exception,
Cannot communicate with flow engine
Reason:
Agent is inactive
Contact your IBM Support center
Bouncing the services or server did not help for that single execution group.
I deployed the same bar to a new execution group on a different broker(different environmnet) and still getting same exception.
All our brokers are at CSD4 and latest Agent(RAC).
Now what to say, debugger is working or not working? We have a problem with only one flow. Might be a debug has some limitations(can't debug xxx flows).
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| wschutz |
| Posted: Tue Feb 07, 2006 12:48 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Does "exactly the same error" mean you are getting this:
| Quote: |
I have my agent controller running. This is what i found in service log on server
"connected to client failed with error major=53 minor=10060" |
| Quote: |
| ETIMEDOUT (10060): The establishment of a connection timed out before a connection was made |
So the obviou question is, is there anything different about the one flow that you can't debug? (ie, using a custom plug-in? uses different odbc connect ... etc)
_________________
-wayne |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Wed Feb 08, 2006 11:38 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
We are getting the same pop-up windows message only. I did not see any errors in the service log(RAC/config/servicelog.log)
I attached good one(EG1) and bad one(badone) to the debugger. Both getting exact same information under the log.
Incoming connection request from agent HIGMQIL1:EG1 in process 4116 with uuid 3e7dfe1f-9c78-4ec0-ab27-b762226db1dc"/>
<SERVER_MSG time="2006:2:8:14:4:54" severity="WARNING" text="Registered Agent 3e7dfe1f-9c78-4ec0-ab27-b762226db1dc."/>
Incoming connection request from agent HIGMQIL1:badone in process 2528 with uuid 2fab1424-30e1-42e6-bad2-9fd8a0f6af0e"/>
<SERVER_MSG time="2006:2:8:14:4:54" severity="WARNING" text="Registered Agent 2fab1424-30e1-42e6-bad2-9fd8a0f6af0e."/>
We are not using any plugin. Looks like it's a very big flow(bunch of sql files).
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| JT |
| Posted: Wed Feb 08, 2006 12:28 pm Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
| Looks like it's a very big flow(bunch of sql files). |
Perhaps increasing the JVM size for the workbench ?
| Code: |
| mqsistudio.exe -vmargs -Xms512mb -Xmx800mb |
|
|
| Back to top |
|
|
| venkat kurra |
| Posted: Fri Feb 10, 2006 9:04 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
JT,
We are using 512mb for the Studio,
C:\Programs\WBIMB\eclipse\mqsistudio.exe -vmargs -Xmx512m -Xms512m
Some readon the toolkit does not allow Xms800 value(JVM terminated Exit code=1 and i could not open the toolkit at all).
Also we set MQSIJVERBOSE to Xmx512Mb on the Broker(/RAC) server.
Finally i sent every thing to IBM. I let you know if we find any thing.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| venkat kurra |
| Posted: Thu Mar 23, 2006 10:57 am Post subject: |
|
|
Master
Joined: 18 Oct 2001
Posts: 245
Location: Bloomington , IL
|
IBM still working on this problem. Looks like the developper worked little hard to create this problem.
Good news is we can debug after we close (or Click "ok") the pop-up window.
_________________
Thanks,
Venkat Kurra
IBM Certified Specialist-MQSeries
IBM Websphere MQSeries Administrator
IBM WebSphere Message Broker System Admin |
|
| Back to top |
|
|
| dsriksha |
| Posted: Tue May 09, 2006 7:23 am Post subject: |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
| venkat kurra wrote: |
IBM still working on this problem. Looks like the developper worked little hard to create this problem.
. |
Did you get any solution from IBM. 
It seems to be I also worked hard  |
|
| Back to top |
|
|
| dsriksha |
| Posted: Tue May 09, 2006 11:28 am Post subject: |
|
|
Voyager
Joined: 27 Feb 2005
Posts: 95
|
Hi :
my strong sense (other than those 6 senses) saying that it might be a Firewall problem.  |
|
| Back to top |
|
|
|
|
