Hi,
I am trying to have a local webservice running on Intalio engine using Axis2 and eclipse plug-in for Axis2 as described in the link at
http://bpms.intalio.com/reference-guides/generating-web-services-using...

Everything seems OK
- plug-in generating web services related java file from WSDL,
- ant building Jars,
- deploying web services archive to Intalio engine,
- using WSDL in workflow and
- finally deoplying workflow on Intalio engine.

After doing above when I try to start the workflow, I get read timeout from the service. I am uploading the webservice aar file along with my workflow. Can someone please take a look at it?

I had posted a similar post a while ago about remote webservice not responding when I try to start a workflow process using this remote webservice.

It did not let me upload aar file.

Dear Saroj,

Pls find the link bellow, InvokeTimeService
http://bpms.intalio.com/samples/invoke-timeservice-process.html

it calls 'external wsdl' within the intalio process The wsdl invoked is 'TimeService.wsdl' which contains an operation 'getCityTime()'.

this use case has pretty much simmilar behavious as yours.

pls download it and deploy on your system, Which works fine and also it will tell you more clearly about WSDL, Pls Read all the intruction given on the link above.


regards,
Naresh

Dear saroj,

The process as designed is correct. So you have to make sure that your web service is actually responding.

To test your webService separatly, you can use a tool like SoapUI. All you need to do is specify the wsdl, and the tool will automatically create a message that you can send to your WS .
If the WS answers correctly, then we have to check the wsdl you are providing.

If this does not solve the problem for you, please attach your aar and I will help you implement your process.

Cheers,
Ihab

Hi Ihab

I am also facing the same problem.

I have tried with both SendJMS (given @ http://bpms.intalio.com/reference-guides/generating-web-services-using... and HelloWorld (provided by Saroj).

Both web services are responding correctly; tested thru SoapUI (as suggested by you).

Hereby, I am attaching following detail for HelloWorld WS:

• soapui.png: Result snap-shot of SoapUI


• exception.png: Exception snap-shot given by Intalio BPMS – Server


• geronimo.log: Logs snippet of Intalio BPMN-Server


• HelloWorldService.aar: aar file as requested by you


• RadianceHello: Intalio BPMS – Developer project

Please let us know what we are missing.

Regards
bIREN

Hi,

the problem is the mapping that you did between the message "thisEventStartMessageRequest" and "intfGetNameRequestMsg".
What you wanted to do, is pass the string that you provide when you call the process, to the message that you sent to the Hello webService.
But instead of that, you copied the message ( and not the string ) that you send to the process, to the message (and not only the myname attribute) that you send to the WS.

So the structure of the message that you send to your WS is actually incorrect.

But why would this throw a read time out exception ?

This is how your process is designed:
1- you send to process a string.
2- the process will send this string to your WS.
3- your webservice will answer the process.
4- your process will send you the answer of the webService.

S in step 2 you send an incorrect message, which cause the webService to return a fault answer to the process. the process then stops, and he will not reach step 4.
Since your client ( the tool with which you send a call to the process , and in this case it is the bpms-console) did not receive an answer from the process, he will throw a read time out error.

Ok now you understand what caused the behavior, but how would you know that by your self?

First of all, if you look in the logs of the Axis2 where you are hosting your webservice, you will find something like this:
10:00:06,682 WARN [ExternalService] Fault response: faultType=(unkown)
http://www.w3.org/2005/08/addressing/faultwsa:ActionNotSupportedThe [action] cannot be processed at the receiver.



Which means that your webservice returned a fault. Which might be because of either:
1- your WS is not working as it should be.
2- the request that you send to your process is incorrect.

Since you tried your WS with soapUI and it worked, then the problem is probably number 2.
In soapUI, you have already an example of a correct message, so all you need to do is compare this one withthe one that the process sends to your WS.
To access this message, all you need to do is log in the bpms-console ( usually at http://localhost:8080/bpms-console ) , go to the instances section, click on the instance that you want to debug, and under the data tab, you can see all the messages that your process sends or receives.
And you are going to notice that your process sends this message:

name

whereas soapUI sends :


name

So you can see that the myname attribute is missing, because of the bad mapping in the process.

Another problem with your WS wsdl, is that the soapAction is empty ( so you need to go to the wsdl inside the aar, and specify a soapAtion and redeploy your aar).
the reason it works with soapUI, is that soapUI uses soap1.2 and therefore no soapAction is required.

Attached is the fix for the problem, I hope this helps.
Regards,
Ihab

I am attaching a zip with the process corrected, and with the