| Author |
Message
|
| DTechBuddy |
 Posted: Tue Mar 27, 2012 1:02 pm Post subject: WMB 6.1 debugging message flows |
 |
|
Novice
Joined: 05 May 2009
Posts: 20
|
Hello All,
I am trying to debug a message flow in WMB 6.1 and got stuck with the below error. I have enable the port on my execution group thru toolkit as well as command.
i ran netstat command which had a positive output of LISTEN on that port.
i restarted broker.
Any help would be appreciated
----------------------error------------------------------------------------
!ENTRY com.ibm.etools.mft.debug 4 8 2012-03-27 16:48:31.946
!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 in abend state, or
Timeout occurred while connecting
Resolution:
Assign a debug port to the flow engine and restart the Broker, and
Make sure that the Broker is not in the abend state, and
Make sure that the Flow engine had started successfully or
Increase the timeout setting in the Preference page
!STACK 0
java.lang.RuntimeException: The XSLT debugger failed to find a port to listen on.
at com.ibm.debug.xdi.impl.XDIListeningConnectorImpl.startListening(Unknown Source)
at com.ibm.debug.xsl.internal.core.XSLDebugTarget.startListening(Unknown Source)
at com.ibm.debug.wsa.internal.core.WSAJavaDebugTarget.setupJavaDebugTargetElements(Unknown Source)
at com.ibm.debug.wsa.internal.core.WSAJavaDebugTarget.createWSAJavaDebugTarget(Unknown Source)
at com.ibm.debug.wsa.WSADebugPlugin.createWSADebugTarget(Unknown Source)
at com.ibm.etools.mft.debug.internal.MBLaunchConfigurationDelegate.wsalaunch(Unknown Source)
at com.ibm.etools.mft.debug.internal.MBLaunchConfigurationDelegate.launch(Unknown Source)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Unknown Source)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(Unknown Source)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(Unknown Source)
at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(Unknown Source)
at org.eclipse.core.internal.jobs.Worker.run(Unknown Source) |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Tue Mar 27, 2012 1:08 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
WMB version numbers have 4 digits, not 2. What version are you using? Also, you cannot use toolkits from different versions. If your runtime is 6.1.0.1 then your toolkit must also be similar to use the debugger.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| DTechBuddy |
| Posted: Tue Mar 27, 2012 1:25 pm Post subject: |
|
|
Novice
Joined: 05 May 2009
Posts: 20
|
Thank you so much for the reply...
my tollkit version installed on windows 7 machine is
Version: 6.1.0
Build id: 6.1.0-20071108_1112
Also, i am trying to connect to a remote broker installed on AIX machine with version
MQSI 6.1.0.8 |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Tue Mar 27, 2012 1:34 pm Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Looks like your toolkit is out of date. Also, there are many fixes, including debugger fixes at the runtime level 6.1.0.10. Update both and try again.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 27, 2012 1:57 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DTechBuddy wrote: |
my tollkit version installed on windows 7 machine is
Version: 6.1.0
Build id: 6.1.0-20071108_1112 |
The WMBv6.1 Toolkit is not supported on Winv7. Using it on that platform sort of works, but weirdness can result.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Mar 28, 2012 1:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Vitor wrote: |
| DTechBuddy wrote: |
my tollkit version installed on windows 7 machine is
Version: 6.1.0
Build id: 6.1.0-20071108_1112 |
The WMBv6.1 Toolkit is not supported on Winv7. Using it on that platform sort of works, but weirdness can result. |
The runtime 6.1 is not supported on Win7 either. If the debugger is having issues, it's likely not just Toolkit level weirdness. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Mar 28, 2012 4:33 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| mqjeff wrote: |
| Vitor wrote: |
| DTechBuddy wrote: |
my tollkit version installed on windows 7 machine is
Version: 6.1.0
Build id: 6.1.0-20071108_1112 |
The WMBv6.1 Toolkit is not supported on Winv7. Using it on that platform sort of works, but weirdness can result. |
The runtime 6.1 is not supported on Win7 either. If the debugger is having issues, it's likely not just Toolkit level weirdness. |
Very good point.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| DTechBuddy |
| Posted: Wed Mar 28, 2012 5:06 am Post subject: |
|
|
Novice
Joined: 05 May 2009
Posts: 20
|
| Thank you so much all for your help..... |
|
| Back to top |
|
|
| DTechBuddy |
| Posted: Thu Mar 29, 2012 6:44 am Post subject: |
|
|
Novice
Joined: 05 May 2009
Posts: 20
|
Hello,
I upgraged my toolkit version to 6.1.0.10
when i try to debug any flow. progress bar shouw connection to JVM and hangs there without any progress ahead.
Am i missing any thing else.
I know i am using Windows 7 and behavoiur can be wierd.
Is this something related to windows 7?
Thank you all. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Thu Mar 29, 2012 6:55 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| DTechBuddy |
| Posted: Thu Mar 29, 2012 7:06 am Post subject: |
|
|
Novice
Joined: 05 May 2009
Posts: 20
|
|
| Back to top |
|
|
| Vitor |
| Posted: Thu Mar 29, 2012 7:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| DTechBuddy wrote: |
| Have i missed any thing |
You've missed the upgrade to the runtime. Installation Manager only handles the Toolkit.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 29, 2012 7:18 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The only versions of Broker that can be expected to work reliably on Windows 7 are Version 7.0.0.x and 8.0.0.x.
No version of Broker v6.1.0.x will function on Windows 7 reliably and supportably.
This applies to both the runtime and the toolkit. |
|
| Back to top |
|
|
| DTechBuddy |
| Posted: Thu Mar 29, 2012 7:25 am Post subject: |
|
|
Novice
Joined: 05 May 2009
Posts: 20
|
| Quote: |
| You've missed the upgrade to the runtime. Installation Manager only handles the Toolkit. |
My runtime will be installed on my AIX server hosted in my datacenter.
i need to upgrade it to version 6.1.0.10? i am accessing my broker remotely.
| Code: |
| The only versions of Broker that can be expected to work reliably on Windows 7 are Version 7.0.0.x and 8.0.0.x. |
can i upgrade my broker to 7.0.0.x from 6.1.0.8
what are the step involved?
i know this is something big to ask for....
any help would be appreciated.
thank you all.[/quote] |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu Mar 29, 2012 7:29 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You can upgrade to 7.0.0.x.
There is plenty of documentation on how to do this in the v7 information center.
But if the runtime is on AIX, then you don't *need* to upgrade it.
If you want to use version 6.1 of broker, then you *must* use 6.1 Toolkit, and you *cannot* run Toolkit 6.1 on Windows 7.
So you have a choice. You can either use Broker v7, or a supported version of Windows for Toolkit 6.1.
Last edited by mqjeff on Thu Mar 29, 2012 7:31 am; edited 1 time in total |
|
| Back to top |
|
|
|
|
