@ruimadaleno, you mean to say there is time taken at Broker side to send request to WAS ?
No he meant to say that maybe WAS is taking too long to process the requests...
What can you do to optimize WAS processing? Is there any caching going on? _________________ MQ & Broker admin
Yes....some of the requests are taking time to get response from WAS...I see some requests fetch more than 5 mins....which ultimately result in time out....I have anyway doubled the value of maxThreads and acceptCount now...and will verify whether the Connection refused (ie EG port 7800 not reachable) is still occuring....
The last time when they ran the load test with 1500 users for 3 hrs, they got Connection refused error 4000 times...
Also further adding to this what if I kept tcpNodelay = true at EG level for performance perspective, as the message size is very small....Currently the tcpNodelay is set to Platform default...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum