| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| is IBM RAC required for debugging message flows in MB V6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| raj429 |
 Posted: Thu Apr 22, 2010 6:04 pm Post subject: is IBM RAC required for debugging message flows in MB V6.1 |
 |
|
Acolyte
Joined: 04 Jul 2009
Posts: 53
|
|
| Back to top |
|
 |
| PeterPotkay |
| Posted: Thu Apr 22, 2010 7:23 pm Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
You should look in the WMB 6.1 Info center for questions related to WMB 6.1
You provided a link to an entry in the WB-IMB 5.0 Infocenter?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| mqmatt |
| Posted: Fri Apr 23, 2010 2:07 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
| No. As of V6.1 Rational Agent Controller isn't used. |
|
| Back to top |
|
|
| raj429 |
| Posted: Fri Apr 23, 2010 7:32 am Post subject: |
|
|
Acolyte
Joined: 04 Jul 2009
Posts: 53
|
Thanks for the reply,,
I am able start my debugging...Thought these stpes may be helpful to others on par with me.
Any corrections all welcome..
1) Enable debug port on the EG if its not been set already.
Switch to BA perspective, right click on EG--> properties-->JVM debug port-->set any port that is available
It should refresh, and debugging option should be enabled on EG. To check this, right click-->debug->should be set to enable(portnumber)
2) if not, right click on EG and then enable debug option on the EG. It will prompt for restart of the EG
3) if not, stop and start EG using command mode.
4) Now switch to BD perspecive,debug-->message broker debug-->new configuration--> set port @ EG was listening--> select EG-->debug
5) Here, it will try to connect to JVM for bebug perpective,
If you see a prompt here, then check for any of the below options..
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 in abend state, or
Timeout occurred when connecting
Resolution:
Assign a debug port to the flow engine and restart the Broker, and
netstat -a -b -p TCP
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
perpective-->window-->preferences-->message broker debug-->timeout(in millin sec)+ increase this value
if you dont see, the dataflowengine at the defined port, then try below it worked for me.
mqsichangeproperties <message broker instance name> -e <execution group name> -o ComIbmJVMManager -n jvmDebugPort -v <debug port> --> this commands change the port to what you want it to be
Restart the broker
again check netstat -a -b -p tcp..Once you see flowengine at port
you will be able to attach EG to debug |
|
| 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
|
|
|
|
