Description of problem: It is script bug in tomcat 7/8. With /opt/webserver/bin/launch.sh file, you can see this part : ~~~ if [ "$db" = "MYSQL" ]; then driver="com.mysql.jdbc.Driver" elif [ "$db" = "POSTGRESQL" ]; then driver="org.postgresql.Driver" fi datasources="$datasources$(generate_datasource $jndi $username $password $driver $url)\n\n" ~~~ As you easily see, there is no mongodb driver so $driver is nothing. Therefore, url will replace of driver. In conclusion, there wouldn't be mongo db driver in tomcat jdbc connection configuration file. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.create template "jws-tomcat7-mongodb-sti" or "jws-tomcat8-mongodb-sti" 2.configure jdbc connection tomcat to mongodb Actual results: it fails to create connection pool. Expected results: it should create connection pool Additional info: This is configuration that is generated by ose3 : <Resource name="jdbc/mydb" auth="Container" type="javax.sql.DataSource" user name="user02" password="user)@" driverClassName="jdbc:mongodb://172.30.124.139:2 7017/mydb" url="" maxWait="10000" maxIdle="30" factory="org.apache.tomcat.jdbc.p ool.DataSourceFactory" minIdle="2" maxActive="3" /> See, there is mongo db url in driverClassName instead of driver name.(mongodb.jdbc.MongoDriver)
Radovan Netuka <rnetuka> updated the status of jira CLOUD-201 to Coding In Progress
Kevin Conner <kevin.conner> updated the status of jira CLOUD-201 to Closed
This is fixed in our upcoming release
Kevin, once the new images are published please move it to ON_QA.
The new JWS images have been released and this bug is fixed there. Use the latest tomcat images from Red Hat registry: jboss-webserver-3/webserver30-tomcat7-openshift:1.1 jboss-webserver-3/webserver30-tomcat8-openshift:1.1