|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
The flow engine has been attached to another debug session |
« View previous topic :: View next topic » |
Author |
Message
|
machinist |
Posted: Mon May 30, 2016 3:03 am Post subject: The flow engine has been attached to another debug session |
|
|
 Novice
Joined: 17 Feb 2016 Posts: 15 Location: India
|
The flow engine has been attached to another debug session, or
The flow engine is not listening on the specified port, or
The Broker is not running, or
Timeout occurred while connecting
Resolution:
Assign a different debug port to the flow engine and restart the Broker, and
Ensure the flow engine is running and listening on the specified port, and
Ensure the broker is running or
Increase the timeout setting in the Preference page
Attach to server at KBHUJBAL-IN:54856 failed.
Connection could not be established.
This can occur for one or more of these reasons:
The host name and/or port are incorrect.
The server on KBHUJBAL-IN is not started in debug mode.
Communication timeouts in the Debug preferences (under the Java node in the Preferences dialog box) are not long enough.
The state of port 54856 on KBHUJBAL-IN must be LISTENING. If the state of the port is ESTABLISHED, then another debug session is already connected to the port.
The "netstat" command line tool can be used to determine port status.
A firewall is interfering with the connection.
Ensure that these settings are properly made before attempting to attach to the server.
I am getting above error while launching debugger,i tried all the ways like deleting execution group,broker,restarting using new port still same error can anyone help me out? |
|
Back to top |
|
 |
anurag.munjal |
Posted: Mon May 30, 2016 3:20 am Post subject: rerunning the debuggeer fixed it! |
|
|
 Voyager
Joined: 08 Apr 2012 Posts: 97
|
Hi, i faced the exact same issue today in my tolkit v8.
i just tried rerunning the debugger, and it worked!! Stil not sure why this error came in.. but its no no more coming!
 _________________ - Anurag
------------------------
Be Simple, Be Happy |
|
Back to top |
|
 |
ruimadaleno |
Posted: Tue May 31, 2016 7:29 am Post subject: |
|
|
Master
Joined: 08 May 2014 Posts: 274
|
some time ago we hit a situation where two developer in two distinct buildings where unable to debug message flows.
They were running broker toolkit in virtual machines (vmware). One of the developer copy the virtual machine from the other and just happily turn it on and start using it.
In the end of the day we had two virtual machines with the same ip trying to debug message flows ..................
Check no one else is trying to hook up to debug port  _________________ Best regards
Rui Madaleno |
|
Back to top |
|
 |
kiantonator |
Posted: Wed Jan 08, 2020 8:40 pm Post subject: |
|
|
 Newbie
Joined: 08 Jan 2020 Posts: 5
|
I am using websphere MQ 6.1 and I am facing similar issue, not sure what to check and how to resolve it? Any ideas guys ? |
|
Back to top |
|
 |
fjb_saper |
Posted: Thu Jan 09, 2020 5:53 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
kiantonator wrote: |
I am using websphere MQ 6.1 and I am facing similar issue, not sure what to check and how to resolve it? Any ideas guys ? |
I don't remember there having been an MQ 6.1, but I do remember WMB 6.1 which I believe you are talking about.
However this version is so antiquated I would strongly urge you to go to IIB 10.0.0.19 or (if you're on the more adventurous side) ACE 11 (latest ).  _________________ MQ & Broker admin |
|
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
|
|
|
|