This content has been marked as final.
Show 3 replies
-
1. Re: EJB3Trail problem
chrisxsb Oct 17, 2005 2:54 PM (in response to urswag)I get the same message in my browser. Additionally, in the server's log, I find this:
14:38:17,884 INFO [EARDeployer] Started J2EE application: file:/C:/jboss/jboss-4.0.3/server/default/deploy/EJB3Trail.ear
14:38:31,259 INFO [STDOUT] The isFirst variable is true
14:38:31,259 INFO [STDOUT] Populate the database tables
14:38:31,259 INFO [STDOUT] javax.naming.NameNotFoundException: trail.entity.basic.Calculator not bound
14:38:31,259 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:514)
14:38:31,259 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:522)
14:38:31,259 INFO [STDOUT] at org.jnp.server.NamingServer.getObject(NamingServer.java:528)
14:38:31,259 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:281)
14:38:31,697 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:610)
14:38:31,697 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
14:38:31,697 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:351)
14:38:31,697 INFO [STDOUT] at org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:64)
14:38:31,697 INFO [STDOUT] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
14:38:31,697 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
14:38:31,697 INFO [STDOUT] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
14:38:31,697 INFO [STDOUT] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
14:38:31,697 INFO [STDOUT] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
14:38:31,697 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
14:38:31,697 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
14:38:31,697 INFO [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
14:38:31,697 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:407)
14:38:31,697 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
14:38:31,697 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
14:38:31,697 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
14:38:31,697 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
14:38:31,697 INFO [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
14:38:31,697 INFO [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
14:38:31,697 INFO [STDOUT] at java.lang.Thread.run(Thread.java:595) -
2. Re: EJB3Trail problem
chrisxsb Oct 17, 2005 2:59 PM (in response to urswag)Some info about my environment might be nice...
I'm running on JBoss 4.0.3
Java 1.5.0_04-b05
Windows XP Pro
I just copied EJB3Trail.ear in server/default/deploy and then ran jboss using run.bat (no arguments). I then went to http://localhost:8080/EJB3Trail/ and I got the error messages mentioned above. -
3. Re: EJB3Trail problem
chrisxsb Oct 17, 2005 3:31 PM (in response to urswag)If I follow the instructions here:
http://docs.jboss.com/ejb3/app-server/tutorial/installing.html
(substituting 4.0.3 for 4.0.2) I'm able to get it to run, but I'm still seeing some errors in the JBoss log:
--- MBeans waiting for other MBeans ---
ObjectName: jboss.j2ee:service=EJB3,name=trail.injection.RecordManagerBean
State: FAILED
Reason: java.lang.RuntimeException: You did not specify a @Resource.mappedName() on javax.sql.DataSource trail.injection.RecordM
anagerBean.myDb and there is no binding for that enc name in XML
ObjectName: jboss.j2ee:service=EJB3,name=trail.slsb.CalculatorBean2
State: FAILED
Reason: javax.naming.NameAlreadyBoundException
--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.j2ee:service=EJB3,name=trail.injection.RecordManagerBean
State: FAILED
Reason: java.lang.RuntimeException: You did not specify a @Resource.mappedName() on javax.sql.DataSource trail.injection.RecordM
anagerBean.myDb and there is no binding for that enc name in XML
ObjectName: jboss.j2ee:service=EJB3,name=trail.slsb.CalculatorBean2
State: FAILED
Reason: javax.naming.NameAlreadyBoundException
(I see this error was also mentioned in this thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=70534 )