Hello,
i'm trying to achieve DBCP with tomcat 5.5.9. I thought to have done things
right since the application could connect to db, but after a night that the
application was running, in the morning, in logs, i saw a lot of Cannot get a
connection, pool exhausted errors.
This is my
Now instead of set connection static i just create a new one for each query to
perform, so if there are concurrent queries it shouldn't cause any problem:
private Connection getConnection() throws Exception {
// get context: provides the starting point for resolution of names
I want to be able to give non login authorization for a local subnet,
but force everybody else to login to a site.
Can I do this with combinations of ip-constraint and auth-constraint in
web.xml? Something like the following would give access to a private
subnet. Could I give access to
On 4/21/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
is there anything else i should change for getting the pool connection to work?
Thanks in advance.
Most of the best practices and common mistakes to avoid are covered
here:
Omar Eljumaily wrote:
I want to be able to give non login authorization for a local subnet,
but force everybody else to login to a site.
Can I do this with combinations of ip-constraint and auth-constraint in
web.xml?
No, since the servlet spec does not define a constraint based on
Greetings! Earthling Jeremy,
Never tried this before, but I'm going to have a guess because I've seen
this question before, and that didn't seem to have much luck...
The underlying technology at work is the cookie... so what happens is the
browser gets a JsessionId cookie from the server
and
Unfortunately that did not work. The cookie still got set as
domain.com, not .domain.com
I have in server.xml:
Engine name=Catalina defaultHost=localhost
Realm className=org.apache.catalina.realm.UserDatabaseRealm
resourceName=UserDatabase/
Host name=localhost
I've configured mod_jk and have sticky sessions, but every request is going
to the exact same Tomcat instance and not the other instance. I've tried
setting the loadbalancer method to both Request and Busyness, but they both
do the same thing.
It works as expected when sticky sessions are
I had another look at this and I think this has to be the only way... short
of writing the authentication code ourselves.
For it to work you must have
login-config
security-constraint
stuff in you web.xml file ie if the page is not protected, its not going
to start working... and it
