Back to bug 1043853
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Radim Vansa | 2013-12-17 10:56:35 UTC | Severity | unspecified | high |
| Radim Vansa | 2014-01-09 09:15:27 UTC | Doc Text | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore, the message will be never received on the receiver node and will be held in unacknowledged messages buffer. If this message is ordered within JGroups, no more ordered messages from this node will be delivered on the receiver node. Possibly, some following messages will be buffered as well, eventually leading to OutOfMemoryException. |
|
| Radim Vansa | 2014-01-09 09:16:57 UTC | Doc Text | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore, the message will be never received on the receiver node and will be held in unacknowledged messages buffer. If this message is ordered within JGroups, no more ordered messages from this node will be delivered on the receiver node. Possibly, some following messages will be buffered as well, eventually leading to OutOfMemoryException. | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore, the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups, no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well, eventually leading to OutOfMemoryException. |
| Radim Vansa | 2014-01-09 09:30:33 UTC | Doc Text | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore, the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups, no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well, eventually leading to OutOfMemoryException. | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore, the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups, no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well, eventually leading to OutOfMemoryException. W: It is recommended to use UNICAST3 as this dramatically reduces the chance of this bug to happen (it was observed with UNICAST2). |
| Shay Matasaro | 2014-01-30 15:58:55 UTC | CC | gsheldon | |
| Doc Text | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again, but all these subsequent attempts will fail with NullPointerException. Therefore | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again | ||
| Doc Text | , the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups | , but all these subsequent attempts will fail with NullPointerException. </para> <para> Therefore | ||
| Doc Text | , no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well | , the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups | ||
| Doc Text | , eventually leading to OutOfMemoryException. W: It is recommended to use UNICAST3 as this dramatically reduces the chance of this bug to happen (it was observed with UNICAST2). | , no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well | ||
| Doc Text | , eventually leading to OutOfMemoryException. W: It is recommended to use UNICAST3 as this dramatically reduces the chance of this bug to happen (it was observed with UNICAST2). | |||
| Doc Text | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again | Sending a message through JGroups may fail under some race conditions with ArrayOutOfBoundException. The reliability mechanism will try to resend this message again | ||
| Doc Text | , but all these subsequent attempts will fail with NullPointerException. </para> <para> Therefore | , but all these subsequent attempts will fail with NullPointerException. </para> <para> Therefore | ||
| Doc Text | , the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups | , the message will be never received on the receiver node and will be held in unacknowledged messages buffer on the sender node. If this message is ordered within JGroups | ||
| Doc Text | , no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well | , no more ordered messages from this node will be delivered on the receiver node. Some following messages may be buffered as well | ||
| Doc Text | , eventually leading to OutOfMemoryException. W: It is recommended to use UNICAST3 as this dramatically reduces the chance of this bug to happen (it was observed with UNICAST2). | , eventually leading to OutOfMemoryException. </para> <para> It is recommended to use UNICAST3 as this dramatically reduces the chance of this bug to happen (it was observed with UNICAST2). | ||
| Blocks | 1059774 | |||
| mark yarborough | 2014-02-19 17:55:12 UTC | Target Release | --- | 6.2.1 |
| CC | myarboro | |||
| Martin Gencur | 2014-03-25 07:44:09 UTC | Target Milestone | --- | CR1 |
| Martin Gencur | 2014-03-25 07:44:47 UTC | Status | NEW | ON_QA |
| Radim Vansa | 2014-03-25 07:46:24 UTC | Status | ON_QA | VERIFIED |
| Misha H. Ali | 2014-05-27 00:03:03 UTC | CC | mhusnain | |
| John Skeoch | 2014-11-30 21:16:06 UTC | CC | mmarkus | sjacobs |
| PnT Account Manager | 2018-09-12 22:21:40 UTC | CC | gsheldon | |
| PnT Account Manager | 2018-09-12 22:31:41 UTC | CC | mhusnain |
Back to bug 1043853