| Author |
Message
|
| kwase |
 Posted: Wed Nov 09, 2005 2:12 am Post subject: EXCEPTION_ACCESS_VIOLATION (C0000005) |
 |
|
Newbie
Joined: 09 Nov 2005
Posts: 4
|
the error occurs everytime I'm trying to deploy something. I don't see the error in the toolkit, there it just says nothing. The error messages are from the even-viewer. I've reinstalled evereything (incl. DB2 and CSD6) and after the reinstall I can deploy only once and then never again with the same error (unfortunately in german but the important bit is in english):
( WBRK_BROKER.default ) Broker-Prozess wurde abnormal beendet; folgende Informationen sind erforderlich, wenn Sie sich mit IBM in Verbindung setzen: '
Severe Abend Error detected.
For full details see Abend File: C:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WBRK_BROKER.default.3244.1852.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 3244, on thread 0x73C.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 001B:0CBA93A5.
The thread could not read from memory address 0x000000B8.
'.
Ein Broker-Prozess wurde fehlerhaft beendet.
next error message:
( WBRK_BROKER.default ) Interner Fehler im Nachrichten-Broker; Diagnoseinformationen: 'As a result of a Severe Abend Error, a MiniDump has been written to: C:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WBRK_BROKER.default.3244.1852.dmp'.
Im Nachrichten-Broker ist ein interner Softwarefehler aufgetreten. Die Auswirkungen dieses Fehlers auf die Arbeitsgänge des Brokers werden in weiteren Nachrichten angezeigt. Die Diagnoseinformationen dieser Nachricht lauten: 'As a result of a Severe Abend Error, a MiniDump has been written to: C:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WBRK_BROKER.default.3244.1852.dmp'.
Schalten Sie den Nachrichten-Broker ab, und starten Sie ihn erneut. Wenn das Problem immer noch auftritt, starten Sie das System neu. Sollte das Problem weiterhin bestehen, benachrichtigen Sie das IBM Support Center.
thanks a lot
Christian |
|
| Back to top |
|
 |
| jhosie |
| Posted: Wed Nov 09, 2005 6:36 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
unless you have a user defined extension (plug-in node or parser) then this is probably an internal error.
You should contact IBM support.
If you do have User Defined Extensions then looking at the contents of C:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WBRK_BROKER.default.3244.1852.Abend might help you find the problem. |
|
| Back to top |
|
|
| kwase |
| Posted: Thu Nov 10, 2005 1:00 am Post subject: |
|
|
Newbie
Joined: 09 Nov 2005
Posts: 4
|
With which editor can I open the .abend or the .dmp files?
Yesterday I've reinstalled XP and WBIMB and everything was working fine until I changed a flow during a debugging session. After the change I couldn't run the flow to completion and could not stop the debugger. And I've got again the same errors as described above...Is this a known behaviour? I remember that I have changed a flow during a running debugging session without any problems in the past. |
|
| Back to top |
|
|
| jhosie |
| Posted: Thu Nov 10, 2005 1:58 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
you can view the abend file in a text editor.
However, it will only make sense to the developers of the code.
So, unless you have your own custom code running (e.g.. a C User Defined Node) then you should contact IBM support with this error and send them the abend and dmp files.
In the meantime can you get your broker back into a working state by detaching the debugger or restarting the workbench?
If you are in a development environment, is it an option to delete and re-create the broker? That might be the quickest way forward for you. |
|
| Back to top |
|
|
| kwase |
| Posted: Thu Nov 10, 2005 2:05 am Post subject: |
|
|
Newbie
Joined: 09 Nov 2005
Posts: 4
|
Yep, I already tried all these steps without success:
1. restart
2. delete the broker
3. delete broker/configmgr/q-manager
4. delete/reinstall WBIMB
The only solution was to reinstall XP. btw: I'm not running any User defined nodes.
I've send the abend/dmp files to IBM, lets wait and see what they find out.
thanks
Christian |
|
| Back to top |
|
|
| jhosie |
| Posted: Thu Nov 10, 2005 2:33 am Post subject: |
|
|
Apprentice
Joined: 12 May 2005
Posts: 28
|
ok, one other component in the equation is RAC (Rational Agent Controller) . The RAC is the component that goes between the Workbench and the broker and acts the comunication channel between them.
If you hit the problem again, try restaring the RAC server. That would have happened when you rebooted/re-installed XP.
You can restart the RAC service via ContolPanel->Administrative Tools->Services. In there you should see a service named IBM Rational Agent Controler. click on restart (or stop then start). You will need to re-start the broker after doing this if you want to use the flow debugger.
NOTE the RAC server runs on the same machine as the broker.
so the order I would do things to try and clear up after this error is:
1) terminate debugger session and/or exit the WBIMB Workbench.
2) stop the broker (and delete if necessary)
3) stop/restart the RAC server
4) start the broker (create if necessary)
5) start WBIMB Workbench
6) verify that you can now deploy okay
7) attach debugger and verify that works ok.
It might be safer to detach the debugger whenever you are going to deploy so as to avoid this error. |
|
| Back to top |
|
|
| kwase |
| Posted: Thu Nov 10, 2005 6:04 am Post subject: |
|
|
Newbie
Joined: 09 Nov 2005
Posts: 4
|
I've tried the steps you suggested but at the end I had to start again at zero:
reinstall XP and all the rest...
thanks again |
|
| Back to top |
|
|
|
|
