CXF/JAX-WS (or JAX-RS) async client can be a good start. Side note: rather than using strict pooling, putting a timeout of 0s and increasing the pool size until it fits your need is more accurate in general.
Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-11-26 16:11 GMT+01:00 hmtb <hmmahbo...@gmail.com>: > > > We have a web application that exposes rest services, In background of our > web service, we called a heavy soap web services. We use Apache tome 1.7.3 > version with jdk 7. > > When we have lots of requests, we get this message in logs: No instances > available in Stateless Session Bean pool. Waited 30 SECONDS > > After we searching in the internet, we find a solution that increase number > of threads and set false value for strict pooling in TOMEE configuration. > > By each changes in configuration of tomee, we have more problems and our web > application became disturbed and TOMEE did not return response to clients. > > The second solution was using async web service. > > Our question is that for implementation a client soap service, which library > in tomee we should use? Should we use Java 8 Async API or EJB 3.1 async or > Apache CXF async Soap Webservice client? > > Is there any optimal solution that it was tested? > > > > -- > Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html
