Description of problem:
As described in https://access.redhat.com/solutions/3231401 , a Spring application that is set to auto configure will pick up the Mongo drivers that we ship in JWS. This is causing alerting errors in the customer's NOC when their applications start.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a Spring auto-configured application
2. Deploy in JWS Tomcat application
3. Examine logs
Error detailed in the KBase article is thrown in server logs
No errors as their applications do not use Mongo
We should really remove the Mongo jar files from the JWS image - if there is a need for them, then the jar files should included as part of the Template that builds the specific application that uses Mogo, not the base JWS template
Bugzilla is not used.
For JWS related issues (Tomcat core libraries), use:
For Spring related issues, use:
QA Contact for JWS on OpenShift Container Platform is: "Stanislav Kaleta" <email@example.com>
IIRC, s2i + JWS is tracked on: https://issues.jboss.org/projects/CLOUD