Bug 1136160

We do actually bundle these database drivers however a recent EAP update might have changed something that we depended on.

Can you paste the errors you find in your application logs?

If possible please run 'rpm -qa | sort' on the Node where the gear is running and provide the output as an attachment to this bug.  Be sure to remove any packages not provided by Red Hat that you believe are sensitive.

I took a look a few minutes ago and it appears to be working fine for me with the latest JBoss EAP from RHN and OpenShift Enterprise 2.1.z installation:

2014/09/04 13:13:49,650 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) JBAS010404: Deploying non-
JDBC-compliant driver class com.mysql.jdbc.Driver (version 5.1)
2014/09/04 13:13:50,155 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 35) JBAS010404: Deploying non-
JDBC-compliant driver class org.postgresql.Driver (version 8.4)

In OpenShift Enterprise we ship the mysql driver with jboss-eap6-modules-6.0.0.GA-8.el6op.noarch.  Here are the relevant files:

/usr/share/jbossas/modules/com/mysql
/usr/share/jbossas/modules/com/mysql/jdbc
/usr/share/jbossas/modules/com/mysql/jdbc/main
/usr/share/jbossas/modules/com/mysql/jdbc/main/module.xml
/usr/share/jbossas/modules/com/mysql/jdbc/main/mysql-connector-java-5.1.18-bin.jar

For postgresql the driver is shipped with the postgresql-jdbc-8.4.704-2.el6.noarch package.  The logic in the EAP spec file wires it up for gears:

https://github.com/openshift/origin-server/blob/master/cartridges/openshift-origin-cartridge-jbosseap/openshift-origin-cartridge-jbosseap.spec#L74

Created attachment 934692 [details]
JBoss EAP server log

This is the JBoss EAP server.log from my customer, who's experiencing the same problem. I will ask him about the RPM's installed and will attach the information later to this BZ.

Were the packages I mentioned installed in your environment?

Additionally can you and the customer both run the following commands from within your gear:

find -L ./jbosseap/modules -name "postgres*"
find -L ./jbosseap/modules -name "mysql*"

If you examine the java process that is running your gear you should see a section like this:

-mp /var/lib/openshift/[gear uuid]/app-root/runtime/repo//.openshift/config/modules:/var/lib/openshift/[gear uuid]/jbosseap//modules

That is what allows you to place modules in your git repo's openshift/config/modules directory as well as picking up system modules that the OpenShift runtime provides under /var/lib/openshift/[gear uuid]/jbosseap//modules.

I did notice that you're running EAP 6.2 and technically 6.3 is the latest.  I really don't think that matters though.

I can confirm that with OSE 2.1.4a on my local OSE installation this issue is not present (I'm also using JBoss EAP 6.3), my customer is using 2.1.2. though.

My customer also confirmed that on all Nodes the following files are available:

/usr/share/jbossas/modules/com/mysql/jdbc/main/module.xml
/usr/share/jbossas/modules/com/mysql/jdbc/main/mysql-connector-java-5.1.18-bin.jar

I will ask my customer for information about the JBoss EAP java process and will attach the information as soon as I have gotten it.

Due to this issue appearing to be resolved in newer versions (2.1.4a+) and sitting for over a year, I'm closing this bug.

If you feel it should remain open, please re-open it.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days