[JBoss Web Services] New message: "Occasional exceptions out of SOAPAddressingPropertiesImpl.writeHeaders"
by Andrew Dinn
User development,
A new message was posted in the thread "Occasional exceptions out of SOAPAddressingPropertiesImpl.writeHeaders":
http://community.jboss.org/message/523856#523856
Author : Andrew Dinn
Profile : http://community.jboss.org/people/adinn
Message:
--------------------------------------------------------------
Hi guys,
I am running an XTS demo on the current AS trunk and am occasionally seeing exceptions thrown from the soap stack:
10:23:03,631 ERROR org.jboss.ws.core.jaxws.handler.HandlerChainExecutor Exception during handler processing: javax.xml.ws.addressing.AddressingException: Cannot read ws-addressing headers
at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:317)
at org.jboss.ws.extensions.addressing.jaxws.WSAddressingClientHandler.handleOutbound(WSAddressingClientHandler.java:116)
at org.jboss.wsf.common.handler.GenericHandler.handleMessage(GenericHandler.java:53)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:312)
at org.jboss.ws.core.jaxws.handler.HandlerChainExecutor.handleMessage(HandlerChainExecutor.java:145)
at org.jboss.ws.core.jaxws.client.ClientImpl.callRequestHandlerChain(ClientImpl.java:178)
at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:300)
at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:299)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:170)
at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:150)
at $Proxy216.completedOperation(Unknown Source)
at com.arjuna.webservices11.wsba.client.ParticipantCompletionCoordinatorClient.sendCompleted(ParticipantCompletionCoordinatorClient.java:142)
at com.arjuna.wst11.messaging.engines.ParticipantCompletionParticipantEngine.sendCompleted(ParticipantCompletionParticipantEngine.java:809)
at com.arjuna.wst11.messaging.engines.ParticipantCompletionParticipantEngine.commsTimeout(ParticipantCompletionParticipantEngine.java:760)
at com.arjuna.wst11.messaging.engines.ParticipantCompletionParticipantEngine.access$000(ParticipantCompletionParticipantEngine.java:52)
at com.arjuna.wst11.messaging.engines.ParticipantCompletionParticipantEngine$1.run(ParticipantCompletionParticipantEngine.java:1254)
at java.util.TimerThread.mainLoop(Timer.java:512)
at java.util.TimerThread.run(Timer.java:462)
Caused by: javax.xml.soap.SOAPException: Unable to create SOAP Factory: Unable to create SAAJ meta-factoryProvider com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl could not be instantiated: java.lang.IllegalStateException: BaseClassLoader@144ee21 classLoader is not connected to a domain (probably undeployed?) for class com.sun.xml.internal.messaging.saaj.soap.SAAJMetaFactoryImpl
at javax.xml.soap.SOAPFactory.newInstance(SOAPFactory.java:270)
at org.jboss.ws.extensions.addressing.soap.SOAPAddressingPropertiesImpl.writeHeaders(SOAPAddressingPropertiesImpl.java:225)
... 17 more
The first exception tag 'Cannot read ws-addressing headers' is actually misleading since the root cause is the IllegalStateException occurring under the call to SOAPFactory.newInstance(). The thing is this problem does not seem to be stopping the XTS code from working -- I am presuming this is because the error is intermittent and the message gets through when XTS resends. Any idea what is causing the IllegalStateException?
n.b. the error happens quite often, I would guess once every 2-3 times XTS dispatches a 'request' or 'response' (these are paired 1-way messages) but I cannot guarantee to be able to reproduce it as yet. The demo in which it manifests is fairly complex -- AOP, EJB, Web Service + XTS BA :-( -- so I'm note sure yet how to isolate the problem. I just want to check if it is a known bug. If not I will investigate further.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523856#523856
16 years, 2 months
[jBPM] New message: "Re: jBPM console not working on JBoss 5.1.0 standard configuration"
by Nenad Popovic
User development,
A new message was posted in the thread "jBPM console not working on JBoss 5.1.0 standard configuration":
http://community.jboss.org/message/523844#523844
Author : Nenad Popovic
Profile : http://community.jboss.org/people/neshap
Message:
--------------------------------------------------------------
Thx for reply Maciej. I tried it again on both "standard" and "all" configuration, and you are right about "all" configuration. I probably caused some confusion by claiming it doesn't work on all without trying it on clean install. But my claim about "standard" still remains. Now I'm not sure if it is jBPM thing at all, since that configuration should not be different from all (except for clustering support). I guess I'll stick with default for development, all for production, and hopefully grab some time to investigate further problem with "standard" conf.
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523844#523844
16 years, 2 months
[jBPM] New message: "Re: How to configure jbpm 4.0 on Tomcat 6.0"
by Anand Kumar
User development,
A new message was posted in the thread "How to configure jbpm 4.0 on Tomcat 6.0":
http://community.jboss.org/message/523839#523839
Author : Anand Kumar
Profile : http://community.jboss.org/people/akstifr
Message:
--------------------------------------------------------------
Thank you once again for suggestions but
As we have developed our application using jbpm 4.0 and for testing we used jboss 5.0
but now we want to move the application from jboss to Tomcat 5.5 in real time. So i am looking for tomcat setup.
Is it possible to move the application from *jbpm 4 to jbpm 4.3* without any issues or will it have any *incomparability* with the versions of jar files or *dependency* problem arises??
*Whether a application developed in jbpm4.3 can be deployed on Tomcat 5.5 or it requires Tomcat 6.0 or higher version??*
--------------------------------------------------------------
To reply to this message visit the message page: http://community.jboss.org/message/523839#523839
16 years, 2 months