This week's book giveaway is in the Big Data forum.
We're giving away four copies of Elasticsearch in Action and have Radu Gheorghe & Matthew Lee Hinman on-line!
See this thread for details.
The moose likes Struts and the fly likes Struts, DBCP weird problem Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Elasticsearch in Action this week in the Big Data forum!
JavaRanch » Java Forums » Frameworks » Struts
Bookmark "Struts, DBCP weird problem" Watch "Struts, DBCP weird problem" New topic

Struts, DBCP weird problem

Lucian Smith

Joined: Mar 04, 2006
Posts: 4
I am trying to set up a database connection with Struts and DBCP (Commons Database Connection Pool) and keep getting this error:

type: Status report

message: Servlet action is not available

description: The requested resource (Servlet action is not available) is not available.

I've copied commons-dbcp-1.2.1.jar, commons-pool-1.2.jar, and mysql-connector-java-3.1.12-bin.jar into the LIB folders of Tomcat, restarted the server... Here is my struts-config.xml:

<data-source type="org.apache.commons.dbcp.BasicDataSource">
value="com.mysql.jdbc.Driver" />
value="jdbc:mysql://" />
value="XXXXXXX" />
value="XXXXXXX" />
value="10" />
value="5000" />
value="false" />
value="false" />
value="SELECT COUNT(*) FROM products" />

And yes, all the XXX is valid information..

Thank you!!!
Merrill Higginson
Ranch Hand

Joined: Feb 15, 2005
Posts: 4864
My advice to anyone looking to set up your connection pooling through struts is simply this: Don't do it.

Since it is the Application server that is ultimately responsible for maintaining a connection pool, it makes sense to do it through your Application Server and to follow the specific instructions provided by the Application Server to set it up. Just look at the Tomcat documentation, and you will find an example for setting up a MYSQl Data Source.

Consultant, Sima Solutions
It is sorta covered in the JavaRanch Style Guide.
subject: Struts, DBCP weird problem