sun-bpel-engine messageType definition Exception - only on solaris when not
Hi,
i'm using the latest release of sun-bpel-engine, and have encountered some weird behavior / BUG.... when running it over windows, my project runs great. but when deployed to unix (when not debugged), it fails and throws:
May 13, 2007 3:44:41 PM com.sun.jbi.engine.bpel.BPELSEInOutThread processRequest
SEVERE: Failed to process In Out Message messageExchangeId: ID:471124-2:2
java.lang.RuntimeException: Could not find the messageType definition babaOperationRequest, specified by the type attribute in jbi:message element.
at com.sun.jbi.engine.bpel.EngineHelper.createWSMessage(EngineHelper.java:493)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processRequest(BPELSEInOutThread.java:370)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.processMsgEx(BPELSEInOutThread.java:208)
at com.sun.jbi.engine.bpel.BPELSEInOutThread.run(BPELSEInOutThread.java:148)
May 13, 2007 3:44:41 PM com.sun.jbi.engine.bpel.BPELSEHelper sendError
WARNING: Setting MessageEx id ID179059471124-2:2 with error: Could not find the messageType definition babaOperationRequest, specified by the type attribute in jbi:message element.
when executed under debug, it runs great...
what's going on ?!
[1254 byte] By [
hofri-ya] at [2007-11-27 4:12:59]
# 1
Interesting..
What components are involved in this project? Who is sending the message to BPEL SE? Also one more thing you can do before sending the project over, is to turn on the log level (maybe to fine or finest if needed) and see the server log.
What i would look for is the JBI message being sent from consumer component
and what is received by the BPEL SE. I would check to see if the JBI message has the messageType attribute defined.
-Kiran.
# 2
A few more questions:
1. What is the configurationh of the Solaris machine (number of CPUs, etc)?
2. What client are you uisng to send in the request(s)?
3. Are you sending a single request or multiple concurrent requests? If you are sending multiple concurrent requests, can you try sending a single request.
# 4
T1000 is multi core, multi threaded. So it could be pointing to some threading issue in the XML document construction. At this point my suspicion is the "custom BC" code. Could you make sure that there is no issue with threading there?
Engine is being (has been) tested on T-series machines with the some of open-ESB BC components, it hasn't reported this error.
Maybe one way to try this out is, make sure your custom BC is in single thread mode (if it is possible) and engine too in single thread mode. Engine threads can be configured after you install the engine. You can do it through NB or programmatically through MBeans.
Next make engine multi thread mode.
Next make your BC multi thread mode and engine single thread.
Let us know in which mode you see the error. There is a chance that you may not see the error at all, because to reproduce the bug, you may need BC and BPEL SE to be multi threaded.
Let us know how it goes or what other techniques you tried to find out the issue.
thanks,
Kiran Bhumana
