5 Replies Latest reply on Feb 12, 2004 10:13 AM by dreimer

    Server failed to start

    Chris Malan Novice

      This is where it hits the fan:

      15:35:05,890 INFO [MainDeployer] Starting deployment of package: file:/usr/ports/java/jboss3/work/
      15:35:05,904 ERROR [Server] Failed to start
      java.lang.AbstractMethodError: org/jboss/deployment/SubDeployerSupport.accepts
      at org.jboss.deployment.MainDeployer.findDeployer(MainDeployer.java:881)
      at org.jboss.deployment.MainDeployer.init(MainDeployer.java:680)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:637)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:613)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:597)
      at java.lang.reflect.Method.invoke(Native Method)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:549)

      This is for JBoss 3.2.1 running on FreeBSD 4.7 with Sun's JDK 1.3.1
      JBOSS_HOME and JAVA_HOME set and found on start-up as the jboss window indicates.

      Obviously, this points to jboss-service.xml I looked at that. Right in the beginning it says to uncoment an xml element if JDK 1.3.0 doesn't find editors, or the likes. Didn't look like it, but I uncommented and tried again - no go. The rest of the error output messages were not helpful.

      Any idea what is going on and how to fix it?


        • 1. Re: Server failed to start
          Juha Lindfors Master

          Looks like it might be a bug in JVM, maybe you can work around it by compiling JBoss from source.

          -- Juha

          • 2. Re: Server failed to start
            Chris Malan Novice

            Thanks Juha,

            Please bear with me, just like Homer Simpson I'm not very bright and both Homer and me know it.

            Isn't the JVM part of the JDK? Actually the JRE. If so, will changing anything in JBoss fix a faulty JVM? I know the J2EE parts are contained in JBoss.



            • 3. Re: Server failed to start
              Jon Barnett Master

              It may be due to a specific byte-code combination. So perhaps recompiling the source produces a different arrangement of the byte-code for your implementation.

              A few of the JDK 1.3.1 implementations seem to have varying success with JBoss. Notably, SCO's 1.3.1 09 seems to fail, as does the IBM 1.3.1 for later 3.2.x releases (and no hope for the SSL parts to work). Unfortunately, I seem to remember the BSD Java releases have been slow in coming and problematic with some J2EE implementations, JBoss included.

              • 4. Re: Server failed to start
                Chris Malan Novice

                Thanks Jonlee,

                It is clear you know what you are talking about.

                On another tack, it's hard to find reasonably priced hosts supporting JBoss in Aussie. I'm now with a host in the USA who charges slightly more than a third of what I would have to pay in Aussie. Everything works fine and fast. Setup over the wire wasn't too difficult, even though it is my first time.

                Both the reseller and me have given up on the FreeBSD based host.



                • 5. Re: Server failed to start
                  dreimer Newbie

                  I was having the same problem on SCO's 1.3.1_10 jre. The solution is to get the JBoss source and compile with the 1.3.1 sdk. Then everything works fine. I guess the compiled JBoss download was compiled with the 1.4 sdk.