[
https://issues.apache.org/jira/browse/ISIS-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved ISIS-3262.
------------------------------
Resolution: Fixed
Issue is with InteractionServiceDefault.preInteractionClosed(...) which does a
flush without handling any flush exceptions, such that if the flush fails, the
interaction close fails as well, that is, the interaction is not properly
closed and reused with the next request-cycle.
Looking into the commit history, the problematic line (369) of code comes from
https://github.com/apache/isis/commit/bc5b92bf1d1eb1750b38727ee6978b3aa59f8018
So I just go with the assumption, that its safe to ignore flush exceptions in
this particular case
> If EntityManagerHolder().getEntityManager().flush() fails, it is retried on
> next interaction.
> ---------------------------------------------------------------------------------------------
>
> Key: ISIS-3262
> URL: https://issues.apache.org/jira/browse/ISIS-3262
> Project: Isis
> Issue Type: Bug
> Components: Isis Core
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 2.0.0-RC1
>
> Attachments: ysP4bWizDh.gif
>
>
> Reported Bug : Error messages appears not to be cleared after its already
> been displayed in a previous interaction.
> Ways to reproduce in the slack thread:
> [https://the-asf.slack.com/archives/CFC42LWBV/p1666532480864199]
> and in the attached gif.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
