Tim Haley [http://community.jboss.org/people/ymaraner] created the discussion
"Re: Random NameNotFoundException in jboss 6.1-SNAPSHOT" To view the discussion, visit: http://community.jboss.org/message/603781#603781 -------------------------------------------------------------- I am having the same issue. I see entries like this in my boot.log: {noformat} 12:49:01,125 INFO [EjbDeployer] installing bean: ejb/xyz.jar#StationHealthAuditTimer,uid917142622 12:49:01,126 INFO [EjbDeployer] with dependencies: 12:49:01,128 INFO [EjbDeployer] and supplies: 12:49:01,129 INFO [EjbDeployer] jndi:foobar/StationHealthAuditTimer/com.company.system.xyz.StationHealthAuditTimer 12:49:01,130 INFO [EjbDeployer] jndi:foobar/StationHealthAuditTimer/com.company.system.xyz.StationHealthAuditTimerLocal 12:49:01,131 INFO [EjbDeployer] jndi:ejb/StationHealthAuditTimerHome 12:49:01,132 INFO [EjbDeployer] jndi:ejb/StationHealthAuditTimerLocalHome {noformat} Then my @Startup bean (Lifecycle) in invoked: {noformat} 10:44:42,361 WARN [InterceptorInfoRepository] EJBTHREE-1852: InterceptorInfoRepository is deprecated 10:44:42,981 INFO [SingletonContainerDeployer] Installing container for EJB Lifecycle 10:44:42,981 INFO [SingletonContainerDeployer] with dependencies: 10:44:42,982 INFO [SingletonContainerDeployer] with demands: 10:44:42,984 INFO [SingletonContainerDeployer] with supplies: 10:44:42,999 INFO [SingletonBeanJNDIBinderDeployer] Binding the following entries in JNDI for singleton bean: Lifecycle 10:44:43,181 INFO [SessionSpecContainer] Starting jboss.j2ee:ear=foobar.ear,jar=ejb3SEE.jar,name=Lifecycle,service=EJB3 10:44:43,182 WARN [SessionSpecContainer] EJBTHREE-2126: container jboss.j2ee:ear=foobar.ear,jar=ejb3SEE.jar,name=Lifecycle,service=EJB3 does not verify the businessObjectFactory 10:44:43,185 INFO [EJBContainer] STARTED EJB: com.company.system.ejbvendor.jboss.Lifecycle ejbName: Lifecycle 10:44:43,196 WARN [TimerServiceContainer] EJBTHREE-2193: using deprecated TimerServiceFactory for restoring timers 10:44:44,030 INFO [STDOUT] Lifecycle.startup() executed {noformat} Eventually, my startup bean attempts to use a JNDI lookup (ejb/StationHealthAuditTimerHome) to access my 'StationHealthAuditTimer' bean, resulting in an error: {noformat} 10:44:45,078 INFO [STDOUT] javax.naming.NameNotFoundException: ejb not bound 10:44:45,079 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) 10:44:45,080 INFO [STDOUT] at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) 10:44:45,081 INFO [STDOUT] at org.jnp.server.NamingServer.getObject(NamingServer.java:785) 10:44:45,083 INFO [STDOUT] at org.jnp.server.NamingServer.lookup(NamingServer.java:396) 10:44:45,084 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:728) 10:44:45,085 INFO [STDOUT] at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:688) 10:44:45,086 INFO [STDOUT] at javax.naming.InitialContext.lookup(InitialContext.java:392) {noformat} later in the log I see this: {noformat} 10:44:51,188 INFO [BaseLocalProxyFactory] Bound EJB LocalHome 'StationHealthAuditTimer' to jndi 'ejb/StationHealthAuditTimerLocalHome' 10:44:51,196 INFO [ProxyFactory] Bound EJB Home 'StationHealthAuditTimer' to jndi 'ejb/StationHealthAuditTimerHome' {noformat} So, it looks like the 'StationHealthAuditTimer' bean is deployed and associated with the correct JNDI, but it is not actually bound to jndi until after my @Startup bean is invoked. Did something happen to change the timing of the invocation for a @Startupbean in JBoss AS 6.1 SNAPSHOT? This works correctly in JBoss AS 6.0.0 Final. Thanks, Tim -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/603781#603781] Start a new discussion in EJB3 at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2029]
_______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
