MQSeries.net :: View topic - How do I debug a plugin node implemented in Java language ?

MQSeries.net

Tech Exchange

Education

Certifications

Library

Info Center

SupportPacs

FAQÂ Â

Usergroups

RSS Feed - WebSphere MQ Support

RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How do I debug a plugin node implemented in Java language ?

How do I debug a plugin node implemented in Java language ?

« View previous topic :: View next topic »

Author

Message

Miko

Posted: Wed Mar 06, 2002 6:57 am Post subject:

Newbie

Joined: 05 Mar 2002
Posts: 1

I have written a Java implemented plugin node using WSAD. How do I attach the Java debugger to the JVM of WMQI ? Any ideas welcome.

Coz

Posted: Thu Mar 07, 2002 3:11 am Post subject:

Apprentice

Joined: 20 Feb 2002
Posts: 44
Location: Basel CH

Assuming that you are testing on NT (or other MS desktop), the easisest way we found was to allow the broker to interact with desktop via the services window and use lots and lots of 'System.out...' which will appear in one of the windows created by the broker.

Coz

kolban

Posted: Thu Mar 07, 2002 5:57 am Post subject:

Grand Master

Joined: 22 May 2001
Posts: 1072
Location: Fort Worth, TX, USA

Install the latest CSDs for WMQI (CSD 0 & 1). Once installed, read the README file of the product and you will find documentation on using Java debugging ... I will reproduce below:

28. Debugging Java nodes.
It is possible to attach the JDB debugger to the JVM running inside the broker thus
allowing developers to debug their Java nodes. The debugger can be attached on a
per execution group basis. In order to attach JDB you must first change the broker
configuration to tell the JVM to listen on a particular port. The command mqsiservice
can be used to change the broker configuration in the following way:
mqsiservice <broker> -r debugJava="<ExecutionGroup1Label=port1>;<ExecutionGroup2Label=port2> ..."
<broker> - The broker name.
<ExecutionGroup1Label=port1> - This tells the JVM in execution group 1 to listen on port1.
<ExecutionGroup2Label=port2> - This tells the JVM in execution group 2 to listen on port2.
Several entries can be added for each execution group, these are separated by semicolons
as illustrated above. The entry can be removed in the following way:
mqsiservice <broker> -r debugJava
Misusing mqsiservice can seriously damage the broker configuration. It should
only be used in the way described above. This command is not available on 390.
The broker must be restarted for these changes to take effect. The JVM in the
execution group will now listen on the specified port and can be attached to
in the usual manner.

Display posts from previous:

Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » How do I debug a plugin node implemented in Java language ?

Jump to:

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

Protected by Anti-Spam ACP