[jboss-jira] [JBoss JIRA] Closed: (JBCACHE-786) errors from "OK" putFailFast replications

[Manik Surtani (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCACHE-786?page=all ]

Manik Surtani closed JBCACHE-786.
---------------------------------

    Resolution: Done

> errors from "OK" putFailFast replications
> -----------------------------------------
>
>                 Key: JBCACHE-786
>                 URL: http://jira.jboss.com/jira/browse/JBCACHE-786
>             Project: JBoss Cache
>          Issue Type: Patch
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.4.0.SP1
>            Reporter: Owen Taylor
>         Assigned To: Manik Surtani
>            Priority: Optional
>             Fix For: 1.4.0.SP2, 2.0.0
>
>         Attachments: jbosscache-failfast-replicate-failure.patch
>
>
> [ Although putFailFast() is deprecated, it is still used by current versions of Hibernate ]
> With putFailFast(), you fairly frequently see the following situation:
>  
>  - a call to putFailFast() succeeds
>  - the (asynchronous) replication fails due to a lock timeout, and throws an exception t
>    that  is thrown is logged at level ERROR
> (Much more frequently because of JBCACHE-785, but it is a legitimate situation that
> doesn't indicate an error.)
> This patch simply detects that case and suppresses the warning. (You might be able to
> it more elegantly by bridging putFailFast() onto the options framework, but to get the
> exact existing behavior of putFailFast() would take a fairly extensive patch.)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira