The SAS Deployment Wizard fails to start JBoss as a service under Windows. When this happens, the jboss_startMidtierServers_yyyy-mm-dd-hh.mm.ss.log shows the following error:

C:\Program Files\SAS\SASDeploymentManager\9.2\products\cfgwizard__92330__prt__xx__sp0__1\Utilities\webAppAntTasks_jboss.xml:1752: jboss startup failed, can't find http://localhost:8080

If this error occurs, you can usually fix the problem, as explained below. As such, you should leave the SAS Deployment Wizard running so you can click Retry in the wizard after you fix the problem.

To solve the problem, check the following items:

• Start Jboss via the SASServer.bat file in a command window. This action displays the reason that the server is not starting. If you are installing JBoss on a 64-bit platform, you might see the following error:

  Error occurred during initialization of VM
  Could not reserve enough space for object heap
  Could not create the Java virtual machine.
  Press any key to continue . . .
  

  This error indicates that the problem is most likely a result of having selected 32-bit Java JDK in the SAS Deployment Wizard. To resolve this error, install the Java 64-bit Java Development Kit (JDK). Then change the following line in the wrapper.conf file , located in JBOSS-installation_directory\server\SASServer1, so that it points to the 64-bit version of the Java JDK.

  wrapper.java.command=path_toU64-bit_JDK\bin\java
• You might also see the following error:

    CLASSPATH: C:\Java\jdk1.5.0_15\lib\tools.jar;C:\jboss-4.2.0.GA\bin\run.jar
  
  ===============================================================================
  
  javax.management.JMRuntimeException: Failed to load MBeanServerBuilder class org
  .jboss.system.server.jmx.MBeanServerBuilderImpl: java.lang.ClassNotFoundExceptio
  n: org.jboss.system.server.jmx.MBeanServerBuilderImpl
          at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServ
  erFactory.java:499)
          at javax.management.MBeanServerFactory.getNewMBeanServerBuilder(MBeanSer
  verFactory.java:530)
          at javax.management.MBeanServerFactory.newMBeanServer(MBeanServerFactory
  .java:304)
          at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFact
  ory.java:219)
          at javax.management.MBeanServerFactory.createMBeanServer(MBeanServerFact
  ory.java:180)
          at sun.management.ManagementFactory.createPlatformMBeanServer(Management
  Factory.java:264)
          at java.lang.management.ManagementFactory.getPlatformMBeanServer(Managem
  entFactory.java:512)
          at sun.management.jmxremote.ConnectorBootstrap.startLocalConnectorServer
  (ConnectorBootstrap.java:417)
          at sun.management.Agent.premain(Agent.java:92)
          at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
          at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
  java:39)
          at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
  sorImpl.java:25)
          at java.lang.reflect.Method.invoke(Method.java:585)
          at sun.management.Agent.startAgent(Agent.java:197)
  Caused by: java.lang.ClassNotFoundException: org.jboss.system.server.jmx.MBeanSe
  rverBuilderImpl
          at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
          at java.security.AccessController.doPrivileged(Native Method)
          at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
          at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
          at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
          at javax.management.MBeanServerFactory.loadBuilderClass(MBeanServerFacto
  ry.java:441)
          at javax.management.MBeanServerFactory.checkMBeanServerBuilder(MBeanServ
  erFactory.java:484)
          ... 13 more
  Exception thrown by the agent : javax.management.JMRuntimeException: Failed to l
  oad MBeanServerBuilder class org.jboss.system.server.jmx.MBeanServerBuilderImpl:
   java.lang.ClassNotFoundException: org.jboss.system.server.jmx.MBeanServerBuilde
  rImplPress any key to continue . . .
  

  This error indicates that the Java Virtual Machine (JVM) option =-Djboss.home.dir="path-to-JBoss-directory" has a trailing slash at the end of the path, as shown in this example:

  -Djboss.home.dir="C:\jboss-4.2.0.GA\"

  To resolve this error, remove the trailing slash from the path in the following line pf the wrapper.conf file that is found in lt;JBOSS_installation_directory;\server\SASServer1\:

  wrapper.java.additional.30=-Djboss.home.dir="C:\jboss-4.2.0.GA"

After you resolve these errors, click the Retry in the SAS Deployment Wizard to start the JBoss service.

Operating System and Release Information