Ours is a mammoth J2EE N-tier enterprise application built on WebSphere 3.5.6 platform (Solaris OS) with multiple clones running on different physical machines (horizontally & Vertically scaled).
Its a very transaction intensive application with highly demanding avalability & performance requirements.
At times, we are seeing a clone getting Auto-recycled (dies & comes back in a minute on its own). Under what circumstances do we see this recycling behaviour of a clone?
From our priliminary analysis, we could not see any reasons for this to happen. Traffic to the application was below normal level, no Db contention, no OSE buildup...etc.,
Please let us know if any one else ha experienced the same.
Ravi K Kakarla