Loading...

XML

Word

Printable

Type: Bug
Resolution: Won't Do
Priority: Minor
Fix Version/s: None
Affects Version/s: cloud 1.4-6.1550575927 GA
Component/s: cloud
Labels:
- cloud

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

5.2.0.GA
Steps to Reproduce:

Hide

How reproducible:
Always

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

Show
How reproducible: Always 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

SFDC Cases Links:
SFDC Cases Counter:
SFDC Cases Open:

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.

Suggestion would be to remove the mongo drivers from the base JWS OpenShift image and include them in any child image that requires Mongo

Assignee:: Sokratis Zappis

Reporter:: Eric Getchell (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2019/05/01 3:54 PM

Updated:: 2019/06/20 9:53 AM

Resolved:: 2019/06/20 9:53 AM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates