I want to detect whether an EJB container(for ANY App Server) has "hung" or not. i.e. Having problems while service client requests, causing a time out of requests. Is there any universal method for knowing this across App servers?
P.S. Are EJB Request time outs a reliable and correct method for detecting such a problem
Message was edited by:
AUTOMATON
No, there is no universal method for determining this.If the server reaches this state it's either a vendor
implementation bug or the machine/JVM resources are not sufficient to handle your application
workload.Your best bet is to analyze the server logs and consult the Java EE server provider to
determine which it is and how to proceed.
From a spec perspective there is no such thing as an ejb request time out.Stateful session beans
can be removed due to timeout but that duration is typically configurable.
--ken
Thank you :)
So in short this is a very very rare occurance right? But let me understand this a bit more. I know that there are a certain number of EJB instances that are there in the EJB container pool to serivice incoming client requests. Of there are say 10 EJB instances but the server is getting 100 requests constantly, will that not create this problem? Getting the used instance count(readily available in servers lilke JBoss) I think is a pretty good measure of measuring how messed up the EJB container is? I have tried to do this through code, but I have not been able to come up with reliable and sure fire method to actually overload the EJB container this way. Am I on the right track?
