Hi
I've ben looking at Turbine as an alternate connection pool to
DBConnectionBroker, but can't get it working. According to the docs :
Build the pool using "build-turbine pool" which works fine.
I have included the jar in my wrapper.classpath on jserv.
I'm importing
org.apache.turbine.util.db.pool.*;
Then using the code:
try{
DBConnection db = DBBroker.getInstance().getConnection();
Connection Conn = db.getConnection();
......do other stuff
}catch (Exception e){
e.printStackTrace();
log("Exception: +e.getMessage(); //this reports NULL
}
The code is "stopping" after
DBConnection db = DBBroker.getInstance().getConnection();
But no exception is being thrown and neither my mod_jserv.log now
jserv.log nor turbine.log are reporting any errors. And the catch is
reporting NULL as the exception.getMessage().
I wasn't sure if I need to put my TurbineResources.Properties in the
turbine path or my servlet zone so I put it in both. But if the fiel
wasn't found then surely mod_jserv should show an exception with debug set
to info.
I know it is not a classpath problem since mod_jserv would tell me that. I
know it is not a file access problems since I am running on Win2KPro as
Administrator (my test system). If my database setup in TurbineResources
are wrong (which they aren't) then I would get an exception message ????
All other parts of all the servlets I run on this system are working just
fine.
Can anyone suggest what I have missed here? I'ts pretty hard to track it
down without an exception to go by.
Thanx.
Chris
On Tue, 05 Sep 2000 09:28:13 -0700, Josh Lucas wrote:
>Didier Dubois wrote:
>>
>> Daniel Rall wrote:
>> >
>> > Christopher Elkins wrote:
>> > > [snipped jon]
>> > > > once we have stable version of this stuff, we should probably also build a way
>> > > > for people to migrate to newer versions by doing upgrades. something like:
>> > > >
>> > > > newapp.sh scarab upgrade
>> > > >
>> > > > that way, it would take an existing application and upgrade it to the latest
>> > > > and greatest TDK.
>> > > >
>> > > +1
>> >
>> > +1. I vote that this should become part of the build process itself.
>> > Upgrade scripts should be checked in with every commit that could break
>> > someone's working Turbine instantiation. Running build-turbine.sh
>> > should automatically run the appropriate Ant tasks to upgrade a Turbine
>> > instantiation from one version to another. This is somewhat difficult
>> > in that just knowing the Turbine version doesn't really provide a known
>> > state, but it would be nice to have a program that would at least *try*
>> > to automate the upgrade, and let you know if you need to take manual
>> > steps if the upgrade could not be completed automatically. Let me know
>> > if you think I'm dreaming guys. ;)
>>
>> +1.
>> Suggestion: what about using a system like rpm? Cold this makes sense?
>> Didier
>>
>
>The problem with RPM is that it is not fully cross-platform. Obviously
>it works for Linux and I know it works for Solaris but what about Win
>users?
>
>Beyond that though, I am +1 on the suggestion. I would like to see a
>Turbine app 'know' about itself in such a way where it could be queried
>and return the appropiate version information. That would allow
>upgrades to occur seemlessly...
>
>
>josh
>
>
>------------------------------------------------------------
>To subscribe: [EMAIL PROTECTED]
>To unsubscribe: [EMAIL PROTECTED]
>Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
>Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
