[jboss-dev-forums] [Design of POJO Server] - Re: Seam order or JBAS-5190

[alesj]

Here I see IndexerAction being bound to MC:

  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) installing bean: jboss.j2ee:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,name=IndexerAction,service=EJB3
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)   with dependencies:
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)   and demands:
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	persistence.units:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,unitName=dvdDatabase
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	jboss.ejb:service=EJBTimerService
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner)   and supplies:
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	jndi:IndexerAction/local
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	jndi:IndexerAction/local-com.jboss.dvd.seam.Indexer
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	Class:com.jboss.dvd.seam.Indexer
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) 	jndi:IndexerAction
  | 2008-06-09 14:08:38,963 INFO  [org.jboss.ejb3.deployers.JBossASKernel] (HDScanner) Added bean(jboss.j2ee:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,name=IndexerAction,service=EJB3) to KernelDeployment of: jboss-seam-dvd.jar
  | 2008-06-09 14:08:38,963 DEBUG [org.jboss.ejb3.Ejb3Deployment] (HDScanner) Bound ejb3 container jboss.j2ee:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,name=IndexerAction,service=EJB3
  | 
This is also what we had before, it was just that the ejb wasn't started soon enough.

But this is not the case here.
I can see this before the exception.
Starting Indexer ejb.

  | 2008-06-09 14:08:58,307 INFO  [org.jboss.ejb3.EJBContainer] (HDScanner) STARTED EJB: com.jboss.dvd.seam.IndexerAction ejbName: IndexerAction
  | 2008-06-09 14:08:58,307 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (HDScanner) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy
  | 2008-06-09 14:08:58,338 DEBUG [org.jboss.ejb3.proxy.factory.ProxyFactoryHelper] (HDScanner) Obtaining JNDI name from policy org.jboss.ejb3.jndipolicy.impl.PackagingBasedJndiBindingPolicy
  | 2008-06-09 14:08:58,338 DEBUG [org.jboss.ejb3.proxy.factory.stateful.BaseStatefulProxyFactory] (HDScanner) Binding reference for IndexerAction in JNDI at local
  | 2008-06-09 14:08:58,338 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (HDScanner) Storing sessions for 'IndexerAction' in: C:\projects\jboss5\trunk\build\output\jboss-5.0.0.CR1\server\default\tmp\sessions\IndexerAction-fh90tm1u-1v
  | 2008-06-09 14:08:58,338 DEBUG [org.jboss.ejb3.cache.simple.StatefulSessionFilePersistenceManager] (HDScanner) Purging all session data in: C:\projects\jboss5\trunk\build\output\jboss-5.0.0.CR1\server\default\tmp\sessions\IndexerAction-fh90tm1u-1v
  | 2008-06-09 14:08:58,338 DEBUG [org.jboss.ejb3.cache.simple.SimpleStatefulCache.IndexerAction] (HDScanner) Initializing SimpleStatefulCache with maxSize: 100000 timeout: 300 for jboss.j2ee:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,name=IndexerAction,service=EJB3
  | 

JNDI naming issue then?

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156693#4156693

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156693