Posted: Thu Jan 14, 2010 7:14 am Post subject: BIP7078S: Failed to detach thread
Newbie
Joined: 14 Jan 2010 Posts: 1
Broker version 6.1.0.4
64-bit AIX 5.3.0.0
Toolkit version 6.1.0.5
I am trying to make a flow (File input / MQ output) go to sleep for x number of minutes if a shared resource is being used. The sleep action is performed by using "Thread.currentThread().sleep(1000 * 60 * intNoOfMins);" in a Java compute node which is accessed within a loop until either the shared resource is freed OR a maximum number of loops is reached. The intNoOfMins is populated from a local environmet variable set from within ESQL.
The problem I get is that the flow can be told to sleep 9 times however on the 10th attempt to use the Java compute node the JVM errors out acording to the user.log enties below. the only way to get the Broker running again is to stop and start it.
Have I done something incorrectly (my first attempt at using Java compute nodes) or is there something else
I'm missing? I've tried to trace the flow but the last entries before the 10th call to the Java Compute node don't
show any issues so I'm at a loss as to what the broker or JVM is complaining about...
The error messages from the user.log
Code:
Jan 13 21:59:44 spwebapp1 user:err|error WebSphere Broker v6104[1679476]: (WMBBRT7.MSIP)[16449]BIP2121E: The thread bootstrap
code caught an unhandled exception on thread '16449'. : WMBBRT7.7585493c-2301-0000-0080-ed457b5c9a47: /build/S610_P/src/Comm
onServices/rios_aix_4/ImbOsThread.cpp: 252: ImbOsThread::threadBootStrap: :
Jan 13 21:59:44 spwebapp1 user:info WebSphere Broker v6104[1679476]: (WMBBRT7.MSIP)[16449]BIP4374S: An unexpected exception h
as occurred in the Java API framework. : WMBBRT7.7585493c-2301-0000-0080-ed457b5c9a47: /build/S610_P/src/DataFlowEngine/Plugi
nInterface/com_ibm_broker_plugin_CMbService.cpp: 1832: ImbJavaExceptionUtils::throwableToNativeException: :
Jan 13 21:59:44 spwebapp1 user:info WebSphere Broker v6104[1679476]: (WMBBRT7.MSIP)[16449]BIP7078S: Failed to detach thread f
rom the JVM. : WMBBRT7.7585493c-2301-0000-0080-ed457b5c9a47: /build/S610_P/src/JNI/ImbJVM.cpp: 1263: ImbJVM::freeEnvironment:
// Extract and convert local environment value
String strNoOfMins = localEnv.getFirstElementByPath("/WaitNoOfMins").getValueAsString();
int intNoOfMins = Integer.parseInt(strNoOfMins);
if (intNoOfMins > 0){
Thread.currentThread().sleep(1000 * 60 * intNoOfMins);
}
else{
// if 0 passed in then just sleep for 100 milliseconds
Thread.currentThread().sleep(100);
}
// End of user code
// ----------------------------------------------------------
// The following should only be changed
// if not propagating message to the 'out' terminal
out.propagate(outAssembly);
Have anyone else has also faced this problem, it is occuring in our environment which is running BROKER V6.1 on AIX server.
Whenever we try to deploy the flow(which is having a JavaComputeNode, we are receiving this error).
Quote:
Jul 28 14:32:53 barb020c WebSphere Broker v6105[303278]: (BROKER1.UAB123)[3401]BIP2121E: The thread bootstrap code caught an unhandled exception on thread '3401'. : BROKER1.f5624a7c-2901-0000-0080-e7e1030c3ce2: /build/S610_P/src/CommonServices/rios_aix_4/ImbOsThread.cpp: 252: ImbOsThread::threadBootStrap: :
Jul 28 14:32:53 barb020c WebSphere Broker v6105[303278]: (BROKER1.UAB123)[3401]BIP4364S: The Java API framework could not create an instance of MbBrokerException. : BROKER1.f5624a7c-2901-0000-0080-e7e1030c3ce2: /build/S610_P/src/DataFlowEngine/PluginInterface/com_ibm_broker_plugin_MbBrokerExceptionImp.cpp: 88: com_ibm_broker_plugin_MbBrokerException::createMbBrokerException: :
Jul 28 14:32:53 barb020c WebSphere Broker v6105[303278]: (BROKER1.UAB123)[3401]BIP7078S: Failed to detach thread from the JVM. : BROKER1.f5624a7c-2901-0000-0080-e7e1030c3ce2: /build/S610_P/src/JNI/ImbJVM.cpp: 1276: ImbJVM::freeEnvironment: :
We are not able to find out the root cause of this problem and it seems the DataFlowEngine process is getting hanged after that as we are not able to perform a successful mqsireload on the execution group.
Only after re-starting the broker, it started working and then this problem again happened next day.
Does anyone can suggest the root cause of this problem.
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