2 Replies Latest reply on Feb 12, 2013 2:22 AM by snelders

    jira 5.1 on jboss 7.1

    lgl

      I tried to deploy jira 5.1 on jboss 7.1, but it failed.

      Need help, thanks.

       

      20:35:59,067 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-5) JBAS015876: Starting deployment of "atlassian-jira-5.1.2.war"

      20:36:15,155 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/bsh-1.2b7.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,156 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/GLUE-STD.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,158 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/quartz.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,159 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/osuser-1.0-dev-2Feb05.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,160 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/propertyset-1.4.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,162 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry lib/commons-logging.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,163 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry oscore-2.2.5.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/osworkflow-2.8.1.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,164 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry jakarta-oro.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,165 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry commons-logging.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,167 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry picocontainer.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,170 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry xercesImpl.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/xalan-2.7.0.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,171 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry xml-apis.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/xalan-2.7.0.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,174 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-6) Class Path entry serializer.jar in "/D:/jboss-as-7.1.1.Final/bin/content/atlassian-jira-5.1.2.war/WEB-INF/lib/xalan-2.7.0.jar"  does not point to a valid jar for a Class-Path reference.

      20:36:15,201 INFO  [org.jboss.as.jpa] (MSC service thread 1-6) JBAS011401: Read persistence.xml for propertyset

      20:36:16,302 INFO  [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-3) JNDI bindings for session bean named OSPropertySet in deployment unit deployment "atlassian-jira-5.1.2.war" are as follows:

       

          java:global/atlassian-jira-5.1.2/OSPropertySet!com.opensymphony.module.propertyset.ejb3.EJBPropertySet

          java:app/atlassian-jira-5.1.2/OSPropertySet!com.opensymphony.module.propertyset.ejb3.EJBPropertySet

          java:module/OSPropertySet!com.opensymphony.module.propertyset.ejb3.EJBPropertySet

          java:global/atlassian-jira-5.1.2/OSPropertySet

          java:app/atlassian-jira-5.1.2/OSPropertySet

          java:module/OSPropertySet

       

      20:36:16,325 WARN  [org.jboss.as.ee] (MSC service thread 1-3) JBAS011006: Not installing optional component webwork.view.taglib.ui.FragementTag due to exception: java.lang.ClassNotFoundException: webwork.view.taglib.ui.FragementTag from [Module "deployment.atlassian-jira-5.1.2.war:main" from Service Module Loader]

          at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:190) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:468) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:456) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClassChecked(ConcurrentClassLoader.java:423) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) [jboss-modules.jar:1.1.1.GA]

          at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:120) [jboss-modules.jar:1.1.1.GA]

          at java.lang.Class.forName0(Native Method) [rt.jar:1.6.0_30]

          at java.lang.Class.forName(Class.java:247) [rt.jar:1.6.0_30]

          at org.jboss.as.server.deployment.reflect.DeploymentClassIndex.classIndex(DeploymentClassIndex.java:54) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:79)

          at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:113) [jboss-as-server-7.1.1.Final.jar:7.1.1.Final]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]

       

      20:36:16,882 INFO  [org.jboss.as.jpa] (MSC service thread 1-8) JBAS011402: Starting Persistence Unit Service 'atlassian-jira-5.1.2.war#propertyset'

      20:36:16,883 INFO  [org.hibernate.ejb.Ejb3Configuration] (MSC service thread 1-8) HHH000204: Processing PersistenceUnitInfo [

          name: propertyset

          ...]

      20:36:16,927 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC00001: Failed to start service jboss.persistenceunit."atlassian-jira-5.1.2.war#propertyset": org.jboss.msc.service.StartException in service jboss.persistenceunit."atlassian-jira-5.1.2.war#propertyset": Failed to start service

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [rt.jar:1.6.0_30]

          at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [rt.jar:1.6.0_30]

          at java.lang.Thread.run(Thread.java:662) [rt.jar:1.6.0_30]

      Caused by: javax.persistence.PersistenceException: [PersistenceUnit: propertyset] Unable to build EntityManagerFactory

          at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:914)

          at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:889)

          at org.hibernate.ejb.HibernatePersistence.createContainerEntityManagerFactory(HibernatePersistence.java:73)

          at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.createContainerEntityManagerFactory(PersistenceUnitServiceImpl.java:162)

          at org.jboss.as.jpa.service.PersistenceUnitServiceImpl.start(PersistenceUnitServiceImpl.java:85)

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]

          ... 3 more

      Caused by: org.hibernate.AnnotationException: @org.hibernate.annotations.Table references an unknown table: PropertyEntry

          at org.hibernate.cfg.annotations.EntityBinder.processComplementaryTableDefinitions(EntityBinder.java:875)

          at org.hibernate.cfg.AnnotationBinder.bindClass(AnnotationBinder.java:710)

          at org.hibernate.cfg.Configuration$MetadataSourceQueue.processAnnotatedClassesQueue(Configuration.java:3406)

          at org.hibernate.cfg.Configuration$MetadataSourceQueue.processMetadata(Configuration.java:3360)

          at org.hibernate.cfg.Configuration.secondPassCompile(Configuration.java:1334)

          at org.hibernate.cfg.Configuration.buildSessionFactory(Configuration.java:1724)

          at org.hibernate.ejb.EntityManagerFactoryImpl.<init>(EntityManagerFactoryImpl.java:84)

          at org.hibernate.ejb.Ejb3Configuration.buildEntityManagerFactory(Ejb3Configuration.java:904)

          ... 9 more

       

      20:36:17,148 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) JBAS015870: Deploy of deployment "atlassian-jira-5.1.2.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"atlassian-jira-5.1.2.war#propertyset\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"atlassian-jira-5.1.2.war#propertyset\": Failed to start service"}}

      20:36:22,243 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) JBAS015877: Stopped deployment atlassian-jira-5.1.2.war in 5095ms

      20:36:22,245 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) JBAS014774: Service status report

      JBAS014777:   Services which failed to start:      service jboss.persistenceunit."atlassian-jira-5.1.2.war#propertyset": org.jboss.msc.service.StartException in service jboss.persistenceunit."atlassian-jira-5.1.2.war#propertyset": Failed to start service

       

      20:36:22,247 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 2) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.persistenceunit.\"atlassian-jira-5.1.2.war#propertyset\"" => "org.jboss.msc.service.StartException in service jboss.persistenceunit.\"atlassian-jira-5.1.2.war#propertyset\": Failed to start service"}}}}

        • 1. Re: jira 5.1 on jboss 7.1
          snelders

          I'm facing the same error with Jira 5.2.6 on JBoss 7.2.0.Alpha1. Did you manage to get this working?

          • 2. Re: jira 5.1 on jboss 7.1
            snelders

            Managed to get around this error by disabling JPA in the server config (standalone.xml).

            On JBoss 7.1.3.Final you will also run into this bug (AS7-5744) wich causes the deployment to fail due to the logging.properties in the JIRA war. You can get around this by disabling per-deployment (or upgrade to a newer version when it arrives)

             

            Ran into several other errors though... Seems like Atlassian only supports Tomcat for a reason.