I have the exact same exception when I try to access an EJB from a servlet.
I took our existing application that worked fine with Tomcat on a separate machine, and embedded tomcat into JBoss. When I try to get the Home object from a servlet the container throws the same exception from StatelessSessionContainer at line 593. To me, it seems this is a JBoss problem with embedded Tomcat. (Not a problem with tomcat itself.) Again, my application works fine with tomcat on a separate machine. Hope we can find a solution soon. -Dennis On Mon, 2002-04-08 at 09:18, James Higginbotham wrote: > Great, thanks for the info, it compiled! > > Now, however, I get the following error when my struts action attempts > to invoke an EJB.. I've used multiple J2EE containers and would assume > that I could get a servlet and EJB out there and working quickly.. My > unit tests show that I can talk to the EJBs in Jboss over RMI, so this > is a Catalina-specific error. I even see the EJBs in the JMS Agent view > (port 8082). > > I'm using the CVS code from March 30th.. I'm afraid to update right now, > due to the db configuration changed mentioned by David over the weekend > - I don't need any more variables interfering with my port at the > moment, unless the update is absolutely necessary. > > Any ideas what could be wrong? I've never struggled so much to get a > J2EE application working as with Jboss 3 beta. My apologies for the > continued emails, but I really need to get this working for our product. > > > Thanks, > James > > > ------------------- > > Here is the tracktrace: > > 2002-04-08 10:11:05,879 INFO > [org.jboss.web.catalina.EmbeddedCatalinaServiceSX] action: Creating > new Action instance > 2002-04-08 10:11:06,139 INFO [STDOUT] 10:11:06,129 ERROR > [UserManagerFactory] getUserManager caught RemoteException > java.rmi.ServerException: null; nested exception is: > java.lang.NullPointerException > java.lang.NullPointerException > at > org.jboss.ejb.StatelessSessionContainer$ContainerInterceptor.invokeHome( > StatelessSessionContainer.java:593) > at > org.jboss.resource.connectionmanager.CachedConnectionInterceptor.invokeH > ome(CachedConnectionInterceptor.java:167) > at > org.jboss.ejb.plugins.StatelessSessionInstanceInterceptor.invokeHome(Sta > telessSessionInstanceInterceptor.java:57) > at > org.jboss.ejb.plugins.AbstractTxInterceptor.invokeNext(AbstractTxInterce > ptor.java:98) > at > org.jboss.ejb.plugins.TxInterceptorCMT.runWithTransactions(TxInterceptor > CMT.java:167) > at > org.jboss.ejb.plugins.TxInterceptorCMT.invokeHome(TxInterceptorCMT.java: > 52) > at > org.jboss.ejb.plugins.SecurityInterceptor.invokeHome(SecurityInterceptor > .java:102) > at > org.jboss.ejb.plugins.LogInterceptor.invokeHome(LogInterceptor.java:109) > at > org.jboss.ejb.StatelessSessionContainer.invokeHome(StatelessSessionConta > iner.java:295) > at org.jboss.ejb.Container.invoke(Container.java:702) > at > org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:441) > at > org.jboss.invocation.local.LocalInvoker.invoke(LocalInvoker.java:98) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:1 > 02) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionInterceptor.jav > a:73) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) > at > org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:185) > at > org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:96) > at $Proxy33.create(Unknown Source) > at > com.betweenmarkets.user.client.EJBUserManagerFactory.getUserManager(EJBU > serManagerFactory.java:36) > at > com.betweenmarkets.usersecurity.DefaultUserSecurityContext.login(Default > UserSecurityContext.java:68) > at > com.betweenmarkets.transactionmanager.web.actions.LogonAction.handleRequ > est(LogonAction.java:77) > at > com.betweenmarkets.web.BaseAction.perform(BaseAction.java:179) > at org.apache.struts.action.Action.execute(Action.java:391) > at > org.apache.struts.action.ActionServlet.processActionPerform(ActionServle > t.java:2234) > at > org.apache.struts.action.ActionServlet.process(ActionServlet.java:2013) > at > org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:558) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:247) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:193) > at > com.betweenmarkets.web.accesscontrol.AccessControlServletFilter.doFilter > (AccessControlServletFilter.java:80) > at > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applica > tionFilterChain.java:213) > at > org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilt > erChain.java:193) > at > org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValv > e.java:243) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 > 72) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContextValve.invoke(StandardContextValv > e.java:190) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:566) > at > org.apache.catalina.valves.CertificatesValve.invoke(CertificatesValve.ja > va:246) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 > 72) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardContext.invoke(StandardContext.java:234 > 3) > at > org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java > :180) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:566) > at > org.apache.catalina.valves.ErrorDispatcherValve.invoke(ErrorDispatcherVa > lve.java:170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:564) > at > org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java > :170) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:564) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 > 72) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve. > java:174) > at > org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.ja > va:566) > at > org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:4 > 72) > at > org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) > at > org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.j > ava:1012) > at > org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java: > 1107) > at java.lang.Thread.run(Thread.java:484) > > > -----Original Message----- > > From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] > > Sent: Monday, April 08, 2002 1:34 AM > > To: James Higginbotham; [EMAIL PROTECTED] > > Subject: RE: [JBoss-user] Building Catalina .sar (Tomcat to > > work with JBoss Beta 2 HOWTO)? > > > > > > To build Catalina sar-file: > > > > In catalina directory (cvs directory structure) in build.xml > > you'll find: > > <!-- This corresponds to the tomcat4 dist existing in this > > module root --> <property name="tomcat.server.root" > > value="${module.root}/jakarta-tomcat-4.0.2"/> > > <path id="tomcat.server.classpath"> > > <pathelement path="${tomcat.server.root}/bin/bootstrap.jar"/> > > <pathelement path="${tomcat.server.root}/common/lib/servlet.jar"/> > > <pathelement path="${tomcat.server.root}/server/lib/catalina.jar"/> > > <pathelement path="${tomcat.server.root}/server/lib/warp.jar"/> > > </path> > > > > Well, this is the answer: copy catalina to > > ${module.root}/jakarta-tomcat-4.0.2 or change the value of > > tomcat.server.root accordingly. And in the jboss-service.xml > > you'll need to specify the catalina's home like this > > <!DOCTYPE server [ > > <!ENTITY catalina.home "c:\jakarta\jakarta-tomcat-4.0.2"> > > ]> > > > > Gooodluck, > > alex > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED]]On Behalf Of > > > James Higginbotham > > > Sent: Saturday, April 06, 2002 3:35 AM > > > To: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > > Subject: RE: [JBoss-user] Building Catalina .sar (Tomcat to > > > work with JBoss Beta 2 HOWTO)? > > > > > > > > > Funny, it was a conflict with log4j.. I had to rename our > > properties > > > file and all is well. Thanks for the verification that all > > it working. > > > > > > On to the next obstacle: Do you (or anyone reading this) > > know how to > > > build the sar file, as I have a CVS version of beta2, and the beta1 > > > sar doesn't seem to act happy - it can't locate a home that jetty > > > compiled for beta2 can. I tried using the build script to > > run ant in > > > the jboss-all/catalina, but I get compile errors > > everywhere. I wasn't > > > sure if this was a bad state that I checked out, or if I'm missing > > > some specific target in the root that I should be invoking to build > > > the catalina module. > > > > > > Thanks, > > > James > > > > > > > -----Original Message----- > > > > From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] > > > > Sent: Friday, April 05, 2002 11:10 AM > > > > To: James Higginbotham > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss Beta 2 HOWTO? > > > > > > > > > > > > Well, James... don't know what to suggest you except for > > > > asking you to send me your app to test in my environment. > > > > I do see any JSP compile errors in the browser. I use > > > > JBoss3.0.0beta2 with Catalina-4.0.2. > > > > > > > > alex > > > > > > > > > -----Original Message----- > > > > > From: James Higginbotham > > [mailto:[EMAIL PROTECTED]] > > > > > Sent: Friday, April 05, 2002 8:01 PM > > > > > To: [EMAIL PROTECTED] > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > Beta 2 HOWTO? > > > > > > > > > > > > > > > Pretty sure that struts is fine, since the app works under > > > > weblogic. > > > > > Jetty was giving me a 'id' attribute invalid for a custom > > > > JSP tag. The > > > > > problem is that I am trying to switch to Tomcat and cannot > > > > see any log > > > > > message or browser message about the error. Not sure what I > > > > am missing > > > > > to enable me to debug this same error in Tomcat. I can > > go back to > > > > > Jetty, but we want Tomcat rather than Jetty, so any work > > > done under > > > > > Jetty may or may not be a waste of time. > > > > > > > > > > So, given the configuration of the sar and jakarta-tomcat-4.0.2 > > > > > from the .zip download of Jboss of beta 1, you can deploy a war > > > > > and see JSP errors with no extra configuration, right? > > > > > > > > > > Any other thoughts? > > > > > James > > > > > > > > > > > -----Original Message----- > > > > > > From: Alex Loubyansky [mailto:[EMAIL PROTECTED]] > > > > > > Sent: Friday, April 05, 2002 10:53 AM > > > > > > To: James Higginbotham > > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > I use struts too and I've seen jsp's compile errors in the > > > > > > browser many times :) > > > > > > And I met blank pages without any errors and stack traces > > > > > > after successfull action operation. The cause was that I > > > > > > wrongly specified forward parameter (non existant). Are you > > > > > > sure it's not your case? > > > > > > > > > > > > alex > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: James Higginbotham > > > > [mailto:[EMAIL PROTECTED]] > > > > > > > Sent: Friday, April 05, 2002 7:42 PM > > > > > > > To: [EMAIL PROTECTED] > > > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > > > > The log dir isn't being created under Tomcat, and I > > think I'm > > > > > > > seeing JSP compile errors from a POST on a successful > > > > display of > > > > > > > the 1st JSP. However, there is no stacktrace for the compile > > > > > > > error. So, login works, > > > > > > > but the next page fails. I was seeing an error message in > > > > > > > Jetty and now > > > > > > > want to move to Tomcat (which is the preferred container) > > > > > but can't > > > > > > > debug the JSP problem (This page does work in Weblogic > > > > due to WL's > > > > > > > looser JSP parsing rules). Any ideas why I wouldn't be > > > > > seeing these > > > > > > > stacktraces, compile errors, since they are not showing in > > > > > > the browser > > > > > > > or in the Jboss server.log? > > > > > > > > > > > > > > James > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: Alex Loubyansky > > > [mailto:[EMAIL PROTECTED]] > > > > > > > > Sent: Friday, April 05, 2002 10:39 AM > > > > > > > > To: James Higginbotham > > > > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > > > > > > > Can't you find log dir? What do you mean? > > > > > > > > And what do you want to log? > > > > > > > > > > > > > > > > alex > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > From: James Higginbotham > > > > > > [mailto:[EMAIL PROTECTED]] > > > > > > > > > Sent: Friday, April 05, 2002 7:01 PM > > > > > > > > > To: [EMAIL PROTECTED]; > > > > > > > [EMAIL PROTECTED] > > > > > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > > > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > > > > > > > > > > Great, that worked, thanks! I hope these things get > > > > > > > > captured in 3.0.0 > > > > > > > > > docs soon. > > > > > > > > > > > > > > > > > > One more issue: I'm not seeing stack traces, but a POST > > > > > > > to a struts > > > > > > > > > action is returning an empty HTML page to the > > browser. I'm > > > > > > > > seeing the > > > > > > > > > log messages from Struts that use the > > > > > > > servletContext.log(), but not > > > > > > > > > any log4j specific stuff. I don't see any log dir or > > > > > > > files created > > > > > > > > > under jboss or tomcat, so I'm not sure where they are > > > > > > > > going. Is there > > > > > > > > > a specific setting within the sar or tomcat to fix this? > > > > > > > > > > > > > > > > > > Thanks again, > > > > > > > > > James > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: Alex Loubyansky > > > > > [mailto:[EMAIL PROTECTED]] > > > > > > > > > > Sent: Friday, April 05, 2002 12:07 AM > > > > > > > > > > To: James Higginbotham; > > [EMAIL PROTECTED] > > > > > > > > > > Subject: RE: [JBoss-user] Tomcat to work with JBoss > > > > > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > It's really easy with JBoss3.0.0beta. > > > > > > > > > > Just drop the tomcat4-service.sar into the deploy > > > > > > directory. And > > > > > > > > > > in the sar's jboss-service.xml you need to > > > > specify tomcat's > > > > > > > > > > home. That's it! :) > > > > > > > > > > > > > > > > > > > > alex > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > > > From: [EMAIL PROTECTED] > > > > > > > > > > [mailto:jboss-user-> [EMAIL PROTECTED]]On > > > > > Behalf Of > > > > > > > > > > James Higginbotham > > > > > > > > > > > > > > > > > > > > Sent: Friday, April 05, 2002 2:22 AM > > > > > > > > > > To: [EMAIL PROTECTED] > > > > > > > > > > Subject: [JBoss-user] Tomcat to work with JBoss > > > > > Beta 2 HOWTO? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > I've been looking through the volunteer documentation > > > > > > on the web > > > > > > > > > > site and mailing list archives, but haven't found a > > > > > page that > > > > > > > > > > describes how to configure 3.0.0 beta 2 to use > > > > > Tomcat 4.. Can > > > > > > > > > > someone point me to a past email that I've missed, to > > > > > > new docs, > > > > > > > > > > or provide a quick step-by-step on how to do this? > > > > > > I'm using the > > > > > > > > > > CVS code from last week (named beta 2 after > > > > > > > > > the build). > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > James > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > JBoss-user mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/jboss-user > > > > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user >
signature.asc
Description: This is a digitally signed message part
