[
https://issues.apache.org/jira/browse/ATLAS-5091?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018044#comment-18018044
]
ASF subversion and git services commented on ATLAS-5091:
--------------------------------------------------------
Commit 0ad88da7d8537ba5d6a3211c4d8479bc7266dab6 in atlas's branch
refs/heads/ATLAS-5021_u from Madhan Neethiraj
[ https://gitbox.apache.org/repos/asf?p=atlas.git;h=0ad88da7d ]
ATLAS-5091: ensure commit/rollback is called on ManagementSystem instances
(#426)
> Fix stale transaction warnings in Atlas logs
> --------------------------------------------
>
> Key: ATLAS-5091
> URL: https://issues.apache.org/jira/browse/ATLAS-5091
> Project: Atlas
> Issue Type: Bug
> Components: atlas-core
> Affects Versions: 3.0.0
> Reporter: Madhan Neethiraj
> Assignee: Madhan Neethiraj
> Priority: Major
> Fix For: 3.0.0, 2.5.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Few uses of AtlasGraphManagement object don't call commit or roll back, which
> result in associated resources (like transactions) not be released as early
> as possible, as seen by logs shown below:
> {code:java}
> ERROR [ManagementLogger.java:275] Evicted [27@ac13000780-atlas-example-com2]
> from cache but waiting too long for transactions to close. Stale transaction
> alert on: [standardjanusgraphtx[0x559ae590]]{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
