Reliable SOAP messaging problems - weblogic.webservice.saf.StoreForwardException

Question

Hi Guys,
I'm playing with the new SOAP reliable message transport in WL 8.1 SP 1.
I have configured a simple web service, with void return, configured for
reliable messaging. I deploy the client to the same server as the server
hosting the webservice, and it uses the async invocation etc.
It wasn't obvious how to throw the exception in the backend implementation.
I simply grab the usertransaction
and call ut.setRollbackOnly(). Hope that's correct..
Whenever I invoke the operation, I get this:
weblogic.webservice.saf.StoreForwardException: Could not find MessageData
header in aknowledgement
I have a JMS file store setup, and I have it assigned to the server via the
services/webservice tab, and I do see some activity in the file store.
My client looks like this:
AsyncInfo asyncInfo = new AsyncInfo();
asyncInfo.setReliableDelivery(true);
FutureResult fr = port.startReliableOperation("hello World", asyncInfo);
System.err.println("Client: Made invocation, invoking async end now");
port.endReliableOperation(fr);
Any ideas?
Regards,
Jon
PS. [As an aside, aknowledgement needs a 'c']
Client: port.StartReliableOperation()
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
Client: Made invocation, invoking async end now
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
web
logic.webservice.saf.SAFHandler threw an exception from its handleResponse
metho
d. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from
its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception
was thrown from callReceive in the Client Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<26-Aug-2003 18:39:31 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
tra
ce associated with message 220047 follows:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.web
service.saf.StoreForwardException: Could not find MessageData header in
aknowled
gement. (see Fault Detail for stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.ja
va:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatche
r.java:119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(Conversatio
nAssembler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAss
embler.java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>

Answer 1

Hi Jon,
I've asked our WS RM guru to comment on your question, but I believe the
answer is going to be that you can explicitly roll back the transaction,
however only from the EJB application method, using the
EJBContext.setRollbackOnly() method.
Regards,
Bruce
Jon Mountjoy wrote:
>
Hi Bruce,
I looked at the example you pointed to, and it does what it says it does.
However, it doesn't attempt to rollback a transaction, which is what I am
doing.
The docs for reliable messaging say:
" If you want to roll back the transaction from the Java method, use the
Java Transaction API (JTA) to get the transaction object and then explicitly
roll back the transaction. "
They also indicate that the receiver executes in the context of a
transaction, which you may rollback.
For example, when the server is down, the transaction doesn't commit. This
behaviour is tested by your example, and it works.
However, when I modify your example to roll back the transaction in the web
service operation backend implementation,
then it doesn't. It yields the same exception that mine does.
For example, I modified your MarketService.java as indicated below to grab
the initial context and then during the operation grab the usertransaction
and call setRollbackOnly(). This causes WebLogic to throw a
weblogic.webservice.saf.StoreForwardException.
Any ideas?
Regards,
Jon
public final class MarketService {
private static boolean mustThrow = true;
InitialContext ctx = null;
public MarketService() {
try {
ctx = new InitialContext();
System.err.println("---InitialContext is set");
} catch (Exception e) {
System.err.println("---InitialContext is not set: " + e);
public void placeOrder(OrderInfo o) {
System.out.println("[MarketService] placing order: " + o);
mustThrow = !mustThrow;
if (mustThrow) {
System.out.println("--S:Going to roll back");
UserTransaction ut = null;
try {
ut = (UserTransaction) ctx.lookup(
"javax.transaction.UserTransaction");
System.out.println("--S: Set setRolbackOnly()");
ut.setRollbackOnly();
// <------------------------------------------
} catch (Exception e) {
System.err.println("--S: UT transaction error:" + e);
} else {
System.out.println("--S: -Not rolling back");
--S:In reliable TX operation
--S:Going to roll back
--S: Set setRolbackOnly()
--S: Finished Reliable operation
<29-Aug-2003 15:48:24 o'clock BST> <Info> <WebService> <BEA-220025> <Handler
weblogic.webservice.saf.SAFHandler threw an
exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.>
myserver:Info:Handler weblogic.webservice.saf.SAFHandler threw an exception
from its handleResponse method. The exceptio
n was:
javax.xml.rpc.JAXRPCException: Failed to handle the response.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220047> <A
exception was thrown from callReceive in the Clie
nt Dispatcher.>
myserver:Info:A exception was thrown from callReceive in the Client
Dispatcher.
<29-Aug-2003 15:48:25 o'clock BST> <Info> <WebService> <BEA-220034> <A stack
trace associated with message 220047 follow
s:
javax.xml.rpc.soap.SOAPFaultException: Exception during processing:
weblogic.webservice.saf.StoreForwardException: Could
not find MessageData header in aknowledgement. (see Fault Detail for
stacktrace)
at
weblogic.webservice.core.ClientDispatcher.receive(ClientDispatcher.java:285)
at
weblogic.webservice.core.ClientDispatcher.callReceive(ClientDispatcher.java:
119)
at
weblogic.webservice.saf.ConversationAssembler.getResponse(ConversationAssemb
ler.java:302)
at
weblogic.webservice.saf.ConversationAssembler.execute(ConversationAssembler.
java:536)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
>
myserver:Info:A stack trace associated with message 220047 follows: