Nick,

Is this really a bug then?

If you put the WAR inside the web apps directory AND in it's own context, Tomcat is actually deploying it twice afaik. That means the error occurs because only one thing can grab the proper JNDI reference?

Cheers,
Mike

To reproduce:

Deploy the war version - put it under the tomcat/webapps dir.

So you probably have atlassian-jira-2.4.1.war (or something)

Now, in your tomcat server.xml, put

<Context path="/jira" docBase="atlassian-jira-2.4.1.war" ..../>

(you can also put "atlassian-jira-2.4.1" because tomcat will unpack the war)

Now, because "jira" and "atlassian-jira-2.4.1" are different, you will get this exception.

If you make them the same, then it will go away.
If you move the war outside of the webapps dir, then it will also go away.

-Nick

I have no idea about this one. I can't replicate on Tomcat 4.1.27. Apart from this bugreport I've not heard any users reporting this problem. Can someone provide more details on how to replicate this with the standalone distribution?

Marking as 'cannot reproduce' in the meanwhile.

Jeff,

Is this fixed now? If so - let's close out the issue.

Cheers,
Mike

Then you put reference in web.xml JIRA stile log wanrings, but work correctly...

So, to clear warnings you realy need to equal "path" to "docBase" in "Context". So, if you setup follow structure of tomcat:
[tomcatRoot]
[jira-backup]
[jira-index]
[jira-attachements]
[jira-webapp]

In server.xml
<Server ...>
<Service ...>
<Engine ...>
<Host appBase="jira-webapp" unpackWARs="false" autoDeploy="false" ...>
<Context path="" docBase="" reloadable="false" ...>
<Resource name="jdbc/JiraDS" auth="Container" type="javax.sql.DataSource"/>
<ResourceParams name="jdbc/JiraDS">
<parameter>
<name>factory</name>
<value>org.objectweb.jndi.DataSourceFactory</value>
</parameter>
<parameter>
<name>username</name>
<value>jira</value>
</parameter>
<parameter>
<name>password</name>
<value>jira</value>
</parameter>
<parameter>
<name>driverClassName</name>
<value>com.mysql.jdbc.Driver</value>
</parameter>
<parameter>
<name>url</name>
<value>jdbc:mysql://localhost:3306/jira?autoReconnect=true</value>
</parameter>

</ResourceParams>

<Resource name="UserTransaction" auth="Container" type="javax.transaction.UserTransaction"/>
<ResourceParams name="UserTransaction">
<parameter>
<name>factory</name>
<value>org.objectweb.jotm.UserTransactionFactory</value>
</parameter>
<parameter>
<name>jotm.timeout</name>
<value>60</value>
</parameter>
</ResourceParams>
</Context>
</Host>
</Engine>
</Service>
</Server>

Then it will be work fine, even without references in web.xml. But you must still have in entityengine.xml full JNDI name ("java:comp/env/jdbc/JiraDS")

<datasource name="defaultDS" field-type-name="mysql"
helper-class="org.ofbiz.core.entity.GenericHelperDAO"
check-on-start="true" use-foreign-keys="false"
use-foreign-key-indices="false"
check-fks-on-start="false"
check-fk-indices-on-start="false"
add-missing-on-start="true">
<jndi-jdbc jndi-server-name="default" jndi-name="java:comp/env/jdbc/JiraDS"/>

</datasource>

Good luck!

Very stange, but you not need to change path to docBase the same. Just put in web.xml such entry:
<!-- resource references -->
<resource-ref>
<description>DB Connection</description>
<res-ref-name>jdbc/JiraDB</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>

As it described in Tomcat documentation...

I think I have worked out the problem with this:

You are looking up java:comp/env - and you dont have any <resource-ref> elements in your web.xml

(How does it work at all?)

Thanks for the work-around information Nick!

BUT,

In fact, this same problem seems to exist with Resin - so its not exclusive to Tomcat!

-Nick

It seems that this is a problem with Tomcat (or is it).

See here for a workaround;

http://forums.atlassian.com/thread.jsp?forum=46&thread=2308&message=28148146&q=%22Failed+to+find+DataSource%22#28148146

-Nick