0. For now, do not set the timeout on the client side.
1. Check the server side log. Ask the provider have a check.
There might be log on the web container side or server side. That might give some clue.
2. Number checking:
I do not know the technical environment of your specific situation. So are Hypothetical questions:
Imagined Process Flow:
Client --- Server side ---Use JMS --- Use Database
Under normal condition, every thing is OK. Meaning the app was designed for a certain N concurrent requests withing a certain time frame.
It might work, three year ago but not now due to growth of work load N+M concurrent requests.
If during the process, if Database or JMS or Web container can not handle N+M concurrent users then Client is in trouble.
For web container, check number of concurrent
thread it can handle.
For Database, number of concurrent connection, was there any deadlock.
For JMS, if the queue is full.
If none of these has any issue, then consider review the whole process flow again - client + server or do some bandage.