| Author |
Message
|
| hongabonga |
 Posted: Tue Feb 15, 2011 5:25 am Post subject: Problem with debug in WMB toolkit 7 |
 |
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
Hi friends,
I am having this issue with Message Broker 7 Toolkit. Whenever I try to start the debug, it shows the following error message.
| Quote: |
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 Ankur-PC:44444 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 Ankur-PC 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 44444 on Ankur-PC 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 tried changing the port, and I could change it. But the result is the same.
Please help.
Many thanks in advance.
Ankur Chakraborty |
|
| Back to top |
|
 |
| Esa |
| Posted: Tue Feb 15, 2011 5:52 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Feb 15, 2011 6:09 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Did you assign the debug port to the EG and restart the EG?
Does netstat -an | find /i "listen" show that the debug port is in LISTENING mode? |
|
| Back to top |
|
|
| hongabonga |
| Posted: Tue Feb 15, 2011 10:13 pm Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
@Esa
Yes, I am using 32 bit windows 7.
@mqjeff
I have assigned the debug port from Broker Explorer and restarted the EG.
However, I haven't tried the netstat yet. I will this afternoon and will get back to you. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue Feb 15, 2011 11:55 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| If your workspace is in the default place under C:\Users, you will get all kinds of problems in Windows 7. Create it somewhere else, for example C:\ws. I am not sure it will help with your debugging problem, but I would try this first. |
|
| Back to top |
|
|
| hongabonga |
| Posted: Wed Feb 16, 2011 12:12 am Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
@Esa
Yes, my workspace is the default one. Let me check this by changing the workspace this evening and I will get back with the results. |
|
| Back to top |
|
|
| hongabonga |
| Posted: Wed Feb 16, 2011 5:48 am Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
@Esa
Changed the workspace, didn't help.
@mqjeff
When I start the debug, the netstat command is giving this output.
| Code: |
C:\Users\Ankur>netstat -an | find /i "44444"
TCP 1.39.222.14:49939 1.39.222.14:44444 SYN_SENT |
And then, throws the error message that I showed before. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 16, 2011 6:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Please confirm that 44444 is not listed in
| Code: |
| netstat -an|find /i "listen" |
When you are NOT trying to connect to it.
If all you see is the SYN-SENT, then someone else is using the debug port, or any of the other causes for the error are occurring. |
|
| Back to top |
|
|
| hongabonga |
| Posted: Wed Feb 16, 2011 7:04 am Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
It is listed this way(6th from top):
| Code: |
C:\Users\Ankur>netstat -an|find /i "listen"
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1414 0.0.0.0:0 LISTENING
TCP 0.0.0.0:8001 0.0.0.0:0 LISTENING
TCP 0.0.0.0:12215 0.0.0.0:0 LISTENING
TCP 0.0.0.0:44444 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING
TCP 0.0.0.0:55446 0.0.0.0:0 LISTENING
TCP 0.0.0.0:60001 0.0.0.0:0 LISTENING
TCP 1.39.222.14:139 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6500 0.0.0.0:0 LISTENING
TCP 127.0.0.1:6501 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING
TCP [::]:445 [::]:0 LISTENING
TCP [::]:1414 [::]:0 LISTENING
TCP [::]:8001 [::]:0 LISTENING
TCP [::]:49152 [::]:0 LISTENING
TCP [::]:49153 [::]:0 LISTENING
TCP [::]:49154 [::]:0 LISTENING
TCP [::]:49155 [::]:0 LISTENING
TCP [::]:49156 [::]:0 LISTENING
TCP [::]:55446 [::]:0 LISTENING
TCP [::]:60001 [::]:0 LISTENING
C:\Users\Ankur> |
|
|
| Back to top |
|
|
| hongabonga |
| Posted: Wed Feb 16, 2011 7:14 am Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
Hi Friends,
Just found the solution here:
https://www.ibm.com/developerworks/forums/thread.jspa?messageID=14460054
In short, the debugger can not work while connected to the internet. I was connected to the internet for all the previous occurances.
Now, I disconnected the connection and it works.
However, this does raise a question; is it somehow possible to debug while connected to the internet?
Thanks a lot for all the help friends. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 16, 2011 7:21 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
So what you mean is your Toolkit was running on a machine that was not on the same network as the Broker machine, and that you couldn't connect because of that.
"Connected to the internet" doesn't mean anything. |
|
| Back to top |
|
|
| hongabonga |
| Posted: Wed Feb 16, 2011 10:25 am Post subject: |
|
|
Novice
Joined: 15 Feb 2011
Posts: 24
|
Hmm. I think that this is an installation issue then.
Probably while installing, I did not configure things correctly.
I am running toolkit and broker on the same machine.
Perhaps, because I am new to WMB, I am not able to express myself correctly.
What I figured that, if I connect to the internet, and try to start the debug, it does not work. However, if I am not connect to the internet(network), I am able to debug. That is the observation.
It might act this way, because my IP changes as I connect to the network, right? |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Feb 16, 2011 10:28 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| hongabonga wrote: |
| It might act this way, because my IP changes as I connect to the network, right? |
Only if you are trying to use the wrong IP address.
Or if the local firewall doesn't let you connect from that IP to the IP that the debugger is running on (which may or may not be the same one). |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Feb 16, 2011 10:30 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| hongabonga wrote: |
| It might act this way, because my IP changes as I connect to the network, right? |
No. Why would it? 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Feb 16, 2011 10:33 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
You may be dual-homing, which is why it works one way and not the other.
Two ways to solve this: In Windows, go to Start -> Settings -> Control Panel -> Network Connections -> and ensure that your local area network conx gets the traffic destined to 1.39.222.14 .
Other way is (if your runtime is running on your local box) specify 127.0.0.1 as the IP addr rather than 1.39.222.14 .
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
|
|
