continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brett Porter <br...@apache.org>
Subject Re: configuration of jdbc URL in context.xml
Date Fri, 18 Sep 2009 13:11:29 GMT
Is there a "next exception" as it states? With Derby, common causes  
might be that another instance is connected to it at the same time  
(eg, the old standalone server).

- Brett

On 18/09/2009, at 10:53 PM, Martin Sudmann wrote:

> I get the trace below, but actually I a afraid that the problem  
> isn't really
> the DB access, as I got the same error later with relative paths as  
> well...
>
> 2009-09-15 17:11:57,175 [main] ERROR JPOX.RDBMS.Schema  - Failed
> initialising database. Please check that your database JDBC driver is
> accessible, and the database URL and userna
> me/password are correct. Exception : Cannot create  
> PoolableConnectionFactory
> (Failed to start database
> '/users/integ.continue/continuum/data/databases/continuum', see the  
> next ex
> ception for details.)
> org.apache.tomcat.dbcp.dbcp.SQLNestedException: Cannot create
> PoolableConnectionFactory (Failed to start database
> '/users/integ.continue/continuum/data/databases/continuum', see
> the next exception for details.)
>        at
> org.apache.tomcat.dbcp.dbcp.BasicDataSource.createDataSource 
> (BasicDataSource
> .java:1225)
>        at
> org.apache.tomcat.dbcp.dbcp.BasicDataSource.getConnection 
> (BasicDataSource.ja
> va:880)
>        at org.jpox.util.FailoverUtils.getConnection 
> (FailoverUtils.java:51)
>        at org.jpox.store.rdbms.RDBMSManager.<init>(RDBMSManager.java: 
> 244)
>        at sun.reflect.NativeConstructorAccessorImpl.newInstance0 
> (Native
> Method)
>        at
> sun.reflect.NativeConstructorAccessorImpl.newInstance 
> (NativeConstructorAcces
> sorImpl.java:39)
>        at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance 
> (DelegatingConstruc
> torAccessorImpl.java:27)
>        at java.lang.reflect.Constructor.newInstance(Constructor.java: 
> 513)
>        at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:73)
>        at
> org.jpox.store.StoreManagerFactory.getStoreManager 
> (StoreManagerFactory.java:
> 73)
>        at
> org.jpox.AbstractPersistenceManager.getStoreManager 
> (AbstractPersistenceManag
> er.java:295)
>        at
> org.jpox.AbstractPersistenceManager.<init> 
> (AbstractPersistenceManager.java:2
> 17)
>        at
> org.jpox.PersistenceManagerImpl.<init>(PersistenceManagerImpl.java:42)
>        at
> org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager 
> (PersistenceMana
> gerFactoryImpl.java:178)
>        at
> org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager 
> (PersistenceMana
> gerFactoryImpl.java:153)
>        at
> org.apache.continuum.dao.AbstractDao.getPersistenceManager 
> (AbstractDao.java:
> 178)
>        at
> org.apache.continuum.dao.AbstractDao.getPersistenceManager 
> (AbstractDao.java:
> 173)
>        at
> org.apache.continuum.dao.AbstractDao.getAllObjectsDetached 
> (AbstractDao.java:
> 153)
>        at
> org.apache.continuum.dao.AbstractDao.getAllObjectsDetached 
> (AbstractDao.java:
> 148)
>        at
> org.apache.continuum.dao.AbstractDao.getAllObjectsDetached 
> (AbstractDao.java:
> 143)
>        at
> org.apache.continuum.dao.SystemConfigurationDaoImpl.getSystemConfiguration 
> (S
> ystemConfigurationDaoImpl.java:52)
>        at
> org.apache.maven.continuum.configuration.DefaultConfigurationService.loadDat
> a(DefaultConfigurationService.java:707)
>        at
> org.apache.maven.continuum.configuration.DefaultConfigurationService.initial
> ize(DefaultConfigurationService.java:92)
>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>        at
> sun.reflect.NativeMethodAccessorImpl.invoke 
> (NativeMethodAccessorImpl.java:39
> )
>        at
> sun.reflect.DelegatingMethodAccessorImpl.invoke 
> (DelegatingMethodAccessorImpl
> .java:25)
>        at java.lang.reflect.Method.invoke(Method.java:597)
>
> Thx,
> Martin
>
> -----Message d'origine-----
> De : Brett Porter [mailto:brett@porterclan.net] De la part de Brett  
> Porter
> Envoyé : vendredi 18 septembre 2009 04:31
> À : users@continuum.apache.org
> Objet : Re: configuration of jdbc URL in context.xml
>
> What exception do you obtain? The Derby documentation indicates that
> an absolute path should work.
>
> - Brett
>
> On 16/09/2009, at 4:55 PM, Martin Sudmann wrote:
>
>> Hi all,
>>
>>
>>
>> I am running Continuum as a webapp on Tomcat.
>>
>> I first installed it as the standalone version (thus creating the
>> databases
>> in the continuum install directory), but now I want to run it as
>> a .war on
>> Tomcat.
>>
>> I don't know how to configure the JDBC URL correctly:
>>
>> I want to use the databases from the initial install (not inside the
>> Tomcat
>> directory), but when I use an absolute unix file path the logs say
>> that they
>> cannot find the database.
>>
>>
>>
>> <Context path="/continuum"
>>
>>
>> docBase="/users/integ.continue/tomcat/webapps/continuum/
>> continuum.war">
>>
>> <Resource name="jdbc/users"
>>
>>           auth="Container"
>>
>>           type="javax.sql.DataSource"
>>
>>           username="sa"
>>
>>           password=""
>>
>>           driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
>>
>>
>> url="jdbc:derby:/users/integ.continue/continuum/data/databases/
>> users;create=
>> false" />
>>
>> <Resource name="jdbc/continuum"
>>
>>           auth="Container"
>>
>>           type="javax.sql.DataSource"
>>
>>           username="sa"
>>
>>           password=""
>>
>>           driverClassName="org.apache.derby.jdbc.EmbeddedDriver"
>>
>>
>> url="jdbc:derby:/users/integ.continue/continuum/data/databases/
>> continuum;cre
>> ate=false" />
>>
>> ..
>>
>>
>>
>> Can anyone help me?
>>
>>
>>
>> Thanks,
>>
>> Martin
>>
>
>


Mime
View raw message