Uploaded image for project: 'JBoss Web Services'
  1. JBoss Web Services
  2. JBWS-1006

JBossWS does not deploy on an installer generated JBoss 4.0.4.GA instance

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • jbossws-1.0.2
    • jbossws-1.0.1
    • None
    • None
    • Hide

      The workaround is to cust and paste all of the mbean configurations from the deploy/naming-service.xml and put them in conf/jboss-service.xml at the bottom. Also, make sure that after you have pasted these entries in jboss-service.xml, that you delete the naming-service.xml file.

      For example:

      <mbean code="org.jboss.naming.NamingService"
      name="jboss:service=Naming"
      xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
      <!-- The call by value mode. true if all lookups are unmarshalled using
      the caller's TCL, false if in VM lookups return the value by reference.
      -->
      <attribute name="CallByValue">false</attribute>
      <!-- The listening port for the bootstrap JNP service. Set this to -1
      to run the NamingService without the JNP invoker listening port.
      -->
      <attribute name="Port">1099</attribute>
      <!-- The bootstrap JNP server bind address. This also sets the default
      RMI service bind address. Empty == all addresses
      -->
      <attribute name="BindAddress">${jboss.bind.address}</attribute>
      <!-- The port of the RMI naming service, 0 == anonymous -->
      <attribute name="RmiPort">1098</attribute>
      <!-- The RMI service bind address. Empty == all addresses
      -->
      <attribute name="RmiBindAddress">${jboss.bind.address}</attribute>
      <!-- The thread pool service used to control the bootstrap lookups -->
      <depends optional-attribute-name="LookupPool"
      proxy-type="attribute">jboss.system:service=ThreadPool</depends>
      </mbean>

      <mbean code="org.jboss.naming.JNDIView"
      name="jboss:service=JNDIView"
      xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml">
      </mbean>

      Show
      The workaround is to cust and paste all of the mbean configurations from the deploy/naming-service.xml and put them in conf/jboss-service.xml at the bottom. Also, make sure that after you have pasted these entries in jboss-service.xml, that you delete the naming-service.xml file. For example: <mbean code="org.jboss.naming.NamingService" name="jboss:service=Naming" xmbean-dd="resource:xmdesc/NamingService-xmbean.xml"> <!-- The call by value mode. true if all lookups are unmarshalled using the caller's TCL, false if in VM lookups return the value by reference. --> <attribute name="CallByValue">false</attribute> <!-- The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port. --> <attribute name="Port">1099</attribute> <!-- The bootstrap JNP server bind address. This also sets the default RMI service bind address. Empty == all addresses --> <attribute name="BindAddress">${jboss.bind.address}</attribute> <!-- The port of the RMI naming service, 0 == anonymous --> <attribute name="RmiPort">1098</attribute> <!-- The RMI service bind address. Empty == all addresses --> <attribute name="RmiBindAddress">${jboss.bind.address}</attribute> <!-- The thread pool service used to control the bootstrap lookups --> <depends optional-attribute-name="LookupPool" proxy-type="attribute">jboss.system:service=ThreadPool</depends> </mbean> <mbean code="org.jboss.naming.JNDIView" name="jboss:service=JNDIView" xmbean-dd="resource:xmdesc/JNDIView-xmbean.xml"> </mbean>

      There is a dependancy ordering issue on installer based AS instances. Installer based builds load the naming service after jbossws, which is a problem for this release because there is no jmx dependancy on the naming service. See comments for current workaround:

      2006-06-13 08:56:59,336 INFO [org.jboss.remoting.transport.socket.SocketServerInvoker] Invoker star
      ted for locator: InvokerLocator [socket://192.168.111.154:3873/]
      2006-06-13 08:56:59,664 INFO [org.jboss.aop.deployment.AspectDeployer] Deployed AOP: file:/C:/jboss
      -4.0.4.GA/server/default/deploy/ejb3-interceptors-aop.xml
      2006-06-13 08:57:06,191 ERROR [org.jboss.kernel.plugins.dependency.AbstractKernelController] Error i
      nstalling to Start: name=SubscriptionManager state=Create mode=Manual requiredState=Installed
      javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutExce
      ption: Receive timed out]
      at org.jnp.interfaces.NamingContext.discoverServer(NamingContext.java:1317)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1446)
      at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:484)
      at org.jnp.interfaces.NamingContext.rebind(NamingContext.java:477)
      at javax.naming.InitialContext.rebind(InitialContext.java:367)
      at org.jboss.util.naming.Util.rebind(Util.java:126)
      at org.jboss.util.naming.Util.rebind(Util.java:113)
      at org.jboss.ws.eventing.mgmt.SubscriptionManager.start(SubscriptionManager.java:149)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:585)
      at org.jboss.joinpoint.plugins.reflect.ReflectMethodJoinPoint.dispatch(ReflectMethodJoinPoint.java:
      72)

              rhn-support-hbraun Heiko Braun
              jgreene@redhat.com Jason Greene
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: