you might want to look at https://issues.apache.org/jira/browse/CLOUDSTACK-6360 
and the commits.


~Rajani



On 23-May-2014, at 3:49 am, Fabrice Brazier 
<[email protected]<mailto:[email protected]>> wrote:

Hi Saulo,

There was an issue with mysql connector. Starting 4.3 mysql connector is no
longer bundled with ACS.
I created a symbolic link to make it available to usage server:
ln -s /usr/share/java/mysql-connector-java.jar
/usr/share/cloudstack-usage/lib/mysql-connector-java.jar

This issue is being added to 4.3 release docs.

Usage server  is working fine now.

Regards,
Fabrice Brazier
Le 23 mai 2014 00:14, "Saulo Zimbaro" 
<[email protected]<mailto:[email protected]>> a écrit :

My cloud_usage table still empty. When I start cloudstack-usage I got error
bellow:


Caused by: java.sql.SQLException: No suitable driver found for

jdbc:mysql://localhost:3306/cloud?autoReconnect=true&prepStmtCacheSize=517&cachePrepStmts=true
       at java.sql.DriverManager.getConnection(DriverManager.java:635)
       at java.sql.DriverManager.getConnection(DriverManager.java:195)
       at

org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
       at

org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
       at

org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1188)
       at

org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
       at

com.cloud.utils.db.TransactionLegacy.getConnection(TransactionLegacy.java:556)
       at

com.cloud.utils.db.TransactionLegacy.prepareStatement(TransactionLegacy.java:467)
       at

com.cloud.utils.db.TransactionLegacy.prepareAutoCloseStatement(TransactionLegacy.java:460)
       at

com.cloud.utils.db.GenericDaoBase.searchIncludingRemoved(GenericDaoBase.java:394)


I use cloudstack 4.3 and works fine.


--
*Saulo Zimbaro*

Mobile ) (+55) 21 99800-0100

*[email protected]<mailto:[email protected]>

*[email protected]<mailto:[email protected]>


Reply via email to