Connection Manager Shutdown with Oracle Data Source

Our Oracle connections start to shutdown very often. This happen from when we have begging developing sail project (with query rule, a!query entity and so on).

This is an example of our error message. Any Suggestion?

2016-07-06 14:05:14,587 [http-amaltea.it.pirelli.com/151.10.76.28:8080-2] ERROR org.hibernate.util.JDBCExceptionReporter - javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/jdbc/PirelliOracleDS
2016-07-06 14:05:14,588 [http-amaltea.it.pirelli.com/151.10.76.28:8080-2] ERROR com.appiancorp.rest.record.data.RecordRestService - Unable to retrieve record summary for record w/ type RecordType [id=321, uuid=c9a5afaa-3423-4d44-bd55-81544c47fa2d, name=BI Forecast Release, sourceTypeStr={http://www.appian.com/ae/types/2009}DataStoreEntity, sourceUuidStr=76e86701-983e-4f61-91d9-60edae6c4aa2@_a-0000dccc-f709-8000-9e06-010000010000_34042] and id 7
com.appiancorp.suiteapi.common.exceptions.AppianExc...

OriginalPostID-222118

OriginalPostID-222118

  Discussion posts and replies are publicly visible

  • ... .LoggingDatasourceConnectionProvider.getConnection(LoggingDatasourceConnectionProvider.java:28)
              at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
              ... 177 more
    Caused by: javax.resource.ResourceException: IJ000451: The connection manager is shutdown: java:/jdbc/PirelliOracleDS
              at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.getManagedConnection(AbstractConnectionManager.java:346)
              at org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.getManagedConnection(TxConnectionManagerImpl.java:368)
              at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:510)
              at org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:143)
              ... 180 more
  • Please check the connection of your database from the application server. You can telnet and verify. Additionally, you can clear the JBoss cache (delete standalone/data/* and standalone/tmp/* contents) and restart JBoss and see if that helps.
  • We encountered the same issue with one of our application's Oracle DB ...No doubt this gave us a scope to check our code again, but deploying the data source from jboss admin console with proper pool connection limits helped us over come the issue.