| Author |
Message
|
| OtisFly |
 Posted: Wed Jan 18, 2006 9:04 am Post subject: Trying to use flow debugger on WBIMB V6 |
 |
|
Novice
Joined: 01 Dec 2005
Posts: 19
Location: London - UK
|
Hello All,
I'm trying to debug a flow with little success. Here's my environment.
Message Brokers toolkit 6.0.0 installed on windows XP
Broker/Configmgr running on solaris (OS 5.9)
Rational Agent Controller 6.0.0.1 on the solaris box
The problem that I have is that although I have breakpoints set in the flow, the input message is processed by the flow without stopping at the first breakpoint.
Security is not enable for the RAC. I've stopped my toolkit, the broker and RAC and then restarted in the order RAC, broker, toolkit.
Looking at the Agent controller log, it seems that a connection is being created:-
<SERVER_MSG time="2006:1:18:17:22:15" severity="INFORMATION" text="Incoming conn
ection request on socket 9 from 0xa800e29"/>
<SERVER_MSG time="2006:1:18:17:22:15" severity="WARNING" text="Notify the client
that we are ready now since security is not enabled"/>
<SERVER_MSG time="2006:1:18:17:22:15" severity="INFORMATION" text="Connection ac
cepted on socket 9"/>
<SERVER_MSG time="2006:1:18:17:22:15" severity="INFORMATION" text="Preparing Age
nt active"/>
<SERVER_MSG time="2006:1:18:17:22:16" severity="WARNING" text="Requesting shared
memory 1048576 bytes, allocating 1048576 bytes, system max 4294967295 bytes"/>
<SERVER_MSG time="2006:1:18:17:22:16" severity="INFORMATION" text="Created data
channel with name rabuffer7 and CB addr 7eb00154 buffer addr 7eb032ec size in=10
48576 size out=1048576"/>
<SERVER_MSG time="2006:1:18:17:22:16" severity="INFORMATION" text="Connected to
client data channel socket on port 2059 with descriptor 10"/>
<SERVER_MSG time="2006:1:18:17:22:16" severity="INFORMATION" text="Created flush
er thread and about to send message to agent"/>
Has anyone got any ideas?
Many Thanks
Otis |
|
| Back to top |
|
 |
| K_A |
| Posted: Fri Jan 20, 2006 4:48 am Post subject: |
|
|
Apprentice
Joined: 10 Nov 2004
Posts: 32
|
Hi
Maybe this is a stupid reply, but I have been in your situation many times and the solution to this problem is often quite trivial, at least has been in my cases.
* You you REALLY have a breakpoint? (At least in rel 5 there was a visuliations bug, so that a bullit was sometimes displayed on the line even if there was no breakpont). Try to take away the breakpoint and add it again.
* Purge the in-queue before you start the flow and the debugger. Then, put on the message.
* Make sure you have no other flows or processes consuming messages from the same in-queue. Stop all other flows and so on. Alternately, change the flow to read a queue that yo're 120% sure is not used elsewhere.
/K_A |
|
| Back to top |
|
|
| ashritha |
| Posted: Wed Jan 25, 2006 10:46 am Post subject: |
|
|
Voyager
Joined: 25 Jul 2005
Posts: 85
|
Hello,
I also had the same problem and tried all the points you mentioned sir, but it doesn't work.
Is there any way around?
Otis, if you have solved this issue, can you please post the solution?
Thanks |
|
| Back to top |
|
|
| OtisFly |
| Posted: Tue Jan 31, 2006 8:16 am Post subject: |
|
|
Novice
Joined: 01 Dec 2005
Posts: 19
Location: London - UK
|
I have been discussing with IBM. Their recommendation is to download fix pack 1 for the toolkit and try again. I'll be doing this tomorrow and I'll report back
Otis |
|
| Back to top |
|
|
| halbster |
| Posted: Tue Feb 21, 2006 6:23 pm Post subject: |
|
|
Newbie
Joined: 08 Feb 2005
Posts: 6
Location: Australia
|
HI there,
We are running Message Broker 6 on AIX, with the toolkit (incl fixpack 1) installed on windows.
We installed the Rational Agent Controller for AIX ver 6.0.0.1 on the AIX server, however the debugger would not stop at the breakpoint specified.
We upgraded the the Agent Controller to fix pack 1 (ver 6.0.1.0) and still encountered the same problem.
The final solution for us was to install the older version of the Agent Controller, ver 5.0.2.1.
Hope this helps. |
|
| Back to top |
|
|
| Paul D |
| Posted: Tue Feb 21, 2006 8:27 pm Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I have this same issue and I'm running with MB v6 with toolkit fix (6.0.0.1 on) and the 5.0.2 Agent Controller and I still get the breakpoint issue. I'm also doing this on Windows at this point. Can you get a 5.0.2.1 version of RAC? It's not on IBM's site that I see. Does 5.0.2 work for anyone, that's what's on IBM's site.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| halbster |
| Posted: Wed Feb 22, 2006 2:31 am Post subject: |
|
|
Newbie
Joined: 08 Feb 2005
Posts: 6
Location: Australia
|
| It was downloaded from the IBM site. It wasn't easy to find. Go to the WBI MB V5.0 downloads. You need to login here. Then there is a section to download the RAC 5.0.2.1. This was the version we required for AIX. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Feb 22, 2006 3:10 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20767
Location: LI,NY
|
We run the broker with Toolkit and RAC in version 6.0 inclusive fixpackson windows for dev.
No problems with debugging on windows. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| rossired |
| Posted: Thu Feb 23, 2006 5:47 am Post subject: |
|
|
Novice
Joined: 22 Feb 2006
Posts: 22
|
| fjb_saper wrote: |
We run the broker with Toolkit and RAC in version 6.0 inclusive fixpackson windows for dev.
No problems with debugging on windows. |
I have a similar problem. I cant debug any flows. In the event log, I get some sort of JNI error: BIP4353 "An error occurred in the JNI layer during flow debugging"
According to this link: http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27007091 (Defect42277), I am supposed to just stop and start the broker, but that doesn't seem to change anything.
Ive reinstalled the Rational Agent Controller ( version 6 ) and the toolkit: Version: 6.0.0.1 Build id: 20060106_1130 )... no difference
Any thoughts on this issue ?
Thanks
Vale |
|
| Back to top |
|
|
| jdlennon |
| Posted: Thu Feb 23, 2006 1:45 pm Post subject: |
|
|
Novice
Joined: 07 Oct 2004
Posts: 19
Location: The Villages, FL
|
Only because I did this by accident will I suggest it. When you go into the debug setup for the message broker - you pick a Flow Project. But - just checking that does not change the actual execution group you may be watching (you need to go and pick the actual execution group it is running in where it asks for Flow Engine further down in the menu). It will have something in there by default that may not be where the particular message flow you want to debug is running. Just a thought. It will run right to end of job if I don't set that properly! If I do set it properly - debug works fine (I have latest maint for the toolkit.) Hope this might help.
_________________
Jill D Lennon |
|
| Back to top |
|
|
| rossired |
| Posted: Thu Feb 23, 2006 1:55 pm Post subject: |
|
|
Novice
Joined: 22 Feb 2006
Posts: 22
|
| jdlennon wrote: |
| Only because I did this by accident will I suggest it. When you go into the debug setup for the message broker - you pick a Flow Project. But - just checking that does not change the actual execution group you may be watching (you need to go and pick the actual execution group it is running in where it asks for Flow Engine further down in the menu). It will have something in there by default that may not be where the particular message flow you want to debug is running. Just a thought. It will run right to end of job if I don't set that properly! If I do set it properly - debug works fine (I have latest maint for the toolkit.) Hope this might help. |
Hi Jill,
Im not sure if you were responding to my "JNI error" bug, but in my case, I only have one exectution group. And I did refresh flow engine in my drop down. Still no good.
Thanks
Vale |
|
| Back to top |
|
|
| Paul D |
| Posted: Fri Feb 24, 2006 9:47 am Post subject: |
|
|
Master
Joined: 16 May 2001
Posts: 200
Location: Green Bay Packer Country
|
I got my v6 flow debugger issues fixed. Here's what I did, hopefully this will help someone that is still having issues. First off, I upgraded my MQ to 6.0, I was previously running 5.3. Hopefully not necessary but I did do it so I'll mention it. Second, I upgraded from RAC 5.0.2 to the must current RAD RAC version (6.0.0.1). Also, when I installed this, I specified the java JRE as the one used for the toolkit (C:\Program Files\IBM\MessageBrokersToolkit\6.0\eclipse\jre\bin). I noticed in the RAC install notes (install.html in RAC 6.0 download root dir) that…
| Quote: |
In general, Agent Controller works with JVM version 1.4 and above. Here are the JVM versions (java -fullversion) that Agent Controller has been tested on:
AIX: J2RE 1.4.1 IBM AIX build ca1411-20040301
HP-UX: J2RE 1.4.2.03-040401-18:59-PA_RISC2.0
Linux IA32: J2RE 1.4.1 IBM build cxia321411-20040301; J2RE 1.4.2 IBM.
Linux for OS/390(R): J2RE 1.4.1 IBM build cx3901411-20040301
z/OS: J2RE 1.4.1 IBM z/OS Persistent Reusable VM build cm1411-20030930
OS/400: J2RE 1.4 IBM
Solaris SPARC: Sun Java(TM) 2 Standard Edition (build 1.4.2_04-b05)
Windows: IA32 J2RE 1.4.1 IBM Windows 32 build cn1411-20040301a; J2RE 1.4.2 IBM Windows 32; Sun Java(TM) 2 Standard Edition (build 1.4.2_04-b05) |
Note that this was also said about the JRE that the RAC uses...
| Quote: |
Specify the path of the Java run-time environment (JRE) executable program java.exe or java which Agent Controller should be using. The JRE entered here will be used by Agent Controller for launching Java applications. Therefore, you may want to change the JRE path pre-filled by the installer program.
Note:
The JRE you provide at this time will be used both to run Agent Controller and for Agent Controller to launch Java applications. You may, however, later configure Agent Controller to a use separate JRE for each of these functions. For details, refer to Agent Controller help topic Configuring Applications to be launched by the Agent Controller. |
It's clearly important to get this at the right version.
I uninstalled the previous RAC version, making sure all files listed in install.html were removed.
With all of this in place, debugging is working very well. I'm doing both regular flow and java debugging in java compute nodes and it's working good. Hope this helps.
_________________
Thanks!!!
Paul D |
|
| Back to top |
|
|
| OtisFly |
| Posted: Tue Feb 28, 2006 8:50 am Post subject: Resolved |
|
|
Novice
Joined: 01 Dec 2005
Posts: 19
Location: London - UK
|
| I have installed the latest interim fix to the toolkit (having installed fixpack 1 for the toolkit) and the debugger is now working. |
|
| Back to top |
|
|
|
|
