AnsweredAssumed Answered

Wily 9.1.0.2 Message: APM Database is not reachable

Question asked by ale81 on May 29, 2013
Latest reply on Jun 2, 2013 by Vaibhav Vir Singh
Hello I have finished t o install CA Wily Introscope Enterprise Manager Release 9.1.0.2 (Build 581100) for connecting with SAp Solution Manager, in the installa´s log i got this message:

Summary
-------

Installation: Successful.

1166 Successes
0 Warnings
0 NonFatalErrors
0 FatalErrors

However,, after to start de EM I got this messages on /ccms/apmintroscope/logs/IntroscopeEnterpriseManager.log

I think that the problema is I don´t have connection with DB cemdb


Any sugestion for this problem???


Thanks

log4j:WARN No appenders could be found for logger (com.mchange.v2.log.MLog).
log4j:WARN Please initialize the log4j system properly.
5/28/13 07:42:19.329 PM ECT [ERROR] [main] [Apm.Data.Model] APM Database is not reachable. Please check the connectivity...
org.springframework.jdbc.UncategorizedSQLException: Hibernate operation: Cannot open connection; uncategorized SQLException for SQL [???]; SQL state [null]; error code [0]; Connections could not be acquired from the underlying database!; nested exception is java.sql.SQLException: Connections could not be acquired from the underlying database!

at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:83)

at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)

at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:80)

at org.springframework.orm.hibernate3.HibernateAccessor.convertJdbcAccessException(HibernateAccessor.java:424)

at org.springframework.orm.hibernate3.HibernateAccessor.convertHibernateAccessException(HibernateAccessor.java:410)

at org.springframework.orm.hibernate3.HibernateTemplate.doExecute(HibernateTemplate.java:424)
.
.
.

Caused by:
java.sql.SQLException: Connections could not be acquired from the underlying database!

at com.mchange.v2.sql.SqlUtils.toSQLException(SqlUtils.java:106)

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:529)

at com.mchange.v2.c3p0.impl.AbstractPoolBackedDataSource.getConnection(AbstractPoolBackedDataSource.java:128)

Caused by:
com.mchange.v2.resourcepool.ResourcePoolException: A ResourcePool cannot acquire a new resource -- the factory or source appears to be down.

at java.lang.Throwable.<init>(Throwable.java:67)

at com.mchange.lang.PotentiallySecondaryException.<init>(PotentiallySecondaryException.java:41)

at com.mchange.lang.PotentiallySecondaryException.<init>(PotentiallySecondaryException.java:49)

at com.mchange.v2.resourcepool.BasicResourcePool.awaitAvailable(BasicResourcePool.java:1279)

at com.mchange.v2.resourcepool.BasicResourcePool.prelimCheckoutResource(BasicResourcePool.java:557)

at com.mchange.v2.resourcepool.BasicResourcePool.checkoutResource(BasicResourcePool.java:477)

at com.mchange.v2.c3p0.impl.C3P0PooledConnectionPool.checkoutPooledConnection(C3P0PooledConnectionPool.java:525)

... 21 more
5/28/13 09:14:49.758 PM ECT [WARN] [InitializationPool.Thread3] [Manager.com.timestock.tess.services.scheduler.ExportReportJob] ExportReportJob cannot be initialized
org.quartz.SchedulerConfigException: Failure occured during job recovery. [See nested exception: org.quartz.JobPersistenceException: Failed to obtain DB connection from data source 'cemdb': java.sql.SQLException: Can't allocate JDBC connection [See nested exception: java.sql.SQLException: Can't allocate JDBC connection]]

at org.quartz.impl.jdbcjobstore.JobStoreSupport.initialize(JobStoreSupport.java:493)

at org.quartz.impl.jdbcjobstore.JobStoreTX.initialize(JobStoreTX.java:68)

at org.quartz.impl.StdSchedulerFactory.instantiate(StdSchedulerFactory.java:1010)

Outcomes