Clarity

We keep getting the below error when ever we try to execute our custom jobs in our CERT environment. But it runs fine in PROD. Are there any parameters or setting that might be causing the issue?

 
ERROR 2017-08-11 19:21:12,481 [Dispatch pool-4-thread-8 : bg@cerr500204.wal-mart.com (tenant=clarity)] loads.ResourceSync (clarity:scheduler:17245052__C47E2378-465B-445C-9390-C44570BF2242:Resource Sync) Fatal error occurred running the "Resource Sync" job:  [SOAPException: faultCode=SOAP-ENV:Client; msg=Error opening socket: java.net.SocketException: Connection reset; targetException=java.lang.IllegalArgumentException: Error opening socket: java.net.SocketException: Connection reset]      at org.apache.soap.transport.http.SOAPHTTPConnection.send(SOAPHTTPConnection.java:354)      at org.apache.soap.rpc.Call.invoke(Call.java:248)      at com.walmart.clarity.loads.xog.XOGInvoker.getSessionId(XOGInvoker.java:104)      at com.walmart.clarity.loads.xog.XOGInvoker.invoke(XOGInvoker.java:148)      at com.walmart.clarity.loads.data.ResourceDao.xogResources(ResourceDao.java:2079)      at com.walmart.clarity.loads.data.ResourceDao.updateResources(ResourceDao.java:1854)      at com.walmart.clarity.loads.ResourceSync.syncResources(ResourceSync.java:80)      at com.walmart.clarity.loads.ResourceSync.scheduledEventFired(ResourceSync.java:57)      at com.niku.njs.Dispatcher$BGTask.run(Dispatcher.java:367)      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)      at java.lang.Thread.run(Thread.java:745)

Hi Prasanth

Are  you running Jobs using SOAP connection or you are running process via Job. It definitely looks like something withing your network is blocking the SOAP calls via process. I would look along with network and DBA togethere

Regards
Suman Pramanik

Hi Prashanth,

When network latency issues exist, the Application Server might experience SOAP connectivity issues if a response is not received within the timeout limit. When it exceeds the timeout limit, the connection is thrown out by the server, causing it to not connect again.

you should use some packet tracing tool to identify where is it getting reset.