1 Reply Latest reply on Feb 6, 2008 1:10 PM by ajaygautam

    InvocationLayer type=http does not start

    ajaygautam Feb 5, 2008 6:35 PM

      The problem: Invocation layer does not start

      2008-02-05 17:38:23,967 [main] ERROR URLDeploymentScanner - Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss.system:service=ServiceBindingManager
 State: CONFIGURED
 I Depend On:
 jboss.mq:service=InvocationLayer,type=HTTP

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
 State: NOTYETINSTALLED
 Depends On Me:
 jboss.system:service=ServiceBindingManager


      Setup:
      JBoss 4.0.5.GA deployed in a cluster on 2 separate redhat linux machines.

      Config:
      Based on "default" server, with additions for clustering.
      From jboss-service.xml: 
      <mbean code="org.jboss.services.binding.ServiceBindingManager"
 name="jboss.system:service=ServiceBindingManager">
 <depends>jboss.mq:service=InvocationLayer,type=HTTP</depends>
 <attribute name="ServerName">kiodex-ports</attribute>
 <!-- NOTE: jboss.server.home.url == ENV_HOME -->
 <attribute name="StoreURL">${jboss.server.home.url}/conf/port-bindings.xml</attribute>
 <attribute name="StoreFactoryClassName">
 org.jboss.services.binding.XMLServicesStoreFactory
 </attribute>
 </mbean>

      From port-bindings.xml: 
      <!-- ********************* jbossmq-httpil.sar **************** -->
 <service-config name="jboss.mq:service=InvocationLayer,type=HTTP"
 delegateClass="org.jboss.services.binding.AttributeMappingDelegate"
 >
 <delegate-config portName="URLPort"/>
 <binding port="24050"/>
 </service-config>


      Debugging effort
      There is nothing in the log that indicates why InvocationLayer fails to start. Before starting the server, I made sure that port 24050 was not bound. Even with log level set to DEBUG for "org.jboss.services", the logs do not point to any possible issues.

      One thing to note here is that this error happens only on one machine. The other machine on the cluster does not have this error in its logs.

      I already tried google and forums search, but did not find anything useful.

      I have been trying to find a reason for why this is failing for the past few hours. Any help / information / nudge in the right direction would be greatly appreciated.

      Thanks in advance

      Ajay

      • 981 Views
      • Tags: