Raj, the way the JavaRanch works is that people don't pay us, and we don't solve things. We help people solve things, and - since we don't get paid, it may sometimes take some time before someone who can help gets online.
The important part of your error message is "driver of class ''". There's an empty string where the classname should be in that message, so somehow you've mis-specified part of your database connection pool definition. To be able to tell you more than that, I'd have to take time away from things I do get paid to do, but I can say that overall, it looks like you're doing everything right. Except, obviously for the 5% of the work that's going to take 95% of the time. Which, sadly is how it usually goes for all of us.
Anyway, do a fine-grained comparison of your application Context database pool definition against the Tomcat docs with special attention to the driver class and JDBC URL and I think you'll find your problem.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Nov 25, 2008
quote] please anybody solve it.
Sorry for this ,But this is not mean i am forcefully saying you have to solve it .I wrote please anybody solve it .So please don't take wrong meaning.I know we don't pay at all .anyway If you are hurted by my words i saying sorry for that.
Joined: May 14, 2004
Upon looking again at your configuration
I have solved this problem by the help of javaranch team.
The problem was i kept this code
inside context.xml but we need to keep inside server.xml
now my program is working fine.
Thanks once again
Actually, that's not true. Normally you would put it in server.xml if you wanted the connection pool to be common to multiple webapps, and you would put it in a context.xml if you wanted to it to be in a single webapp.
If you put it in both places, that could be a conflict. You can also get a conflict if you created a META-INF/context.xml file in your WAR and also had defined a context XML file in the TOMCAT_HOME/conf/Catalina/localhost directory. Finally, just to make life really challenging, if you change a WAR file and re-deploy it, you must delete the exploded version of the previous WAR file if it is present in the TOMCAT_HOME/webapps directory because if you do not, not only will you have out-of-date database connections, you will have out-of-date code and data resources!