1 Reply Latest reply on May 23, 2006 8:41 PM by George Moberly

    Can't use alternate ServiceBindingManager ports with DukesBa

    George Moberly Newbie

      I can run DukesBank following the Getting Started guide without any problems, until I try to use an alternate set of ports.

      If my jboss-server.xml contains this, it works fine (changed <> to [])
      ===================================================================
      [mbean code="org.jboss.services.binding.ServiceBindingManager"
      name="jboss.system:service=ServiceBindingManager"]
      [attribute name="ServerName"]ports-default[/attribute]
      [attribute name="StoreURL"]${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml[/attribute]
      [attribute name="StoreFactoryClassName"]
      org.jboss.services.binding.XMLServicesStoreFactory
      [/attribute]
      [/mbean]
      ===================================================================


      If I change this to
      ===================================================================
      [mbean code="org.jboss.services.binding.ServiceBindingManager"
      name="jboss.system:service=ServiceBindingManager"]
      [attribute name="ServerName"]ports-01[/attribute]
      [attribute name="StoreURL"]${jboss.home.url}/docs/examples/binding-manager/sample-bindings.xml[/attribute]
      [attribute name="StoreFactoryClassName"]
      org.jboss.services.binding.XMLServicesStoreFactory
      [/attribute]
      [/mbean]
      ===================================================================

      It will not deploy the DukesBank .ear file.


      The server.log shows that the naming service is running on port 1199 (as expected)
      ===================================================================
      2006-05-23 20:25:18,356 INFO [org.jboss.naming.NamingService] Started jndi bootstrap jnpPort=1199, rmiPort=1198, backlog=50, bindAddress=/0.0.0.0, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
      2006-05-23 20:25:18,366 DEBUG [org.jboss.naming.NamingService] InitialContext Environment:
      2006-05-23 20:25:18,366 DEBUG [org.jboss.naming.NamingService] key=java.naming.factory.initial, value=org.jnp.interfaces.NamingContextFactory
      2006-05-23 20:25:18,366 DEBUG [org.jboss.naming.NamingService] key=java.naming.factory.url.pkgs, value=org.jboss.naming:org.jnp.interfaces:org.jboss.naming:org.jnp.interfaces
      2006-05-23 20:25:18,366 DEBUG [org.jboss.naming.NamingService] Listening on port 1199
      2006-05-23 20:25:18,376 DEBUG [org.jboss.naming.NamingService] Started jboss:service=Naming
      ===================================================================

      But server.log also shows that SOMETHING is still trying to contact the default port 1099:
      ===================================================================
      2006-05-23 20:25:29,774 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to localhost:1099
      javax.naming.CommunicationException: Failed to connect to server localhost:1099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server localhost:1099 [Root exception is java.net.ConnectException: Connection refused: connect]]
      at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:254)
      at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1370)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:579)
      at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:572)
      at javax.naming.InitialContext.lookup(InitialContext.java:351)
      etc
      ===================================================================

      And these are rolled up with something like
      ===================================================================
      2006-05-23 20:26:16,894 ERROR [org.jboss.deployment.MainDeployer] could not start deployment: file:/C:/JBApps/DukesBank/v1_0/dev/dev02/jboss_402/server/default/tmp/deploy/tmp36565JBossDukesBank.ear-contents/app-client.jar
      org.jboss.deployment.DeploymentException: Failed to setup client ENC; - nested throwable: (javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out])
      at org.jboss.deployment.ClientDeployer.start(ClientDeployer.java:156)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:964)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:956)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:775)
      etc
      ===================================================================

      Please help!

      George.