| Author |
Message
|
| kiran_raghunam |
 Posted: Tue May 02, 2006 6:05 am Post subject: problem with debugger:pls help |
 |
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
hi i am using WMB6.0,after putting the message in to the input queue from rfhutil,the broker perspective is not switching to debug perspective,but the message is going to output queue.The error in applicationlog is as follows:
( CITCO_Broker1.default ) An error occurred in the JNI layer during flow debugging
Observe any following errors and try to correct them. If you are unable to do so, please contact your IBM support center.
1.3.2.0.
0008: 00 00 43 00 49 00 54 00 ..C.I.T.
0010: 43 00 4f 00 5f 00 42 00 C.O._.B.
0018: 72 00 6f 00 6b 00 65 00 r.o.k.e.
0020: 72 00 31 00 2e 00 61 00 r.1...a.
0028: 64 00 62 00 63 00 63 00 d.b.c.c.
0030: 37 00 66 00 33 00 2d 00 7.f.3.-.
0038: 30 00 61 00 30 00 31 00 0.a.0.1.
0040: 2d 00 30 00 30 00 30 00 -.0.0.0.
0048: 30 00 2d 00 30 00 30 00 0.-.0.0.
0050: 38 00 30 00 2d 00 38 00 8.0.-.8.
0058: 63 00 66 00 65 00 66 00 c.f.e.f.
0060: 62 00 63 00 34 00 37 00 b.c.4.7.
0068: 38 00 30 00 37 00 00 00 8.0.7...
0070: 46 00 3a 00 5c 00 62 00 F.:.\.b.
0078: 75 00 69 00 6c 00 64 00 u.i.l.d.
0080: 5c 00 53 00 30 00 30 00 \.S.0.0.
0088: 30 00 5f 00 50 00 5c 00 0._.P.\.
0090: 73 00 72 00 63 00 5c 00 s.r.c.\.
0098: 44 00 61 00 74 00 61 00 D.a.t.a.
00a0: 46 00 6c 00 6f 00 77 00 F.l.o.w.
00a8: 45 00 6e 00 67 00 69 00 E.n.g.i.
00b0: 6e 00 65 00 5c 00 46 00 n.e.\.F.
00b8: 6c 00 6f 00 77 00 44 00 l.o.w.D.
00c0: 65 00 62 00 75 00 67 00 e.b.u.g.
00c8: 5c 00 49 00 6d 00 62 00 \.I.m.b.
00d0: 56 00 66 00 64 00 4a 00 V.f.d.J.
00d8: 6e 00 69 00 49 00 6e 00 n.i.I.n.
00e0: 74 00 65 00 72 00 66 00 t.e.r.f.
00e8: 61 00 63 00 65 00 2e 00 a.c.e...
00f0: 63 00 70 00 70 00 00 00 c.p.p...
00f8: 31 00 36 00 38 00 00 00 1.6.8...
0100: 49 00 6d 00 62 00 56 00 I.m.b.V.
0108: 66 00 64 00 4a 00 6e 00 f.d.J.n.
0110: 69 00 49 00 6e 00 74 00 i.I.n.t.
0118: 65 00 72 00 66 00 61 00 e.r.f.a.
0120: 63 00 65 00 3a 00 3a 00 c.e.:.:.
0128: 64 00 65 00 73 00 65 00 d.e.s.e.
0130: 72 00 69 00 61 00 6c 00 r.i.a.l.
0138: 69 00 7a 00 65 00 00 00 i.z.e...
0140: 00 00 00 00 ....
Also while creating a newconfiguration for debug,there is a column called source in which there is a field called default.if i click on it it says:
a stack overflow error has occured.
please help...
thnx in advance
_________________
Regards
Kiran |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue May 02, 2006 4:29 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Upgrade to 6.0.0.1 of Toolkit and Broker runtime.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Tue May 02, 2006 9:05 pm Post subject: upgrading not possible.... |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
hi thnx for replyin...
actually the project requirement is that we use only WMB6.0.
so upgrading to 6.0.1 is not possible....
also this problem is occuring only on my machine and other machines are working fine...
any other solution?
thnx in advance
_________________
Regards
Kiran |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Tue May 02, 2006 9:10 pm Post subject: upgrading not possible.... |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
hi thnx for replyin...
actually the project requirement is that we use only WMB6.0.
so upgrading to 6.0.1 is not possible....
also this problem is occuring only on my machine and other machines are working fine...
any other solution?
thnx in advance
_________________
Regards
Kiran |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Tue May 02, 2006 10:30 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi kiran_raghunam,
This is the most silly excuse your manager or client or you could give us.
MB v6 is a new tool, there are bound to be fixes released....upgrading to 6.0.1 is not that u need to ask the client to spend on the product again, and developing over a tool which you know has errors is then putting your neck on the line....
I suggest if this is your approach, then u might as well go into production with v5 and Fixpack 8.
You said that the broker perspective is not switching to Debug, have you selected the option for it to automatically switch.
Did you add the flow to debug.
Stack overflow could mean that your virtual memory is low.
Regards. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Wed May 03, 2006 2:01 am Post subject: |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
HI
Yes i have attached the flow to the debugger and the option to switch automatically is also set.
I even reinstalled Rational Controller , increased the size of virtual memory..
but the problem still persists..
Also let me knw if there are any specific rules to be followed while installing fix pack6.0.0.1 and how to install fix pack...
Pls help
Thnx in advance....
_________________
Regards
Kiran |
|
| Back to top |
|
|
| TheBigEasy |
| Posted: Wed May 03, 2006 4:20 am Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Hi kiran_raghunam
What is the configuration of your environment. Are you developing and testing with toolkit, boker and ConfigMgr all on your local PC?
I have done several installs locally on WMBV6 and with FP01 - the debugging all ran smoothly. However, we are having an issue with the following: toolkit (PC), Configmgr (Windows Server) and broker (AIX).
Config lets us add the broker & ExecGroup, debug session starts - but the test message is not captured and debugged. We have tried logging onto the ConfigMgr and debugging from there, thinking that it was a problems with domian security but no joy yet!
If you are having the same problem - I'll post our solution (if we get one) to this topic.
best wishes |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Wed May 03, 2006 5:26 am Post subject: |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
Yes i am developing and testing with toolkit, broker and ConfigMgr all on my local PC...
pls giv soln as soon as possible....
Thnxs for ur help in adv...
regards
kiran
_________________
Regards
Kiran |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed May 03, 2006 5:55 am Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi kiran_raghunam,
Do a Debug trace on your flow. Check the log created, you should find something.
Try putting a message using an Enqueue or a direct queue put....
Regards. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Wed May 03, 2006 6:41 am Post subject: |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
Hi
I have put the message using enqueue and adding traces in the flow.
my flow consists of MQInput node,Mapping node and MQOutput node along with trace nodes.
I am able to put messge using enqueue and its going fine to MQOutput..
The problem is it is not switchin to debug perspective and the application log says:
CITCO_Broker1.default An error occurred in the JNI layer during flow debugging
shall i reinstall the broker toolkit itself?
Thnx for replying..
waitin for ur valuable sugesstions...
_________________
Regards
Kiran |
|
| Back to top |
|
|
| TheBigEasy |
| Posted: Wed May 03, 2006 1:47 pm Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Hi kiran_raghunam
I have installed WMBv6 several on local set ups and in 9 out 10 they have been fine. The only problem I came across with debug on base WMBv6 I posted:
http://www.mqseries.net/phpBB2/viewtopic.php?t=25828&highlight=
I could recreate the problem, but I failed to raise a PMR because I took FixPack 01- no issues since.
I would take the earlier suggestion of jefflowrey and elvis_gn of applying FP01. I would argue that it is still WMBv6 and you save the mgnt team the cost of upgrading at a later date. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Wed May 03, 2006 10:47 pm Post subject: no more head scratching.... |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
hi
I have reinstalled the broker toolkit and no issues since then....
i was told not to apply FP1 by a member of my team as it would create some other problems .....which i dont understand till now....
is it that Fix pack creates any problem?
do let me knw...
bye
Thnx...
_________________
Regards
Kiran |
|
| Back to top |
|
|
| elvis_gn |
| Posted: Wed May 03, 2006 10:59 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi kiran_raghunam,
If the fix pack created problems it wouldn't be called a FIX pack 
Ur friend seems to be conservative, and dosen't want to learn and preventing you from doing so too...put it on your local system and see how it behaves and wait for some time before installing into production.
Regards. |
|
| Back to top |
|
|
| kiran_raghunam |
| Posted: Thu May 04, 2006 3:37 am Post subject: |
|
|
Apprentice
Joined: 02 May 2006
Posts: 36
|
Hi
The problem seems to be prsisting after some successful attempts to debug...
The flowengine names are not being populated while creating a debug configuration...
i am able to attach flow project to the broker but flow engine list is empty..
Thnx in advance
_________________
Regards
Kiran |
|
| Back to top |
|
|
| TheBigEasy |
| Posted: Thu May 04, 2006 6:18 am Post subject: |
|
|
Apprentice
Joined: 04 Jul 2005
Posts: 33
Location: London
|
Hi kiran_raghunam
Can you recap on the issue? are all the components running under the same user, spec of pc etc. You are staying ont he base version?
Close everything down - ensure all the processes are killed in your taskmgr panel.
Manually start the components in order of RAC, broker, CM toolkit.
I would create and deploy a simple flow jsut to check everyhting hangs together before you debug.
Then try the debug.
best wishes |
|
| Back to top |
|
|
|
|
