In our project we are using a web service and we are using web service transformer stage to call the web service.Our job design is given below
Seq File ->WSDL Transformer->XML file
Right now we are testing for a single invocation of web service.Initially we faced the firewall issue , and we resolved the issue,now we are able to connect to web service server from datastage server and we checked it using telnet.We are using key store file to do handshakes between web service and datastage.But now we are facing the below error
Service invocation exception: <Fault xmlns="http://schemas.xmlsoap.org/soap/envelope/">
<faultcode xmlns="">SOAP-ENV:Server</faultcode>
<faultstring xmlns="">A timeout occurred during processing</faultstring>
<faultactor xmlns="">/</faultactor>
<detail xmlns=""><text>Timeout. Broker did not provide a response within the specified time interval (180 seconds) (made it to flow: true)</text></detail>
</Fault>
at com.ascentialsoftware.wsclient.OperationCall.handleRemoteException(OperationCall.java:388)
at com.ascentialsoftware.wsclient.OperationCall.invoke(OperationCall.java:293)
at com.ascentialsoftware.wsclient.WebService.callServiceInternal(WebService.java:1685)
at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1591)
at com.ascentialsoftware.wsclient.WebService.callService(WebService.java:1544)
at com.ascentialsoftware.wspack.Transformer.process(Transformer.java:105)
at com.ascentialsoftware.jds.StageFactory.runStage(StageFactory.java:544)
at com.ascentialsoftware.jds.StageFactory.runTransformer(StageFactory.java:361)
Please help.
We are getting response from SOAP UI for the same input
A timeout occurred during processing-WSDL Transformer
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India
Host entry
Do we have to make a host entry for web service port address in datastage environment to resolve the time out issue?
Is your soapUI testing run on a Windows client or on your UNIX DataStage server? Testing this type of problem needs to be done from the server.
Usually timeouts indicate firewall blockages. If you are certain you have the firewall open, and you've tested the IP and port using telnet from the UNIX server, then I would suspect that the web service itself is timing out on the other end.
You might also want to involve your network team to monitor traffic and trace what's going on.
Usually timeouts indicate firewall blockages. If you are certain you have the firewall open, and you've tested the IP and port using telnet from the UNIX server, then I would suspect that the web service itself is timing out on the other end.
You might also want to involve your network team to monitor traffic and trace what's going on.
Choose a job you love, and you will never have to work a day in your life. - Confucius
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
It is sometimes very worthwhile to re-write your Job as a Server Job, using the WS Transformer Stage......do this for debugging purposes, because the WSTransformer in Server supports fully tracing capability....
Build the Job in Server, then compile and run it...and while on the "run" dialog, find the "Tracing" tab and then check your WS Transformer stage on the left, and all four boxes on the right.....
You will get a LOT of stuff in the log....and most importantly, in the very middle of all of that, you will get (hopefully) an entry for "xml" that is for the soap envelope going "OUT" and another for the soap envelope coming back "IN"......
That information may help determine where your timeout is.......if you never get a soap message back "in", then DataStage is stuck waiting and getting timed out....
...if the fault you are receiving is in the message in the way back "in", it may be that the web service host itself is waiting on something and getting timed out.
Ernie
Build the Job in Server, then compile and run it...and while on the "run" dialog, find the "Tracing" tab and then check your WS Transformer stage on the left, and all four boxes on the right.....
You will get a LOT of stuff in the log....and most importantly, in the very middle of all of that, you will get (hopefully) an entry for "xml" that is for the soap envelope going "OUT" and another for the soap envelope coming back "IN"......
That information may help determine where your timeout is.......if you never get a soap message back "in", then DataStage is stuck waiting and getting timed out....
...if the fault you are receiving is in the message in the way back "in", it may be that the web service host itself is waiting on something and getting timed out.
Ernie
Ernie Ostic
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
blogit!
<a href="https://dsrealtime.wordpress.com/2015/0 ... ere/">Open IGC is Here!</a>
-
- Participant
- Posts: 17
- Joined: Thu Jan 15, 2015 5:21 am
- Location: India