Back to bug 1012036
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| mark yarborough | 2013-10-02 13:17:54 UTC | Target Release | --- | 6.2.0 |
| CC | myarboro | |||
| Red Hat Bugzilla | 2013-11-03 23:56:32 UTC | CC | gsheldon | |
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Radim Vansa | 2013-11-04 10:08:25 UTC | Doc Text | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort) for that and even with ignore policy the log is filled with errors. |
|
| Misha H. Ali | 2014-05-27 00:22:09 UTC | Doc Text | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort) for that and even with ignore policy the log is filled with errors. | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort) for that and even with ignore policy the log is filled with errors. |
| Doc Text | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort) for that and even with ignore policy the log is filled with errors. | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), and even with ignore policy the log is filled with errors. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Text | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), and even with ignore policy the log is filled with errors. | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), and even with ignore policy the log is filled with errors. | ||
| CC | mhusnain | |||
| Doc Text | When a site is unreachable, JGroups's RELAY2 logs error for each dropped message. Infinispan has configurable fail policies (ignore/warn/abort), and even with ignore policy the log is filled with errors. | When a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. | ||
| Misha H. Ali | 2014-09-15 04:56:52 UTC | Doc Text | When a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. | In Red Hat JBoss Data Grid, when a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. This is a known issue for JBoss Data Grid 6.3.1 and no workaround is currently available. |
| Misha H. Ali | 2014-11-10 04:55:17 UTC | Doc Text | In Red Hat JBoss Data Grid, when a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. This is a known issue for JBoss Data Grid 6.3.1 and no workaround is currently available. | In Red Hat JBoss Data Grid, when a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. This is a known issue for JBoss Data Grid 6.4 Beta and no workaround is currently available. |
| Radim Vansa | 2014-11-11 08:18:56 UTC | Blocks | 1152458 | |
| John Skeoch | 2014-11-30 21:15:57 UTC | CC | mmarkus | sjacobs |
| Misha H. Ali | 2015-01-18 23:46:22 UTC | Doc Text | In Red Hat JBoss Data Grid, when a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. This is a known issue for JBoss Data Grid 6.4 Beta and no workaround is currently available. | In Red Hat JBoss Data Grid, when a site is unreachable, JGroups's <systemitem class="protocol">RELAY2</systemitem> logs an error for each dropped message. Infinispan has configurable fail policies (<literal>ignore</literal>/<literal>warn</literal>/<literal>abort</literal>), but the log is filled with errors despite the <literal>ignore</literal> policy. This is a known issue in JBoss Data Grid 6.4 and no workaround is currently available for this issue. |
| Christian Huffman | 2015-04-02 12:47:02 UTC | CC | chuffman | |
| PnT Account Manager | 2018-09-12 22:21:15 UTC | CC | gsheldon | |
| PnT Account Manager | 2018-09-12 22:31:23 UTC | CC | mhusnain |
Back to bug 1012036