JBoss 5.1.2 EAP doesn't start after moving to java 1.7

  • 7014451
  • 24-Jan-2014
  • 24-Jan-2014

Environment

Red Hat JBoss Enterprise Application Platform 5.1.2 Application Server
Identity Manager 4.0.2
Identity Manager Roles Based Provisioning Module 4.0.2
Identity Manager Roles Based Provisioning Module 4.0.2 Patch D

Situation

After the installation of RBPM 4.0.2 Patch D and moving from java jre / jdk 1.6 to java jre / jdk 1.7 Red Hat JBoss EAP 5.1.2 fails to start.

The following exception is shown while executing start-jboss.sh / start-jboss.bat:

Exception in thread "main" java.lang.NoClassDefFoundError: org/jboss/bootstrap/BaseServerConfig
    at org.jboss.bootstrap.AbstractServerImpl.doInit(AbstractServerImpl.java:190)
    at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:173)
    at org.jboss.bootstrap.AbstractServerImpl.init(AbstractServerImpl.java:143)
    at org.jboss.Main.boot(Main.java:218)
    at org.jboss.Main$1.run(Main.java:556)
    at java.lang.Thread.run(Thread.java:744)
Caused by: java.lang.ClassNotFoundException: org.jboss.bootstrap.BaseServerConfig
    at java.net.URLClassLoader$1.run(URLClassLoader.java:366)
    at java.net.URLClassLoader$1.run(URLClassLoader.java:355)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:354)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:425)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:358)

Resolution

Contact Red Hat and request patch: JBPAPP-8693

After the installation of patch JBPAPP-8693, the configuration file %jboss-install-folder%/server/%context%/deployers/jbossweb.deployer/META-INF/war-deployers-jboss-beans.xml has to be modified. The following section has to be commented out:

 <!--
            <entry>
               <key>SECURITY_DOMAIN</key>
               <value>org.picketlink.identity.federation.bindings.tomcat.PicketLinkAuthenticator</value>
            </entry>
 -->

After having made these changes the server should be able to start.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.