Failed to enable Jira in JBoss

I'm with the error below trying deploy and enable of the jira in jboss. I'm using java 6, Jira 6 and Jboss Enterprise Application Plataform 6.2.0 GA and Oracle Linux 6. Please can help me.

Failed to enable jira.war.

Unexpected HTTP response: 500

Request

{

"address" => [("deployment" => "jira.war")],

"operation" => "deploy"

}

Response

Internal Server Error

{

"outcome" => "failed",

"failure-description" => {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./jira" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./jira: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context

Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}},

"rolled-back" => true

}

1 answer

0 vote

Jira 6.x is not supported on Java 6. You need to upgrade to Java 7.

ok, but, with Java 7 happens same error.

Ok, so what does the Jira log say?

log Jboss

--------------------------------------------------------------

13:08:00,235 INFO [org.jboss.as.server.deployment] (MSC service thread 1-10) JBAS015876: Starting deployment of "atlassian-jira-6.2.2.war" (runtime-name: "atlassian-jira-6.2.2.war")

13:08:09,673 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/bsh-1.2b7.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,673 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/GLUE-STD.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,674 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/quartz.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,674 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/osuser-1.0-dev-2Feb05.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,675 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/propertyset-1.4.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,675 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry lib/commons-logging.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,676 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry oscore-2.2.5.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/osworkflow-2.8.1.jar does not point to a valid jar for a Class-Path reference.

13:08:09,685 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry jakarta-oro.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar does not point to a valid jar for a Class-Path reference.

13:08:09,685 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry commons-logging.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar does not point to a valid jar for a Class-Path reference.

13:08:09,686 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry picocontainer.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/radeox-1.0b2-forked-22Apr2004.jar does not point to a valid jar for a Class-Path reference.

13:08:09,713 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry xercesImpl.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.

13:08:09,713 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry xml-apis.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.

13:08:09,714 WARN [org.jboss.as.server.deployment] (MSC service thread 1-15) JBAS015960: Class Path entry serializer.jar in /content/atlassian-jira-6.2.2.war/WEB-INF/lib/xalan-2.7.0.jar does not point to a valid jar for a Class-Path reference.

13:08:10,754 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-11) JBAS018568: Deployment "deployment.atlassian-jira-6.2.2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.

13:08:10,755 WARN [org.jboss.as.dependency.unsupported] (MSC service thread 1-11) JBAS018568: Deployment "deployment.atlassian-jira-6.2.2.war" is using an unsupported module ("org.joda.time:main") which may be changed or removed in future versions without notice.

13:08:11,631 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-4) JNDI bindings for session bean named OSPropertySet in deployment unit deployment "atlassian-jira-6.2.2.war" are as follows:

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

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

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

java:global/atlassian-jira-6.2.2/OSPropertySet

java:app/atlassian-jira-6.2.2/OSPropertySet

java:module/OSPropertySet

13:08:13,699 WARN [org.jboss.as.ee] (MSC service thread 1-6) JBAS011006: Not installing optional component webwork.view.taglib.ui.FragementTag due to an exception (enable DEBUG log level to see the cause)

13:08:13,863 INFO [org.jboss.web] (ServerService Thread Pool -- 60) JBAS018210: Register web context: /atlassian-jira-6.2.2

13:08:14,297 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/atlassian-jira-6.2.2]] (ServerService Thread Pool -- 60) JBWEB000287: Exception sending context initialized event to listener instance of class com.atlassian.jira.startup.LauncherContextListener: java.lang.NoSuchMethodError: org.joda.time.DateTime.now()Lorg/joda/time/DateTime;

at com.atlassian.jira.ComponentManager.initComponentContainer(ComponentManager.java:260) [classes:]

at com.atlassian.jira.ComponentManager.bootstrapInitialise(ComponentManager.java:172) [classes:]

at com.atlassian.jira.startup.BootstrapContainerLauncher.bootstrapJIRA(BootstrapContainerLauncher.java:51) [classes:]

at com.atlassian.jira.startup.BootstrapContainerLauncher.start(BootstrapContainerLauncher.java:31) [classes:]

at com.atlassian.jira.startup.DefaultJiraLauncher.preDbLaunch(DefaultJiraLauncher.java:93) [classes:]

at com.atlassian.jira.startup.DefaultJiraLauncher.access$000(DefaultJiraLauncher.java:32) [classes:]

at com.atlassian.jira.startup.DefaultJiraLauncher$1.run(DefaultJiraLauncher.java:80) [classes:]

at com.atlassian.jira.util.devspeed.JiraDevSpeedTimer.run(JiraDevSpeedTimer.java:34) [classes:]

at com.atlassian.jira.startup.DefaultJiraLauncher.start(DefaultJiraLauncher.java:76) [classes:]

at com.atlassian.jira.startup.LauncherContextListener.contextInitialized(LauncherContextListener.java:54) [classes:]

at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

at org.apache.catalina.core.StandardContext.start(StandardContext.java:3777) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]

at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

at org.jboss.threads.JBossThread.run(JBossThread.java:122)

13:08:14,328 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 60) JBWEB001103: Error detected during context /atlassian-jira-6.2.2 start, will stop it

13:08:14,348 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/atlassian-jira-6.2.2]] (ServerService Thread Pool -- 60) JBWEB000306: Exception sending context destroyed event to listener instance of class com.atlassian.jira.startup.LauncherContextListener: java.lang.NullPointerException

at com.atlassian.jira.startup.ActiveServicesLauncher.getSchedulerLauncher(ActiveServicesLauncher.java:64) [classes:]

at com.atlassian.jira.startup.ActiveServicesLauncher.stop(ActiveServicesLauncher.java:57) [classes:]

at com.atlassian.jira.startup.DefaultJiraLauncher.stop(DefaultJiraLauncher.java:151) [classes:]

at com.atlassian.jira.startup.LauncherContextListener.contextDestroyed(LauncherContextListener.java:89) [classes:]

at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:3427) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

at org.apache.catalina.core.StandardContext.stop(StandardContext.java:3920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

at org.apache.catalina.core.StandardContext.start(StandardContext.java:3839) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]

at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.3.0.Final-redhat-14.jar:7.3.0.Final-redhat-14]

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]

at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

at org.jboss.threads.JBossThread.run(JBossThread.java:122)

13:08:14,357 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 60) MSC000001: Failed to start service jboss.web.deployment.default-host."/atlassian-jira-6.2.2": org.jboss.msc.service.StartException in service jboss.web.deployment.default-host."/atlassian-jira-6.2.2": org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context

at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96)

at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_51]

at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_51]

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_51]

at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_51]

at org.jboss.threads.JBossThread.run(JBossThread.java:122)

Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context

at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161)

at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60)

at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93)

... 6 more

13:08:14,567 ERROR [org.jboss.as.server] (HttpManagementService-threads - 3) JBAS015870: Deploy of deployment "atlassian-jira-6.2.2.war" was rolled back with the following failure message:

{"JBAS014671: Failed services" => {"jboss.web.deployment.default-host.\"/atlassian-jira-6.2.2\"" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host.\"/atlassian-jira-6.2.2\": org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context

Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}}

13:08:15,029 INFO [org.jboss.as.server.deployment] (MSC service thread 1-13) JBAS015877: Stopped deployment atlassian-jira-6.2.2.war (runtime-name: atlassian-jira-6.2.2.war) in 461ms

I'm just with Jboss log. Dont have Jira log.

The error happens enabling application Jira in Jboss.

Ok, makes sense, it's not starting at all.

The problem here seems to be Jboss not providing the right effective classpaths for Jira to find all its dependent libraries.

How did you build the the war file you are deploying?

I'm using ./build.sh of the Jira for create the file .war

Ok good, and what instructions are you following to configure Jboss to use it?

Riiight, well, that's for Jira 4 and not 6, but I don't think it's that far off.

There is definitely something wrong with the class paths that Jboss is using and forcing onto Jira, but I'm not entirely sure what or how to fix them. It looks like it's not including the WEB-INF/lib but I really don't know. I'm tempted to say to try adding that explicitly to your environment (the PATH variable) to see if that helps, or at least provokes different errors. But I'm not sure.

I'm afraid the last time I used Jboss was a while ago, and I did have similar problems, and someone with more Jboss than me did something to the paths to fix it, but it's going back beyond what I can reliably recall.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Julia Dillon
Posted Tuesday in Jira

Tell us how your team runs on Jira!

Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...

233 views 1 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you