Configure JIRA in a /jira context

[Alberto Ocaña da Costa]

Hi.

I've installed JIRA 5.0.6 in http://server:8080 and everything works fine. I've made the installation using the installer for Linux 64bits.

Now, I need to have JIRA deployed in /jira context (http://server:8080/jira). I was reading that this is made by defining a Context in server.xml

I've modified server.xml (/opt/atlassian/jira/conf/server.xml) and added the next line within <server port="8005" shutdown="SHUTDOWN"> section:

<context path="/jira" docbase="${catalina.home}/atlassian-jira" reloadable="false/">

I've restarted JIRA but when I do http://server:8080/jira I get:

Not Found (404)

/jira

Could not find what you were looking for. Maybe you should raise an issue.

What am I doing wrong?

Regards.

Alberto

[Pepe]

The path needs to be "/jira" not just "jira"

[Petra Vanickova]

hello, I have the same problem on ubuntu using jira 5.0.1 and binary installer. When using in server.xml

<Context docBase="${catalina.home}/atlassian-jira" path="" reloadable="false" useHttpOnly="true">
<Resource auth="Container" factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60" name="UserTransaction" type="javax.transaction.UserTransaction"/>
<Manager pathname=""/>
</Context>

I can see Jira at http://localhost:8080

but when i change the context path to jira, I am getting 400 on http://localhost:8080/jira

<Context docBase="${catalina.home}/atlassian-jira" path="jira" reloadable="false" useHttpOnly="true">
<Resource auth="Container" factory="org.objectweb.jotm.UserTransactionFactory" jotm.timeout="60" name="UserTransaction" type="javax.transaction.UserTransaction"/>
<Manager pathname=""/>
</Context>

Is there any fix for this?

Regards

p.

[Pepe]

@gareth - Don't walk away just yet. Sometimes setup issues come up that can make it frustrating but Answers will get you thru it. Are you having the same issue? If not start a new question and post your logs or other info that can help us help you debug. If all else fails shoot me an email if you want me to take a look (support@praecipio.com).

@aocana - Building on Joris' answer look in your logs to ensure that jira started up correctly. The "false/"> bit likely caused jira to fail to startup so even tho the process is running (as shown by ps aux) JIRA itself has not started.

[Gareth Hailey]

Bump! I am having same problem as OP. Windows 7 - very frustrating.

Please any ideas?

I'll spare the sob story about all the trouble we've had with JIRA set up so far... Suffice to say, that we are already leaning away from this software considering the amount of issues to set up and lack of supporting documentation from Atlassian for what seem to be common issues. Maybe it's just aimed at dedicated sysadmins who have a lot more knowledge than everyone in our company ??

Would love some help please!

[Deleted user]

First of all, the end of that line is saying 'false/">' while it probably should be 'false"/>' (or 'false">' if there's a separate closing tag) - if you copy-pasted it from the configuration file, that might be your problem.

Are you sure the docbase specified is the right one? The output of your 'ps auxfh' says catalina.home is /opt/atlassian/jira, so you're telling Tomcat that the docbase is /opt/atlassian/jira/atlassian-jira. Just to be sure :)

Besides that, I have reloadable set to true, and also crossContext=true and debug=5. That last one might help you finding out what's wrong in the logs maybe? Are the logs saying anything relevant at all?

[Pepe]

Did you change anything else? That looks right to me. Are you sure you don't have two JIRA processes running? In linux "ps aux | grep [j]ira" and ensure that there is only one JIRA instance running.