0

A Heavy Request comes to application; deployed in my wildfly server; via HTTPD. It takes 5 minutes to process 800 Records in request. (Application calls 2 servers using Multithreading and concatenate results and send back)

Application run till end:

2022-03-14 15:06:21,545 INFO  [com.gvry.chintugrator.msc.service.ToneConfigurationItemSearchResource] (default task-1) Before Result With Status: 200
2022-03-14 15:06:21,545 INFO  [com.gvry.chintugrator.msc.service.ToneConfigurationItemSearchResource] (default task-1) Before Result With StatusInfo: OK
2022-03-14 15:06:21,545 INFO  [com.gvry.chintugrator.msc.service.ToneConfigurationItemSearchResource] (default task-1) Before Result With ToString: org.jboss.resteasy.specimpl.BuiltResponse@7779817c

@POST
@Produces({ MediaType.APPLICATION_JSON, MediaType.APPLICATION_XML })
@Path("/configuration-items")
public Response searchForConfigurationItems(ConfigurationItemsSearch search) {
 --after 5 to 6 mins
 --log(message and success))
 return Response.ok().entity(new GenericEntity<List<ConfigurationItem>>(configurationItems)
}

But after processing my Postman, ARC and client are getting "Error: read ECONNRESET" enter image description here

Strange thing is:

HTTPD log says 200 when i hit from both Postman and ARC

net.cosng.integrator.qa.masterdata_access.log:[14/Mar/2022:14:44:33 +0100] 253.110.6.132, 139.316.415.46, 410.0.11.23 (410.0.11.23) masterdata.qa.chintugrator.cosng.net 
"POST //mscbilling/api/search/configuration-items HTTP/1.1" 200 "PostmanRuntime/7.29.0"

HTTPD timeout is 900 seconds and request return in 5-6 minutes

ARC client has following in header.

enter image description here

Postman has following in header:

enter image description here

Then i downloaded Google Chrome ARC plugin and it returns 200 OK but

enter image description here

There is no issue in response json which i print in logs.

Where is the issue is

fatherazrael
  • 5,511
  • 16
  • 71
  • 155
  • Sounds like you open the response, send the 200 status and then start to send output a bit at a time, but the connection times out before the entire response is sent. That explains all the symptoms you see. – Jim Garrison Mar 14 '22 at 23:40
  • But Timeout is infinite on one place and 10 minutes on other. So what timed out? – fatherazrael Mar 15 '22 at 09:27

0 Answers0