| Author |
Message
|
| mustang |
 Posted: Wed Oct 24, 2007 7:57 am Post subject: WMB Toolkit debugger |
 |
|
Acolyte
Joined: 07 Feb 2006
Posts: 72
|
We use WMB 6.
I receive an "Unable to install breakpoint in .... due to missing line number attributes. Modify compiler options to generate line number attributes" error when trying to launch the WMB Toolkit's debugger.
It is for a jar file with classes accessed by a JavaCompute node. The jar file is built using ANT with the debug="true" and debuglevel="lines,vars,source" parameters. When I open the offending class file in a decompiler, it displays the line numbers (which it won't do if the class files are compiled without line numbers).
In addition, I receive the same error when I replace the jar file generated by ANT with a jar file generated by the toolkit in the same workspace. This jar file was generated using the eclipse setting "Add source file name to generated class file (used by the debugger)" setting checked. I also verified that the line numbers were set by viewing the class file in a decompiler.
Any reason why the toolkit's debugger keeps giving me this message? I would really love to set breakpoints in the source that generates this jar file.
Thanks! |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Oct 24, 2007 8:11 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Are you sure the jar file is generated with the right version of Java.? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mustang |
| Posted: Thu Oct 25, 2007 4:47 am Post subject: |
|
|
Acolyte
Joined: 07 Feb 2006
Posts: 72
|
| No, I am not sure. When I built it using ANT, the compiler was from j2sdk1.4.2_11. When I built it using the WMB Toolkit, the compiler was compiler compliance 1.4. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 25, 2007 4:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Well, that should be close enough.
You did all the necessary things to enable Java debugging on the broker runtime - enabled the debugger port, and etc?
Is this a JAR file that's being deployed in a BAR, or through some other means?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| mustang |
| Posted: Thu Oct 25, 2007 5:36 am Post subject: |
|
|
Acolyte
Joined: 07 Feb 2006
Posts: 72
|
Yes, I believe I did all the necessary things to enable Java debugging on the broker runtime, including enabling the debugger port. The debugger does step into the JavaCompute node. It even steps into the code in the jar file. It just won't recognize the breakpoints in the jar file source.
It is a jar file being deployed in a BAR. The BAR is built using the WMB Toolkit. I have built the jar using both ANT and the WMB Toolkit, both with the necessary parameters needed to enable line numbers.
Thanks! |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Oct 25, 2007 5:38 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Is it possible you have a phantom EG, and the debugger is connecting to that?
Compare what you see in mqsilist BROKERNAME to what you see in the Toolkit. Compare what you see in mqsilist BROKERNAME to the number of DataFlowEngine processes you see.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
