| Author |
Message
|
| shrek |
 Posted: Sun Apr 17, 2005 5:50 pm Post subject: EXCEPTION_ACCESS_VIOLATION--Thread couldn't read memory addr |
 |
|
Acolyte
Joined: 19 Feb 2005
Posts: 61
Location: Gudivada,India
|
All,
Can you please help me in overcoming the below error. The broker process the deploy and the message successfully if i comment out the call to the java methods.
If I uncomment and deploy the broker I am recieving the below errors.
Here is the java code
| Code: |
package com.ibm.JavaMethods;
import com.ibm.broker.plugin.*;
import com.ibm.broker.plugin.MbException;
import com.ibm.broker.plugin.MbInputTerminal;
import com.ibm.broker.plugin.MbMessageAssembly;
import com.ibm.broker.plugin.MbNode;
import com.ibm.broker.plugin.MbNodeInterface;
public class BrokerUtils {
/*
* Returns the name of the broker, which the flow is running on.
*/
public static String getBrokerName() {
String value ="Error:";
try
{
// create an instance of message node
MbNode mn = new MbNode();
// create an instace of broker class
MbBroker mb = mn.getBroker();
value = mb.getName();
return value;
} catch (MbException e) {
return value;
} // end of try catch block
} // end of getBrokerName static method
|
Here is the Create Procedure and Call
| Code: |
CREATE PROCEDURE getBroker()
RETURNS CHAR
LANGUAGE JAVA
EXTERNAL NAME "com.ibm.JavaMethods.BrokerUtils.getBrokerName";
SET Environment.Variables.brokerName = getBroker();
|
| Quote: |
( WKSBRKR.Test ) 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:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WKSBRKR.Test.2260.196.Abend
A summary of the Error follows:
An Unhandled Exception detected in process 2260, on thread 0xC4.
Type: EXCEPTION_ACCESS_VIOLATION (C0000005).
Address: 001B:00EBE60B.
The thread could not read from memory address 0x0000001C.
'.
A broker process is terminating abnormally.
|
| Quote: |
( WKSBRKR.Test ) Message broker internal error: diagnostic information 'As a result of a Severe Abend Error, a MiniDump has been written to: C:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WKSBRKR.Test.2260.196.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:/Program Files/IBM/WebSphere Business Integration Message Brokers/errors/WKSBRKR.Test.2260.196.dmp'.
Shutdown and restart the message broker. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.
|
| Quote: |
( WKSBRKR.Test ) Database record associated with message flow '5398da52-0301-0000-0080-9834bafb23d0' is not valid.
The message broker found a database record associated with the persistent state of message flow '5398da52-0301-0000-0080-9834bafb23d0' to be invalid. The active broker state may not be as expected.
See the following message or messages for details of the error. Attempt to correct the error or errors by redeploying the complete broker configuration from the Message Brokers Toolkit. If the problem persists, contact your IBM support center.
|
System Details
OS: Windows XP Professional
Version : WBIMB 5 FixPack 4
I have read on IBM site that this is a program error and is fixed in FixPack3 but I am already on FixPack4
Thanks in advance for your help |
|
| Back to top |
|
 |
| rkford11 |
| Posted: Sun Apr 17, 2005 7:20 pm Post subject: Re: EXCEPTION_ACCESS_VIOLATION--Thread couldn't read memory |
|
|
Partisan
Joined: 06 Jun 2004
Posts: 316
|
|
| Back to top |
|
|
| shrek |
| Posted: Mon Apr 18, 2005 5:41 pm Post subject: |
|
|
Acolyte
Joined: 19 Feb 2005
Posts: 61
Location: Gudivada,India
|
Does anyone know if this was fixed in FP 5? I'm yet to go through the FP5 read me file and Memo.ptf.
Appreciateyour help.
Thanks. |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Apr 19, 2005 2:16 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
What you are trying to do is not supported from in a Java Method called from ESQL. Whilst I agree the broker should not abend, and a fix to throw an exception explaining the problem would be better, what you are trying to do is not possible. This method is supposed to be called from a Java Plugin NODE, not from a ESQL calling a Java stand alone method. The problem is the new MbNode object you create is not part of a flow, and therefore not part of the broker, and so has no brokerName.
Regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| shrek |
| Posted: Tue Apr 19, 2005 6:41 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2005
Posts: 61
Location: Gudivada,India
|
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Apr 19, 2005 6:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
That's not what he said.
What he said is, you can't call the Broker Plug-in Java API from within a Java procedure.
You can't use anything in the com.ibm.broker.plugin packages in a regular Java procedure.
You can only use them from within a real plug-in.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| shrek |
| Posted: Wed Apr 20, 2005 5:03 am Post subject: |
|
|
Acolyte
Joined: 19 Feb 2005
Posts: 61
Location: Gudivada,India
|
I got it now. Sorry MGK. Thanks Jefflowrey.
I'll investigate further. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Wed Apr 20, 2005 5:09 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
|
| Back to top |
|
|
| malammik |
| Posted: Wed Apr 20, 2005 6:45 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2005
Posts: 397
Location: Philadelphia, PA
|
|
| Back to top |
|
|
|
|
