Bug 1563856 - JWS Mongo Driver Errors for Spring auto-configured applications
Summary: JWS Mongo Driver Errors for Spring auto-configured applications
Alias: None
Product: JBoss Enterprise Web Server 2
Classification: JBoss
Component: unspecified
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: ---
Assignee: Jean-frederic Clere
QA Contact: skaleta
Depends On:
TreeView+ depends on / blocked
Reported: 2018-04-04 21:55 UTC by Eric Getchell
Modified: 2018-04-05 14:27 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-04-05 13:34:19 UTC
Type: Bug

Attachments (Terms of Use)

Description Eric Getchell 2018-04-04 21:55:32 UTC
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):
OCP 3.8

How reproducible:

Steps to Reproduce:
1. Create a Spring auto-configured application
2. Deploy in JWS Tomcat application
3. Examine logs

Actual results:
Error detailed in the KBase article is thrown in server logs

Expected results:
No errors as their applications do not use Mongo

Additional info:
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

Comment 1 Michal Karm Babacek 2018-04-05 13:34:19 UTC
Dear Eric,

Bugzilla is not used.

For JWS related issues (Tomcat core libraries), use:
 * https://issues.jboss.org/projects/JWS
For Spring related issues, use:
 * https://issues.jboss.org/projects/RHOAR


Comment 2 Michal Karm Babacek 2018-04-05 13:37:43 UTC
QA Contact for JWS on OpenShift Container Platform is: "Stanislav Kaleta" <skaleta@redhat.com>

Comment 3 Michal Karm Babacek 2018-04-05 14:27:18 UTC
IIRC, s2i + JWS is tracked on: https://issues.jboss.org/projects/CLOUD

Note You need to log in before you can comment on or make changes to this bug.