foodmart and sugarcrm sample databases are great for demo, testing and development. But these connection pools are causing unnecessary warnings for production deployment. How can I switch them off completely?
I am using wildfly8, JRS 6.2.1 pro and centos 7
2016-10-11 05:23:39,821 WARN [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (JCA PoolFiller) IJ000610: Unable to fill pool: javax.resource.ResourceException: Could not create connection
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:347)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:354)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:288)
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.createConnectionEventListener(SemaphoreArrayListManagedConnectionPool.java:1166) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final]
at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.fillTo(SemaphoreArrayListManagedConnectionPool.java:1030) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final]
at org.jboss.jca.core.connectionmanager.pool.mcp.PoolFiller.run(PoolFiller.java:97) [ironjacamar-core-impl-1.1.9.Final.jar:1.1.9.Final]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
Caused by: java.sql.SQLException: Could not connect: Unknown database 'foodmart'
at org.mariadb.jdbc.internal.SQLExceptionMapper.get(SQLExceptionMapper.java:149)
at org.mariadb.jdbc.internal.SQLExceptionMapper.throwException(SQLExceptionMapper.java:106)
at org.mariadb.jdbc.Driver.connect(Driver.java:114)
at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:322)
... 6 more
Caused by: org.mariadb.jdbc.internal.common.QueryException: Could not connect: Unknown database 'foodmart'
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.checkErrorPacket(MySQLProtocol.java:446)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.connect(MySQLProtocol.java:408)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.connect(MySQLProtocol.java:593)
at org.mariadb.jdbc.internal.mysql.MySQLProtocol.<init>(MySQLProtocol.java:216)
at org.mariadb.jdbc.Driver.connect(Driver.java:110)
... 7 more
2 Answers:
Posted on October 16, 2016 at 4:03pm
Thanks @hozawa. The trouble is each container has its own configuration system for JNDI resources and I was hoping buildomatic to support disabling of these sample datasources (since buildomatic is the layer that does multiple container support in the first place). But after researching, that seems not to be the case. I had to use a manual post-install modification of wildfly configuration files (i.e 3 files, WEB-INF/web.xml, WEB-INF/jboss-web.xml and js-jboss7-ds.xml).
