The name is not defined correctly in that context.
What kind of a resource is it ?
Context path=/admin docBase=sfadmin debug=1
Resource name=jdbc/larco auth=Container
type=javax.sql.DataSource/
ResourceParams name=jdbc/larco
The server.xml looks right .
What about the web.xml in your webapp ?
How does it look like ?
The strange thing is, I don't have it defined in the web.xml.
That is because as soon as I do it I got a jdbc connection 'null' can't be
loaded or something like that.
But I had it working w/ out it
Sure it won't work.
Check out the res-ref-name. Here you claim it is admin/larco , but in
server.xml you tell tomcat it is jdbc/larco. So if you do a lookup for
jdbc/larco or admin/larco the name is not bound to the context.
admin/larco should be jdbc/larco.
Make the changes and see if it
Sounds like you don't have the appropiate driver loaded or you have
incorrectly specified your pgsql driver in server.xml. Double check the
values. I make that mistake alot.
I have gotten that answer like 10 times now :(
I have the correct driver specified :)
I must have because I had this all
David Durst wrote:
Sounds like you don't have the appropiate driver loaded or you have
incorrectly specified your pgsql driver in server.xml. Double check
the values. I make that mistake alot.
I have gotten that answer like 10 times now :(
I have the correct driver specified :)
I must have
I've used DBCP on 4.1.12 and 4.0.X
well, its now working.
Strangely enough haveing the driver in WEB-INF/lib causes a problem,
somone should document that on the page (Specifically telling people where to
put the jar)
Thanks for the help
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
I've used DBCP on 4.1.12 and 4.0.X
BTW how do you verify that the connections are being pooled
--
To unsubscribe, e-mail: mailto:[EMAIL PROTECTED]
For additional commands, e-mail: mailto:[EMAIL PROTECTED]
David,
We use DBCP on a mission critical 24 x 7 application - and we have no issues with it.
We started with Tomcat 4.1.12 and are about to go to 4.1.18 - already in development
and working fine.
When we did our initial investigations, we were able to use DBCP at all the levels
possible in
