Archive for the ‘WebSphere’ Category
Request timeout due to the high load or the size of the requests
July 12th, 2010 | 
Author: IBM Technote# 1403094: Cause : unable to to respond within the default ORB request timeout due to the high load or the size of the requests.
Resolution: Increase the value of ORB timeout on WebSphere admin console >> Servers > Application servers > server_name > Container services > ORB service >> set “Request Timeout” parameter to new value. ( By default its 180 seconds, try increasing it a bit, for example try setting it to 600 seconds.)
[ Websphere Ref: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/uorb_rsetg.html ]
Posted in 
WebContainer thread pool to be equal at 50/50 min/max
Web container thread pool:
1. In the administrative console click Servers > Application Servers > server_name.
2. Near the bottom of the page, open Additional Properties, Thread Pools.
3. Click on WebContainer.
4. Change the Minimum Size field to whatever the Maximum is set to, probably 50.
5. Ensure that the “Allow thread allocation ?” checkbox is not checked [or that it is set to false].
6. Click OK and then save the configuration.
The application server will need to be restarted for the setting to take effect.
Restart WebSphere Dmgr
root path maybe different:
/usr/WebSphere/61/profiles/
- /AppSrv01/bin/stopNode.sh
- /Dmgr/bin/stopManager.sh
- /Dmgr/bin/startManager.sh
- /AppSrv01/bin/startNode.sh