2 Replies Latest reply on Nov 15, 2007 10:47 AM by Kelly Dolan

    Invoker starting order  problem

    Sebastian Rzytki Newbie

      Hello
      This is continuation of thread posted few days ago - http://www.jboss.com/index.html?module=bb&op=viewtopic&t=85342

      After few tests I noticed when I start an server without ear application, and next deploy an application everything was ok.

      Below I showed standard output of jboss which starts with and without ear to show some my observation.

      Standard output of jboss starting with ear:

      13:27:47,633 INFO [DLQ] Bound to JNDI name: queue/DLQ
      13:27:47,823 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
      oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      13:27:47,894 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
      oss.jca:service=DataSourceBinding,name=APP_XMLDS' to JNDI name 'java:APP_X
      MLDS'
      13:27:47,924 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
      loy/jmx-console.war/
      13:27:48,084 INFO [EARDeployer] Init J2EE application: file:/E:/INSTALL/APP_RELEASE/OE 3.30 RC1 - SSL/OE SERVER/jboss-4.0.4RC1-OE/server/default/deploy/oe3
      .ear
      13:27:52,922 INFO [EjbModule] Deploying SystemChart
      ....
      ....
      ....
      ame=oe3/SessionController,service=EJB
      java.lang.RuntimeException: invoker is null: jboss:service=invoker,type=jrmp,soc
      ketType=SSL
       at org.jboss.proxy.ejb.ProxyFactory.setupInvokers(ProxyFactory.java:258)
      
       at org.jboss.proxy.ejb.ProxyFactory.start(ProxyFactory.java:242)
       at org.jboss.ejb.SessionContainer.startInvokers(SessionContainer.java:44
      0)
      .....
      .....
      .....
      
      
      ObjectName: jboss.j2ee:jndiName=ejb/ResponseSenderSessionBean,service=EJB
       State: FAILED
       Reason: java.lang.RuntimeException: invoker is null: jboss:service=invoker,typ
      e=jrmp,socketType=SSL
      ....
      ....
      ....
      ....
      09:12:39,758 INFO [STDOUT] com.sun.net.ssl.internal.ssl.SSLSessionContextImpl@4
       38d57
      09:12:40,519 INFO [SimpleThreadPool] Job execution threads will use class loade
      r of thread: Timer-4
      09:12:41,060 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0
      -8080
      09:12:41,230 INFO [QuartzScheduler] Quartz Scheduler v.1.5.1 created.
      09:12:41,230 INFO [RAMJobStore] RAMJobStore initialized.
      09:12:41,230 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
      r' initialized from default resource file in Quartz package: 'quartz.properties'
      
      09:12:41,230 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.1
      09:12:41,230 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
      TERED started.
      09:12:41,260 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      09:12:41,320 INFO [JkMain] Jk running ID=0 time=0/180 config=null
      09:12:41,330 INFO [Server] JBoss (MX MicroKernel) [4.0.4RC1 (build: CVSTag=JBos
      s_4_0_4_RC1 date=200602071519)] Started in 34s:639ms
      


      Standard output of jboss starting without ear:

      13:25:29,612 INFO [DLQ] Bound to JNDI name: queue/DLQ
      13:25:29,782 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
      oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      13:25:29,852 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
      oss.jca:service=DataSourceBinding,name=APP_XMLDS' to JNDI name 'java:APP_X
      MLDS'
      13:25:29,903 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
      loy/jmx-console.war/
      13:25:30,544 INFO [STDOUT] com.sun.net.ssl.internal.ssl.SSLSessionContextImpl@1
       af328
      13:25:30,974 INFO [Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0
      -8080
      13:25:31,175 INFO [ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      13:25:31,185 INFO [JkMain] Jk running ID=0 time=0/110 config=null
      13:25:31,195 INFO [Server] JBoss (MX MicroKernel) [4.0.4RC1 (build: CVSTag=JBos
      s_4_0_4_RC1 date=200602071519)] Started in 16s:128ms
      




      As you can see differences between that ouputs is line

      13:25:30,544 INFO [STDOUT] com.sun.net.ssl.internal.ssl.SSLSessionContextImpl@1
      af328


      I think problem is in invoker starting order, stateless-ssl-rmi-invoker is initalized after ear deploying.

      If anybody has any idea I'll be glad for help.

      Sebastian