1 Reply Latest reply on Apr 6, 2008 6:18 AM by jaikiran pai

    Container not yet available problem

    Mike Ahlers Newbie

      Hi,

      Brief situation:

      A -> B (remote ejb lookup + invocation -> success)

      B performs some ejbTimer logic, in the timeout I proceed

      B -> A (remote ejb lookup + reflection/invocation -> fails due container not yet available)

      I'm using Jboss 4.2.2.GA and pass the JNDI properties, as well as the interface (name) and method from A to B. From there I do some reflection to invoke a method. A and B are seperate Jboss instances on a single machine, using virtual ip's.

      In a single JVM this works.

      At first I discovered I had to set a RMISecurityManager at both machines, a d so I did. Both sides have a all permission. Based on the fact I succeed from A to B I get the feeling this is done ok, but perhaps I forgot something?

      A snippet of the log/stacktrace:

      2008-04-04 18:38:42,497 DEBUG [org.jboss.ejb.txtimer.TimerImpl] setTimerState: in_timeout
      2008-04-04 18:38:42,531 WARN [org.jboss.ejb3.LocalProxy] Container jboss.j2ee:ear=phonemessage-1.0.0.ear,jar=phonemessage-engine-1.0.0.jar,name=CallHandlerServiceBean,service=EJB3,VMID=ff2143713a7260c3:-350bd643:1191a4ce5d2:-7ffd is not yet available
      2008-04-04 18:38:42,531 DEBUG [com.thespeechcorporation.service.timer.ScheduleBean] Lookup result (using: 127.0.0.106:1099): CallHandlerServiceBean
      2008-04-04 18:38:42,531 INFO [com.thespeechcorporation.service.timer.ScheduleBean] About to invoke a callback on: 'com.phonemessage.service.CallHandlerService'
      2008-04-04 18:38:42,531 WARN [org.jboss.ejb3.LocalProxy] Container jboss.j2ee:ear=phonemessage-1.0.0.ear,jar=phonemessage-engine-1.0.0.jar,name=CallHandlerServiceBean,service=EJB3,VMID=ff2143713a7260c3:-350bd643:1191a4ce5d2:-7ffd is not yet available

      and from there it breaks...

      Any suggestions? If more information is required, let me know and I can provide this.

      Thanks in advance,
      Mike Ahlers