Loading...

XML

Word

Printable

Affects:

Release Notes
Release Note Text:

Hide
JBoss Cache used the <systemitem>useOutOfBandMessage</systemitem> message hard-coded to <literal>false</literal> when making remote procedure calls. Consequently, RPC messages that were meant to be processed immediately, such as a transaction commit, had to wait for other messages to be processed first, which could cause deadlocks. With this update, the <systemitem>useOutOfBandMessage</systemitem> is no longer set to <literal>false</literal>. Out-of-band RPC messages are now processed immedately and can no longer cause deadlocks.

Show
JBoss Cache used the <systemitem>useOutOfBandMessage</systemitem> message hard-coded to <literal>false</literal> when making remote procedure calls. Consequently, RPC messages that were meant to be processed immediately, such as a transaction commit, had to wait for other messages to be processed first, which could cause deadlocks. With this update, the <systemitem>useOutOfBandMessage</systemitem> is no longer set to <literal>false</literal>. Out-of-band RPC messages are now processed immedately and can no longer cause deadlocks.
Release Note Status:
Documented as Resolved Issue
Docs QE Status:
NEW

RPCManagerImpl#callRemoteMethods#743 hard-codes useOutOfBandMessage to false.

This causes every RPC call made by JBoss Cache to be non-OOB.
Which reintroduces https://issues.jboss.org/browse/JBCACHE-1270 that uses OOB.

blocks

JBPAPP-9613 Rollback messages to be broadcast as out-of-band messages so they are not blocked on the receiver's end