Logs :-
<log4j:throwable><![CDATA[java.rmi.RemoteException:
EJB Exception: ; nested exception is:
java.lang.RuntimeException: An invocation of EJB <anonymous>.jar) timed out while waiting to get an instance from the free pool.
There were a whole lot of threads (70) in the Weblogic console related to EJB.jar - I could not see them getting processed.
From BEA
doc form BEA edoc:
A high pool timeout ratio could be indicative of an improperly sized free pool. Increasing the maximum size of your free pool via the max-beans-in-free-pool setting will increase the number of bean instances available to service requests and may reduce your pool timeout ratio.
Another factor affecting the number of pool timeouts is the configured transaction timeout for your bean. The maximum amount of time a
thread will wait for a bean from the pool is equal to the default transaction timeout for the bean. Increasing the trans-timeout-seconds setting in your weblogic-ejb-jar.xml file will give threads more time to wait for a bean instance to become available.
But its not the initial stage(application start up) where the Bean gets time out, its in the middle of the apllication where the users are accessing it.
Plese give me ideas how it happens and why ??