So I have an application which runs fine in WS 4.0.1 Porting it into WS 5.1 we have strange problems. It appears that connections are not being freed, open file handles for WS user increases, which cases IHS to keep making more kids, until the whole machine is trashed.
The application has a servlet which creates a thread to determine if backend data sources are available. Every so many seconds the thread wakes up and tries to ping.
As I understand the world the new version of WS uses a new version of the Servlets specification does anyone know if this would make my servlet behave differently?
Please ignore post, I have no idea what I am talking about.
Did the Connection Pool settings get copied from the 4.x environment?
There are some new 5.x settings that may have inappropriate defaults for your app.
We just finished a 4->5 upgrade, and it was not particularly pretty.
We had problems with:
-CLASSLOADER policies. Default in 5 seems exactly backwards than in 4.
-Default XML parser
All configuration issues really, but they took time to figure out.
We has a "performance" problem. The contractors doing the 5 install tried to point the finger at the app, which had not changed significantly in about 10 months, and ran fine under 4.
We wrote a servlet that did nothing but sleep for 1 second. Loaded up the two environments running only that servlet, and got some metrics. So ..... net result is that 5 absolutely needs tuned after you initially install it.
If you are unable to get TCP connections, and are exceeding max open files (a Unix box I presume), you need to tune your TCP stack and the OS:
-Time sockets spend in CLOSE_WAIT status
-The OS value for 'ulimit -n' needs to be looked at. IBM makes certain recommendations for WAS, and many OS's have lower defaults.