-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Mark,
On 6/25/13 10:32 AM, Mark Thomas wrote: > On 25/06/2013 15:01, Nickalaus A Painter wrote: >> Thank you very much for your quick response! Here are the >> previous error messages: > > It would have been helpful to include all the error messages the > first time around. I then wouldn't have had to waste time working > through the code checking that there should have been an error > message and telling you what to look for. Someone is cranky, today. :p >> Also, for completeness, here is MyApp.xml: > > And there we have the problem. >> >> <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE Context> >> <application xmlns="http://java.sun.com/xml/ns/j2ee"; >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="http://java.sun.com/xml/ns/javaee/web-app_2_5.xsd >> http://java.sun.com/xml/ns/j2ee/web-app_2_5.xsd"; version="2.5"> > > WTF? Where does it suggest that this is valid for a context.xml > file? Honestly, for a novice user, it is not entirely clear what the difference is between a "deployment descriptor" (i.e. web.xml) and a "context descriptor" (i.e. context.xml). I know I sometimes call context.xml a "deployment descriptor" when I'm not being careful. The document element should have been a clue (the XML is a complete mess: DOCTYPE is "Context", but then the document element is <application>, schema dictates that the document element should be web-app, etc.) but it's easy to get confused. On top of that, there is no schema available for <Context> so maybe OP thought he'd use the next-best thing... >> <Resource name="jdbc/dbconn" auth="Container" >> type="javax.sql.DataSource" >> driverClassName="com.mysql.jdbc.Driver" >> url="jdbc:mysql://localhost:3306/mydatabase" username="root" >> password="root" maxActive="50" maxIdle="15" maxWait="-1"/> > > I really, really hope those aren't the real values. You should > never connect to a database as root, even for development. +1 A few additional thoughts: 1. maxActive=50 is quite a lot. I run a medium-traffic site and we have maxActive=20 with an alert whenever active > 10. 2. maxWait=-1 is a terrible idea: you can easily tie-up all your request-processing threads waiting for database connections if something goes wrong. You won't even be able to tell users that something is wrong. Even if you make this something outrageous like 60 seconds, you should not set it to -1 for "infinite wait". - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJRybCgAAoJEBzwKT+lPKRYPTMQAKpdCnZoKAK3cnAIRhKARSnK M+Ri/0yErfLYJ9Kp7l0sDdJjW2hnrfmf9sDjmx1QNiM0t0WrMfZb6/tNURgMYgKX Ew0PtUZtA0+eBP4dZZeMWgti2zc2KraC1B3Vu8X1Kn8z3/od749QKOGAeMXSIGPm 7RYYGe7dmX4v0/CL5c5QBcD68Lea57R0dTmCEeGJ8PICG7tmfRBIuvpDpxD4BqJk UQi5jC9O9jXRZdA16Pyoqdh1oO/dTjL8MsRvLJDZrN25UCi+iocxmVZSegJdRDLL l0JJ89vQu2rrDo6REs3S01qinpxBiCa7TtVsUcemWVAqIG9aSUZglIzdTEN6gpSo VCJu67j/vmue+BRYi4mYFepTbecpv5p5YZvdTsWuwwLcnxqm+lDts/D8mKh3Nb4E 8AkCkM5W9WFs5mrczJBAo2kEFqqoDKR91c8Mx/5J0uqWnO3AnlUmK+ALUlmEHJHS x6NSP4+NTlfmiRbrq09wwKY/+F735Sufknmyo9Ojqejl+d4yvuU2blCU/mr9biXq AlA6cdNS8wG9VNhe4/XC4yDTk2DrUW7vupk4+7dhEqsZGIZzMl0hRWsQpgXMwo3w HYHJaQYcj1CNCCnOIl+HY0qgh75lICFsoBKqBFzZTudG0G8iIYa0A4IKxMKn++0z sY1qBU8Bd25MKGEJMRrG =S/j2 -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
