Forgot to ask for you stateless container config (here with two important parameters for high load):
<Container id="My Stateless Container" type="STATELESS"> # Specifies the size of the bean pools for this stateless # SessionBean container. If StrictPooling is not used, instances # will still be created beyond this number if there is demand, but # they will not be returned to the pool and instead will be # immediately destroyed. MaxSize = 10 # StrictPooling tells the container what to do when the pool # reaches it's maximum size and there are incoming requests that # need instances. # # With strict pooling, requests will have to wait for instances to # become available. The pool size will never grow beyond the the # set MaxSize value. The maximum amount of time a request should # wait is specified via the AccessTimeout setting. # # Without strict pooling, the container will create temporary # instances to meet demand. The instances will last for just one # method invocation and then are removed. # # Setting StrictPooling to false and MaxSize to 0 will result in # no pooling. Instead instances will be created on demand and live # for exactly one method call before being removed. StrictPooling = true </Container> *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* 2012/9/21 Romain Manni-Bucau <[email protected]> > Hi, > > you log message is related to spring not tomee. > > Can you share a stack trace when it hangs? > > I think you can monitor stateless pool through JMX (at least on the > snapshot - here is the repo > https://repository.apache.org/content/groups/snapshots/org/apache/openejb/apache-tomee/1.5.1-SNAPSHOT/ > ) > > *Romain Manni-Bucau* > *Twitter: @rmannibucau* > *Blog: http://rmannibucau.wordpress.com* > *LinkedIn: http://www.linkedin.com/pub/romain-manni-bucau/43/544/956* > > > > > 2012/9/21 almos <[email protected]> > >> Hello, >> >> I have a question on tomee.xml configuration for highly loaded system. >> In my application all business logic is implemented in stateless EJB >> components. When load starts to grow, particular components stop >> responding >> to client requests, however others do fine and container continues >> working - >> for me it looks like pool of particular EJB components exceeded some max >> size and requests are hanging waiting for free resources. >> >> In logs there are no exceptions just this line each time I request >> "hanged" >> EJB: >> INFO: JSR-330 'javax.inject.Inject' annotation found and supported for >> autowiring >> >> This happens on TomEE v1.0 and ob nightly builds of Sep 9-10. >> The only way to restore operation is kill <tomee pid> because it's even >> impossible to stop it. >> >> Any comments/recommendations? >> >> Thanks, >> Alex >> >> >> >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/tomee-xml-configuration-for-high-load-tp4657577.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > >
