[
https://issues.apache.org/jira/browse/ISIS-3262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623026#comment-17623026
]
Daniel Keir Haywood commented on ISIS-3262:
-------------------------------------------
With the command log, executionlog, audit trail and executionoutbox modules
enabled (with JPA) I also saw optimistic locking exceptions in the stack trace.
It's not clear to me whether the commandlog should always be logged (ie in a
separate transaction).... it is meant to represent an action invocation and so
is conceptually _before_ the action. But the others (executionlog, audittrail,
executionoutbox) are _after_ the action and should only be emitted if the
action succeeds ... I think.
> Sticky Message Broker Error Message
> -----------------------------------
>
> 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
>
>
> Reported Bug : Error messages appears not to be cleared after its already
> been displayed in a previous interaction.
> Ways to reproduce unclear at this point.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
