WLI: Can't call synchronous web services from async business process?

Question

I have three web services, X, Y, and Z, that I want to call from a business process B. X is asynchronous, Y and Z are synchronous. Therefore, B must be asynchronous. B is called from another business process, A, that must be synchronous. So, I have A call B synchronously using the SyncAsync pattern described in "Best Practices for Oracle WebLogic Integration Application Life Cycle". This worked fine in earlier development when I was only calling X from B. However, when I try to add synchronous calls to Y or Z and run A, I get the following error message from B:
com.bea.control.classic.ServiceControlException: Attempting to perform the client
callback 'doY' while servicing a blocking request from the same client.  This can
result in a deadlock condition.  An @jws:message-buffer tag should be placed on
the synchronous operation or on this callback.This is obviously an old error message, since it recommends an annotation in the old style. Anyway, what can I do? Shouldn't it be possible to invoke web services synchronously from process B? If so, then how? I don't know what synchronous operation it's talking about -- is it A's call to B? As for the callback, I don't see a separate callback. Annotating the SBControl's method with weblogic.jws.MessageBuffer did no good, and I can't use com.bea.control.annotations.MessageBuffer because the method doesn't return void. Can I make this work without rewriting B, and if so, how? It'd be nice if I could call X, and then call Y and Z while waiting for X's callback.
Alternatively, I could rewrite my processes so that A calls a new process C synchronously, which in turn calls B (which calls X), Y, and Z. That should work, right? Thanks for any help y'all can give me.

Answer 1

Greetings everyone,
We have found a solution to this problem, and it is very much like one offered by Trinidad, except there was some confusion in my understanding.
http://sql-patch/B1WS/webreferences/LoginService.wsdl
Indeed, the url http://localhost/Service.asmx appears in the WSDL files, as well as the web.config.
I changed it to http://sql-patch/B1WS/webreferences/LoginService.wsdl in the WSDL files only.  This did not work.
We then found it in the web.config file also, and changed it to http://sql-patch/B1WS/webreferences/LoginService.wsdl also.
The reason I was using this URL is because the files exist there.  Looking at IIS, there is no Service.asmx anywhere in the B1WS path, and this confused me.
This got us one step further, but now a new error was showing itself -- 405 Method Not Allowed.
It turns out that the URL we needed to change it to is this:
http://sql-patch/B1WS/Service.asmx
That is, we replace localhost with the name of the machine, and NOTHING else.
This seems to have solved it for us, and is hopefully useful for you.
Thanks all,
Mike