| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Why my excute group is auto connected to debug mode??? |
« View previous topic :: View next topic » |
| Author |
Message
|
| iamfat |
 Posted: Sun Apr 22, 2012 11:05 pm Post subject: Why my excute group is auto connected to debug mode??? |
 |
|
Apprentice
Joined: 08 Mar 2012
Posts: 32
Location: China
|
I only start the Explorer , and no other Broker Toolkit running on my computer. But after i set the debug port and restart the execution group, the group will change to debug mode automatically.
And my toolkit cant' connect to the broker any more, it'll stuck at the connection to the JVM... and it'll show these messages.
-----------------------
Can not communicate with the flow engine.
Reason:
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
------------------
I'm confused... what should i do..
And the icon of execution group is showed as a green bug at the right corner of the bottom.
Also some error message.
=====================================
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 AB6718:9911 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 AB6718is 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 9911 on AB6718must 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.
========================================= |
|
| Back to top |
|
 |
| iamfat |
| Posted: Mon Apr 23, 2012 12:51 am Post subject: |
|
|
Apprentice
Joined: 08 Mar 2012
Posts: 32
Location: China
|
I decide to reinstall the whole suite.
And install some fixed patch.
God bless , it 'll be ok.  |
|
| Back to top |
|
|
| iamfat |
| Posted: Mon Apr 23, 2012 6:03 pm Post subject: |
|
|
Apprentice
Joined: 08 Mar 2012
Posts: 32
Location: China
|
| iamfat wrote: |
I decide to reinstall the whole suite.
And install some fixed patch.
God bless , it 'll be ok. |
After i reinstall the whole broker, it's working fine now.
Maybe i installed the wrong patch, and the version is not match.
 |
|
| 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
|
|
|
|
