Hi Alex,
The bpel process itself can't initialize or manage transaction at all it
just forwards transaction context.
i.e. you have to initialize XATransaction before Bpel Process.
Atomic property allows in transaction context to look at bpel process as
atomic part i.e. in case any outcoming calls are failed(rollback)
then the bpel process instance will be rolled back.
More details are here:
http://wiki.open-esb.java.net/Wiki.jsp?page=HTTPBCWS%20Atomic%20Transactionhttp://blogs.sun.com/dutchman/http://wiki.open-esb.java.net/Wiki.jsp?page=MEprocessingAndPropertyPropagationRegards,
Vitaly.
alexndr wrote:
> Hi!
>
> I have a BPEL that I have set to be "atomic". In the BPEL, the incoming
> message is sometimes stored to a JMS queue using the JMS BC. I have set the
> JMS BC WSDL to use XATransactions. I have also verified that connector
> resource used are configured to use XATransactions.
>
> When storing the message to the queue I get following info message:
>
> [#|2009-07-03T11:47:33.900+0200|INFO|sun-appserver9.1|sun-jms-binding.com.sun.jbi.jmsbc.OutboundMessageProcessor|_ThreadID=102;_ThreadName=JMSBC-pool-1-thread-1;{
http://j2ee.netbeans.org/wsdl/bpelProject/sendToErrorQueue}JMSOutOperation;110967726877695-59603-134659072536820180;qError;Context=caProjetc-sun-jms-binding::sendToErrorQueue_OutPort::JMSOutOperation;|JMSBC-I0713:
> JMS binding operation
> {
http://j2ee.netbeans.org/wsdl/bpelImpulsFormedlare/skickaFelTillKo}JMSOutOperation
> was marked as XATransaction but no transactional context is available in
> message exchange with ID 110967726877695-59603-134659072536820180; will
> continue to send JMS message to JMS destination qError without participating
> in an XA transaction|#]
>
> I thought that the atomic property will enable XATransactions for the BPEL?
>
> What could be wrong?
>
> Thanks
>
> /Alex
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]
