[jboss-jira] [JBoss JIRA] (WFLY-5706) Failure to commit/response shouldn't trigger failure

Paul Ferraro (JIRA) issues at jboss.org
Thu Nov 19 09:43:00 EST 2015


     [ https://issues.jboss.org/browse/WFLY-5706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Ferraro updated WFLY-5706:
-------------------------------
    Description: 
We should log a warning instead, ideally commit data to the local node (e.g. AS7 behavior).

In sync case its too late to propagate to undertow because the response was already commited.

  was:
We should log a warning instead, ideally commit data to the local node (e.g. eap 5 behavior).

In sync case its too late to propagate to undertow because the response was already commited.



> Failure to commit/response shouldn't trigger failure
> ----------------------------------------------------
>
>                 Key: WFLY-5706
>                 URL: https://issues.jboss.org/browse/WFLY-5706
>             Project: WildFly
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: 10.0.0.CR4
>            Reporter: Radoslav Husar
>            Assignee: Paul Ferraro
>
> We should log a warning instead, ideally commit data to the local node (e.g. AS7 behavior).
> In sync case its too late to propagate to undertow because the response was already commited.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)


More information about the jboss-jira mailing list