1 Reply Latest reply on Apr 11, 2003 9:39 AM by wimflam

    Problems getting started

    wimflam

      Hi everyone,
      I've managed to get nukes out of CVS.

      I've successfully built it and deployed it according to the instructions.

      However, when I go to http://localhost:8080/nukes/index.html,
      I get a blank screen.

      When I look at the logs, I see two problems.
      I get this during deployment:

      14:40:53,874 INFO [MainDeployer] Deployed package: file:/home/pete/jnuke/workspace/jboss-3.2.0RC4/server/default/deploy/nukes.ear
      14:40:53,875 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:
      ...


      and then when I try to access index.html:

      14:42:01,672 ERROR [NukeServlet] Cannot invoke core module because of runtime exception
      java.lang.IllegalArgumentException: bundle parameter cannot be null
      at org.jboss.nukes.io.handlers.ResourceBundleAdapter.(ResourceBundleAdapter.java:27)
      at org.jboss.nukes.html.Page.process(Page.java:317)
      at org.jboss.nukes.core.modules.core.CoreModule.process(CoreModule.java:1229)
      at org.jboss.nukes.core.modules.core.CoreModule.processPage(CoreModule.java:1130)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      ...

      I had a look at the code, and this looks like it has something to do with locale settings.

      I'm running jdk 1.4.1-b21 on a linux 2.4.19 kernel. My locale is set to en_GB.

      I running on JBoss3.2RC4

      Any ideas?

        • 1. Re: Problems getting started
          wimflam

          I answered my own question.

          The problem actually resided with the JBoss 3.2RC4 that I downloaded.

          It seems as though the WebService does something weird when binding its socket

          I solved the problem by explicity adding "localhost" to the bindaddress parameter of the web service mbean.