Author |
Message
|
FMER |
Posted: Wed Jan 09, 2008 8:43 am Post subject: Toolkit debugger and broker code mismatch |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
I am experiencing a strange issue and I can't seem to resolve it. I have an execution group which contains 4 flows and a couple of message sets. I have made code changes in the ESQL for one flow. I have stopped the flow and removed it from the execution group using the toolkit. I deploy to the new flow and got a successful acknowledgement. When I debug this flow and ESQL the debugger is skipping over lines and not stopping at breakpoints. The result is that the new code is not deployed some how and the old code is still deployed in the broker. I have tried creating new a new executing group and deleting the previous one. I have added the source code to my bar file and that has not worked. It has in the past. I have restarted the RAC and the Broker and that has not worked either. I am lost on what to do. I have contacted IBM and all I get is we can't recreate your issue... UGH...
Broker Toolkit is at 6.0.0.2 and the broker is at 6.0.0.3.
Any help would be greatly appreciated. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 09, 2008 8:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Do you see a difference between the result of mqsilist BROKER and the list of DataFlowEngine processes on the machine?
I.e., you might have a Phantom Execution Group. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
FMER |
Posted: Wed Jan 09, 2008 9:35 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
They are the same. I have six execution groups and six DataFlowEngine processes.
I have selected the correct Flow engine in my debug configuration. So I don't see how a phantom execution group could cause a problem. The new execution group I created has not existed on this broker. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Jan 09, 2008 9:38 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
You might have redeployed but you did not compile before deployment and you have auto-compile turned off. So you redeployed the old code executable...
Enjoy  _________________ MQ & Broker admin |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 09, 2008 9:39 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
A phantom EG could hold an older version of the code.
Are you sure that you deployed the newest version of the code, and that you rebuilt the projects before building a new bar file?
I.e. - try a) doing a CLEAN on all projects involved, and then b) creating a new BAR file and deploying that. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
FMER |
Posted: Wed Jan 09, 2008 9:51 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
The Build Automatically option is on. I have cleaned the all the projects and created a new bar file and deployed it successfully.
I will try it again. This is driving me nuts! |
|
Back to top |
|
 |
FMER |
Posted: Wed Jan 09, 2008 10:23 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
I cleaned all projects, turned off the Build Automatically and build each project separately. I created a new bar file and added the projects. I stopped and removed the flows and message sets from my execution group. I deployed the new bar file and got successful messages in the Event log.
BIP4040I: The Execution Group 'DEVELOPMENT' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
BIP2056I: Broker FQMBR01D_BROKER successfully processed the entire internal configuration message.
An internal configuration message was processed to completion.
No user action required.
When I also updated the debug config by removing all flows and saved it. Then I added the flows back and save it.
I still got the same result where the code has not been deployed to the broker. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 09, 2008 10:49 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
turn on user trace(debug) and see if that confirms the results you're seeing in the RAC.
It could just be a weird RAC issue. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
FMER |
Posted: Wed Jan 09, 2008 12:18 pm Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
I ran the user trace (debug) and found that my code did get deployed correctly. So that is good but the bad is the debugger is still jumping over lines and stopping at blank lines.
Looks like it may be the RAC issue. Any suggestions on how to resolve it? I have start/stopped it in the broker server once already. |
|
Back to top |
|
 |
jefflowrey |
Posted: Wed Jan 09, 2008 12:20 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002 Posts: 19981
|
Stop RAC.
Stop broker.
Start broker.
Start RAC.
Or learn to live with traces...
And restart toolkit with -clean for good measure. _________________ I am *not* the model of the modern major general. |
|
Back to top |
|
 |
FMER |
Posted: Wed Jan 09, 2008 1:26 pm Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
No luck, I followed your requested steps and I still have the strange behavior in the toolkit.
Does anyone know if Fix 011 addresses this issue? I see that the fix was available last month. |
|
Back to top |
|
 |
fjb_saper |
Posted: Wed Jan 09, 2008 1:45 pm Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
FMER wrote: |
No luck, I followed your requested steps and I still have the strange behavior in the toolkit.
Does anyone know if Fix 011 addresses this issue? I see that the fix was available last month. |
You show the toolkit being at 6.0.0.2 whereas it should show 6.0.2 ifix >9 ...
I hope that was only a typo... if not it will take a very long time to update the toolkit... _________________ MQ & Broker admin |
|
Back to top |
|
 |
FMER |
Posted: Thu Jan 10, 2008 8:00 am Post subject: |
|
|
Newbie
Joined: 09 Jan 2008 Posts: 7
|
Moving up to Fix 011 resolved the debugging issue.
Thanks for the help Jeff. |
|
Back to top |
|
 |
|