| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Problem with debugger & execution groups |
« View previous topic :: View next topic » |
| Author |
Message
|
| opel.corsa |
 Posted: Tue Sep 12, 2006 4:47 am Post subject: Problem with debugger & execution groups |
 |
|
Newbie
Joined: 12 Sep 2006
Posts: 2
Location: Germany
|
Hello
We have set up a new project and could run and debug everything until last friday. But since yesterday, we have some anomalies.
First, we can no longer use the debugger. He turns off by himself after max. one minute. Within that time, we can inspect flows
and see data, but it does not help much. Checking this site did not lead to a solution.
And on the machine hosting the server (linux, 1,5 GB RAM, WBI 6.0.0.1), we found a duplicate execution group. (Broker Toolkit: 6.0.0.1)
| Code: |
mqsi@54 bin]$ ps -ef | grep DataFlowEngine
...
mqsi 11935 11858 0 13:14 ? 00:00:11 DataFlowEngine BKD01LSE 856b5588-0d01-0000-0080-bd74b50583e4 as_sinfos_test 0
mqsi 11942 11858 0 13:14 ? 00:00:13 DataFlowEngine BKD01LSE cdaf069c-0d01-0000-0080-9f3f17972cb0 as_sinfos_test 0
...
mqsi 12781 10596 0 13:39 pts/2 00:00:00 grep DataFlowEngine
|
And 'top' revealed many DataFlowEngine entries, maybe too many.
| Code: |
[mqsi@54 bin]$ top
13:38:45 up 21:02, 7 users, load average: 0.58, 0.24, 0.54
526 processes: 524 sleeping, 2 running, 0 zombie, 0 stopped
CPU states: cpu user nice system irq softirq iowait idle
total 0.0% 0.0% 2.1% 0.0% 0.0% 0.1% 97.6%
Mem: 1025376k av, 1002472k used, 22904k free, 0k shrd, 76200k buff
778212k actv, 143568k in_d, 14076k in_c
Swap: 2040212k av, 138312k used, 1901900k free 193608k cached
PID USER PRI NI SIZE RSS SHARE STAT %CPU %MEM TIME CPU COMMAND
12690 mqsi 20 0 1384 1384 1132 S 0.0 0.1 0:00 0 bash
12689 mqsi 16 0 2076 2032 1672 S 0.0 0.1 0:00 0 sshd
12687 root 20 0 1852 1808 1484 S 0.0 0.1 0:00 0 sshd
12608 mqsi 15 0 1664 1664 884 R 1.3 0.1 0:02 0 top
12530 mqm 20 0 1832 1632 1400 S 0.0 0.1 0:00 0 amqpcsea
12279 mqm 20 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12218 mqsi 15 0 17844 11M 5344 S 0.0 1.1 0:00 0 RAServer
12192 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12190 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12189 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12188 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12187 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12186 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12185 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12184 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12183 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12179 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12162 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12161 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12160 mqsi 15 0 76812 75M 27368 S 0.0 7.4 0:00 0 DataFlowEngine
12159 mqsi 15 0 76812 75M 27368 S 0.0 7.4 0:00 0 DataFlowEngine
12158 mqsi 15 0 76812 75M 27368 S 0.0 7.4 0:00 0 DataFlowEngine
12157 mqsi 15 0 76812 75M 27368 S 0.0 7.4 0:00 0 DataFlowEngine
12155 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12156 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12153 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12154 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12151 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12152 mqsi 15 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12150 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12149 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12147 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12145 mqsi 25 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12146 mqsi 24 0 89444 87M 27656 S 0.0 8.7 0:00 0 DataFlowEngine
12144 mqm 15 0 3720 3720 3244 S 0.0 0.3 0:00 0 amqzlaa0
12143 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12142 mqm 24 0 2212 2212 1768 S 0.0 0.2 0:00 0 amqcrsta
12141 mqm 15 0 9532 9112 7700 S 0.0 0.8 0:00 0 amqzlaa0
12140 mqsi 15 0 78944 77M 27340 S 0.0 7.6 0:00 0 DataFlowEngine
12139 mqsi 15 0 78944 77M 27340 S 0.0 7.6 0:00 0 DataFlowEngine
12138 mqsi 15 0 78944 77M 27340 S 0.0 7.6 0:00 0 DataFlowEngine
12135 mqm 15 0 2212 2212 1768 S 0.0 0.2 0:00 0 amqcrsta
12136 mqm 20 0 2212 2212 1768 S 0.0 0.2 0:00 0 amqcrsta
12137 mqm 15 0 2212 2212 1768 S 0.0 0.2 0:00 0 amqcrsta
12133 mqm 15 0 2212 2212 1768 S 0.0 0.2 0:00 0 amqcrsta
12131 mqm 15 0 3720 3720 3244 S 0.0 0.3 0:00 0 amqzlaa0
12132 mqm 15 0 3720 3720 3244 S 0.0 0.3 0:00 0 amqzlaa0
12130 mqsi 15 0 84180 82M 28636 S 0.0 8.2 0:00 0 DataFlowEngine
12129 mqsi 15 0 84180 82M 28636 S 0.0 8.2 0:00 0 DataFlowEngine
12128 mqsi 15 0 84180 82M 28636 S 0.0 8.2 0:00 0 DataFlowEngine
12127 mqm 20 0 3720 3720 3244 S 0.0 0.3 0:00 0 amqzlaa0
12126 mqm 15 0 3720 3720 3244 S 0.0 0.3 0:00 0 amqzlaa0
12125 mqsi 15 0 84180 82M 28636 S 0.0 8.2 0:00 0 DataFlowEngine
|
Could anyone think of a solution for this problem?[/list] |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Tue Sep 12, 2006 6:11 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Most linux version of PS and TOP show threads instead of procesess.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| opel.corsa |
| Posted: Tue Sep 12, 2006 6:36 am Post subject: |
|
|
Newbie
Joined: 12 Sep 2006
Posts: 2
Location: Germany
|
Got that.
But what about the debugger, which disappears too soon to work with? |
|
| Back to top |
|
|
| special_agent_Queue |
| Posted: Fri Oct 06, 2006 9:33 am Post subject: |
|
|
Centurion
Joined: 27 Jul 2006
Posts: 102
|
I think we are having the same problem.
The debugger appears to connect, but about 15 seconds later, it says "Cannot connect with flow engine."
Checking the event viewer for the server machine shows that the execution group had stopped and started. When we encountered this problem the first time, restarting the computer with the toolkit trying to connect to the debugger worked for a couple days. Now it doesn't.
Here are the specific event messages:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
( WMB6_BROKER.default ) Broker process terminating abnormally: The following diagnostic information will be required when contacting IBM: '
Severe Abend Error detected.
For full details see Abend File: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/WMB6_BROKER.default.556.4108.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 556, on thread 0x100C.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 001B:70D57885.
The thread could not read from memory address 0x0000000C.
'.
A broker process is terminating abnormally.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~`
( WMB6_BROKER.default ) Message broker internal error: diagnostic information 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/WMB6_BROKER.default.556.4108.dmp'.
An internal software error has occurred in the message broker. Further messages will indicate the effect of this error on the broker's transactions. The diagnostic information associated with this message is: 'As a result of a Severe Abend Error, a MiniDump has been written to: C:\Documents and Settings\All Users\Application Data\IBM\MQSI/common/errors/WMB6_BROKER.default.556.4108.dmp'.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
( WMB6_BROKER ) The broker has detected that the Execution Group 'default', process ID 556, has shutdown.
An Execution Group has shutdown. A new instance of the execution group will be started in approximately 0 seconds.
Investigate any prior system log messages for possible problems. Contact your IBM support center if you are unable to determine the cause of the shutdown.
~~~~~~~~~~~~~~~~
Anyone have any ideas?
Thanks! |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Oct 06, 2006 3:17 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
If you are trying to debug with more than 9 execution groups registered to the RAC in V6 talk to IBM support and get the fix for the toolkit.
Otherwise happy debugging...
Anyways there should be some information on why the exec group shut down in the broker log.
Read it VERY carefully. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
