|
From: Jan B. <ja...@we...> - 2007-09-09 23:51:40
|
Hi Christian, I guess you've already followed the instructions here: http://docs.codehaus.org/display/JETTY/JIRA Can you double-check that you've updated the web.xml files with the correct resource references, one pointing to jdbc/Jira and one to jdbc/JiraOld? Also you may need to check inside each jira webapp's WEB-INF/classes/entityengine.xml file to set the jndi-name appropriately for each webapp: <datasource name="defaultDS" field-type-name="hsql" 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" check-indices-on-start="true"> <jndi-jdbc jndi-server-name="default" jndi-name="java:comp/env/jdbc/JiraDS"/> cheers Jan Christian Meunier wrote: > Hi Jan, > > Basically, to enable a second instance of Jira, i add a webcontext and > add a jndi jdbc resource as follow below the existing one for the first > instance: > > First instance: > > <New id="jira-ds" class="org.mortbay.jetty.plus.naming.Resource"> > <Arg>jdbc/Jira</Arg> > <Arg> > <New class="com.atomikos.jdbc.nonxa.NonXADataSourceBean"> > <Set name="Url">jdbc:postgresql://127.0.0.1/jira</Set> > <Set name="driverClassName">org.postgresql.Driver</Set> > <Set name="user">jira</Set> > </New> > </Arg> > </New> > > Second instance: > > <New id="jira-old-ds" class="org.mortbay.jetty.plus.naming.Resource"> > <Arg>jdbc/JiraOld</Arg> > <Arg> > <New class="com.atomikos.jdbc.nonxa.NonXADataSourceBean"> > <Set name="Url">jdbc:postgresql://127.0.0.1/jira_old</Set> > <Set name="driverClassName">org.postgresql.Driver</Set> > <Set name="user">jira</Set> > </New> > </Arg > </New> > > Then when I start Jetty, the log says that a previous Jira database > schema was detected and then it says that Jira can not start because the > database is locked. > From my point of view, it's like the both instances use the very same > database somehow instead of using each their own. I can run both > instances separately just fine but issues arise when I try to have both > running in the same Jetty instance... > > Regards > Chris > > -----Original Message----- > From: jet...@li... > [mailto:jet...@li...] On Behalf Of Jan > Bartel > Sent: vendredi 7 septembre 2007 09:14 > To: Jetty usage, help & informal support > Subject: Re: [Jetty-support] Atomikos configuration for multiple webapps > with Jetty 6 > > Christian, > > When integrated with a j2ee container, the tx manager becomes a resource > for the whole container. Therefore there should only be once instance > of the tx manager and the atomikos config file per jetty installation. > > Each webapp can make use of the single tx manager. Can you describe > what is not working? > > cheers > Jan > > Christian Meunier wrote: >> Hi, >> >> I am trying to find out how to configure Atomikos under Jetty6.1.5 to >> work with multiple apps, for example, 2 instances of Atlassian Jira > (it >> works fine with one webapp). >> The first step seems to be able to give each webapp their own >> jta.properties / transactions.properties however, Atomikos does not >> detect them in the classpath ( Tried >> WEB-INF/classes,WEB-INF/lib,WEB-INF) >> >> Any ideas ? >> >> Thanks in advance >> Chris >> >> >> >> >> > ------------------------------------------------------------------------ > - >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a > browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Jetty-support mailing list >> Jet...@li... >> https://lists.sourceforge.net/lists/listinfo/jetty-support >> > > -- Jan Bartel, Webtide LLC | ja...@we... | http://www.webtide.com |