I just re-read this thread. Thanks for the additional detail. When the .war containing the EJB client starts (and gets stuck hanging), has the EAR file already been deployed?
Also, how is the servlet in your EJB client .war making the call - are you using the LocalInitialContextFactory, or remote? I'd suspect the latter may fail as the connector might not have started at that point. I'm a little swamped, but I'll put together a sample as soon as I can. Jon On Thu, Mar 14, 2019 at 1:00 PM zsaade <[email protected]> wrote: > Dear jgallimore > > Find below an example for an ejb remote client war (considering that you > have already an ejb (war file) deployed under <tomee-home>\webapps): > > 1-Create a Web Project > 2-Under the web project create a Servlet > 3-Inside the Servlet init Method lookup and call an ejb > > public void init() throws ServletException > { > //To Do Look up and call a method from a remote ejb. > } > > > 4-Inside the Web Project open web.xml file and add the below to let the > server start at the deploymnet event: > > <servlet> > <servlet-name>ServletName</servlet-name> > > <servlet-class>package.location.of.serfvlet.ServletName</servlet-class> > <load-on-startup>1</load-on-startup> > </servlet> > > 5-Export the web project as war file. > > 6-Make sure that the ejb project is already deployed and add the exported > war under <tomee-home>\webapps > > 7-The project will be able to start correctly (OK scenario) > > 8-Stop TomEE > > 9-Start TomEE the server will hang on EJB calling. > > > PS1: EJB project always start before the client project > PS2: I'm using apache-tomee-plume-7.1.0 > > if you need further details don't hesitate to contact me. > > Thanks in advance > > Best Regards > > > > -- > Sent from: > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html >
