Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.0.0-RC2
-
None
Description
what I believe I saw with the current implementation (of one interaction and lots of transactions within) is that any entity values in `QueryResultsCache` get set to null at some stage - my guess is that DN is doing this when one of the transactions is completed, even though the underlying interaction is still open.
For safety/more robustness, instead create a new `Interaction` for each command.
Attachments
Issue Links
- links to