wsdoc job marked as FAILURE although job processes as expected

[Anon Anon]

I'm using Workload Automation AE and have a Web Service job scheduled to run 3 times a day. This job usually takes longer than 5 minutes to complete at which point AutoSys will change its Status to FAILURE although the work performed by this job completes successfully on the backend. If this job completes within 5 minutes AutoSys changes its status to SUCCESS. Initially, I believed that this was a timeout issue and could be resolved by setting the "Minutes to wait before terminating" to 10 but that didn't work. I've also tried to override the "Average run time" from 4 minutes to 8 minutes, but that didn't work. Is there anyway to resolve this issue? Here is the error message I receive:

 

Request execution failure

javax.xml.ws.WebServiceException: Error sending HTTP request

@at cybermation.commonservice.webservice.ws.binding.CybHttpSoapBinding.invoke(CybHttpSoapBinding.java:418)

@at cybermation.commonservice.webservice.ws.CybDocumentLiteralInvocator.invokeWS(CybDocumentLiteralInvocator.java:337)

@at cybermation.plugins.webservice.handler.CybWSDocLitHandler.call(CybWSDocLitHandler.java:416)

@at cybermation.plugins.webservice.handler.CybWSDocLitHandler.call(CybWSDocLitHandler.java:84)

@at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

@at java.util.concurrent.FutureTask.run(Unknown Source)

@at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

@at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

@at java.lang.Thread.run(Unknown Source)

Caused by: java.net.SocketException: Connection reset

@at java.net.SocketInputStream.read(Unknown Source)

@at org.apache.http.impl.io.AbstractSessionInputBuffer.fillBuffer(AbstractSessionInputBuffer.java:149)

@at org.apache.http.impl.io.SocketInputBuffer.fillBuffer(SocketInputBuffer.java:110)

@at org.apache.http.impl.io.AbstractSessionInputBuffer.readLine(AbstractSessionInputBuffer.java:264)

@at org.apache.http.impl.conn.LoggingSessionInputBuffer.readLine(LoggingSessionInputBuffer.java:115)

@at org.apache.http.impl.conn.DefaultResponseParser.parseHead(DefaultResponseParser.java:98)

@at org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:252)

@at org.apache.http.impl.AbstractHttpClientConnection.receiveResponseHeader(AbstractHttpClientConnection.java:281)

@at org.apache.http.impl.conn.DefaultClientConnection.receiveResponseHeader(DefaultClientConnection.java:247)

@at org.apache.http.impl.conn.AbstractClientConnAdapter.receiveResponseHeader(AbstractClientConnAdapter.java:219)

@at org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:298)

@at org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)

@at org.apache.http.impl.client.DefaultRequestDirector.tryExecute(DefaultRequestDirector.java:645)

@at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:464)

@at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:820)

@at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:754)

@at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:732)

@at cybermation.commonservice.transport.http.CybHTTPConnector.processWriteRequest(CybHTTPConnector.java:219)

@at cybermation.commonservice.transport.http.CybHTTPConnector.post(CybHTTPConnector.java:236)

@at cybermation.commonservice.webservice.ws.binding.CybHttpSoapBinding.invoke(CybHttpSoapBinding.java:413)

@at cybermation.commonservice.webservice.ws.CybDocumentLiteralInvocator.invokeWS(CybDocumentLiteralInvocator.java:337)

@at cybermation.plugins.webservice.handler.CybWSDocLitHandler.call(CybWSDocLitHandler.java:416)

@at cybermation.plugins.webservice.handler.CybWSDocLitHandler.call(CybWSDocLitHandler.java:84)

@at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)

@at java.util.concurrent.FutureTask.run(Unknown Source)

@at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

@at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

@at java.lang.Thread.run(Unknown Source)

[Steve Carrobis]

the key is Caused by: java.net.SocketException: Connection reset

 

similar to ftp reset by peer etc etc etc.. basically , yes you are timing out. But this could be on the webservice side as well.

Get network involved etc. and have you opened a ticket with CA yet ?

 

Good luck.

[Anon Anon]

Will do, haven't opened a ticket yet...this will be my first.

[Donny Osman]

hi, I am facing similar issue, any solution...

[Richard Kao]

Donny,
If the exception message is the same as the one in this thread "Caused by: java.net.SocketException: Connection reset" this means that the Web Service has closed the connection unexpectedly.  Connection reset means the server closed the connection improperly.  This is the same as disconnecting the network in the middle of the transaction.  I have typically seen this type of error when there is some network device which sits between the agent and the web service and the request is a long running request and the network device is closing the connection because it thinks the connection is idle.