[TINKERPOP-2719] hasNext is called on TraverserIterator after transaction is committed

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.5.2
• Fix Version/s: 3.6.0, 3.5.3
• Component/s: server
• Assignee: Florian Hockmann
• Reporter: Florian G
• Created: 14/Mar/22 14:40
• Updated: 22/Mar/22 11:14
• Resolved: 22/Mar/22 11:14

Description

In TraversalOpProcessor, the hasNext() function is called on a TraversalIterator object after the transaction is committed. This causes issues if the database tries to further execute the traversal upon the hasNext() call but has no access to the transaction anymore.