Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-4106

run.bat generates failed deployment on startup on Windows

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • 4.3.0.GA_CP08
    • 4.3.0.GA_CP08
    • Clustering
    • None
    • Windows 2003, x86, JDK 5

      Starting the application server with
      > run.bat -c all -b <non-loopback IP address>
      causes server startup to progress normally until the point at which the farm service starts to pull deployments:

      09:56:20,424 INFO [FarmMemberService] **** pullNewDeployments ****
      09:56:20,424 INFO [ClusterFileTransfer] Start pull of file cluster-examples-service.xml from cluster.
      09:56:20,440 INFO [ClusterFileTransfer] Finished cluster pull of file cluster-examples-service.xml to cluster-examples-service.xml
      09:56:20,440 INFO [ClusterFileTransfer] Start pull of file destinations-farm-service.xml from cluster.
      09:56:20,455 INFO [ClusterFileTransfer] Finished cluster pull of file destinations-farm-service.xml to destinations-farm-service.xml
      09:56:20,455 INFO [ClusterFileTransfer] Start pull of file stateless-clustered example.jar from cluster.
      09:56:20,455 INFO [ClusterFileTransfer] Finished cluster pull of file stateless-clustered-example.jar to stateless-clustered-example.jar
      09:56:20,486 INFO [QueueService] Queue[/queue/testFarmQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000
      09:56:20,690 WARN [LoadMgr3] Not resheduling failed loading task, loadTask=org.jboss.mx.loading.ClassLoadingTask@55ff4{classname: org.jboss.example.jms.statele
      ssclustered.bean.StatelessClusteredSessionExampleBean, requestingThread: Thread[main,5,jboss], requestingClassLoader: org.jboss.mx.loading.UnifiedClassLoader3@f52ed

      { url=file:/W:/rachmatowicz/jboss-eap-4.3.0.GA_CP08/jboss-eap-4.3/jboss-as/server/all/tmp/deploy/tmp3296406267388750333stateless-clustered-example.jar ,addedOrder=48}

      , loadedClass: nullnull, loadOrder: 2147483647, loadException: java.lang.UnsupportedClassVersionError: Bad version number in .class file, threadTaskCount: 0, state: 1, #CCE: 1}
      java.lang.UnsupportedClassVersionError: Bad version number in .class file

      Looks to be a problem with class versioning.

      The compiler used for starting the server:

      W:\jboss-eap-4.3.0.GA_CP08\jboss-eap-4.3\jboss-as\bin>hostname
      dev29
      W:jboss-eap-4.3.0.GA_CP08\jboss-eap-4.3\jboss-as\bin>java -version
      java version "1.5.0_22"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03)
      Java HotSpot(TM) Client VM (build 1.5.0_22-b03, mixed mode)

              bstansbe@redhat.com Brian Stansberry
              rachmato@redhat.com Richard Achmatowicz
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: