Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.1.4.CR1, 7.1.4.GA
Affects Version/s: 7.1.0.GA, 7.1.1.GA, 7.1.2.GA, 7.1.3.GA, 7.2.0.CD13
Component/s: JCA
Labels:
- gss
- regression_test_only

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

7.1.z.GA
Git Pull Request:
https://github.com/ironjacamar/ironjacamar/commit/8e7898fe94f7ee9f632cb3a78aa59e2884123ab2

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

There is some corner cases in which IJ isn't able to avoid IJ000100 (closing connection for you) on connection already marked as invalid and firing IJ000100 closing it, even if the connection would be closed as invalid immediately after. It doesn't create problems to the connection pool, but the redundant WARN isn't useful and could be read as connection leak.

It happens only with enlistment-trace=false (which is default since 7.1) set for the involved datasource

clones

JBJCA-1377 use enlistmentTrace instead of disableEnlistment parameter to avoid eager IJ000100

Resolved

is cloned by

WFLY-10414 Cached-connection-manager DEBUG connection closure could be too eager with enlistment-trace==false

Closed

is incorporated by

JBEAP-14714 [GSS](7.1.z) Upgrade Ironjacamar from 1.4.9 to 1.4.10

Closed

links to

KCS

Assignee:: Stefano Maestri

Reporter:: Stefano Maestri

Tester:: Daniel Cihak

QA Contact:: Daniel Cihak

Votes:: 0 Vote for this issue

Watchers:: 8 Start watching this issue

Created:: 2018/05/21 7:11 AM

Updated:: 2021/10/24 5:53 AM

Resolved:: 2018/05/25 4:25 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates