[Ds-java-dev] [jira] Assigned: (DS-13) java.sql.SQLException: No suitable driver error occurs when deploying a service though the jdbc driver is placed in \webapps\ROOT\WEB-INF\lib

[Samisa Abeysinghe (JIRA)]

     [ https://wso2.org/jira/browse/DS-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Samisa Abeysinghe reassigned DS-13:
-----------------------------------

    Assignee: Isuru Eranga Suriarachchi  (was: Saminda Wishwajith Abeyruwan )

> java.sql.SQLException: No suitable driver error occurs when deploying a service though the jdbc driver is placed in \webapps\ROOT\WEB-INF\lib
> ---------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DS-13
>                 URL: https://wso2.org/jira/browse/DS-13
>             Project: WSO2 Data Services
>          Issue Type: Bug
>          Components: core
>         Environment: Ubuntu/winxp, jdk15, mysql 5
>            Reporter: Charitha Kankanamge
>            Assignee: Isuru Eranga Suriarachchi
>            Priority: Blocker
>             Fix For: 1.0-beta
>
>
> I'm getting the following error when deploying a MySQL data service.
> May 2, 2008 11:44:43 AM org.wso2.ws.dataservice.DBDeployer deploy
> SEVERE: The myds.dbs service, which is not valid, caused Pooling manager could not establish a connection to database.
> org.apache.axis2.AxisFault: Pooling manager could not establish a connection to database.
>         at org.wso2.ws.dataservice.DBDeployer.createDBService(DBDeployer.java:261)
>         at org.wso2.ws.dataservice.DBDeployer.processService(DBDeployer.java:467)
>         at org.wso2.ws.dataservice.DBDeployer.deploy(DBDeployer.java:108)
>         at org.apache.axis2.deployment.repository.util.DeploymentFileData.deploy(DeploymentFileData.java:136)
>         at org.apache.axis2.deployment.DeploymentEngine.doDeploy(DeploymentEngine.java:597)
>         at org.apache.axis2.deployment.repository.util.WSInfoList.update(WSInfoList.java:144)
>         at org.apache.axis2.deployment.RepositoryListener.update(RepositoryListener.java:330)
>         at org.apache.axis2.deployment.RepositoryListener.checkServices(RepositoryListener.java:227)
>         at org.apache.axis2.deployment.RepositoryListener.startListener(RepositoryListener.java:324)
>         at org.apache.axis2.deployment.scheduler.SchedulerTask.checkRepository(SchedulerTask.java:64)
>         at org.apache.axis2.deployment.scheduler.SchedulerTask.run(SchedulerTask.java:71)
>         at org.apache.axis2.deployment.scheduler.Scheduler$SchedulerTimerTask.run(Scheduler.java:83)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> May 2, 2008 11:44:43 AM org.wso2.ws.dataservice.FaultyServiceRectifier run
> INFO: Trying to re-establish fautly database connection for data services :D:\wso2ds\WSO2DS~1\bin\..\repository\dataservices\myds.dbs
> May 2, 2008 11:44:43 AM org.wso2.ws.dataservice.FaultyServiceRectifier run
> SEVERE: Error occurred while trying to re-establish database connection for D:\wso2ds\WSO2DS~1\bin\..\repository\dataservices\myds.dbs.Retrying....
> java.sql.SQLException: No suitable driver
>         at java.sql.DriverManager.getConnection(DriverManager.java:545)
>         at java.sql.DriverManager.getConnection(DriverManager.java:171)
>         at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:65)
>         at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:294)
>         at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:840)
>         at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:96)
>         at org.wso2.ws.dataservice.FaultyServiceRectifier.run(FaultyServiceRectifier.java:45)
>         at java.util.TimerThread.mainLoop(Timer.java:512)
>         at java.util.TimerThread.run(Timer.java:462)
> The strange thing is I get connection successful message when testing the DB connectivity through UI. The above error can be seen in the console when clicking on finish button at the final step of the wizard.  
> The jdbc driver jar has been placed at lib directory and packages were added to the web.xml. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira