Back to bug 807741
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Michal Linhard | 2012-03-28 15:20:31 UTC | Priority | unspecified | high |
| Target Release | --- | 6.0.0.ER6 | ||
| Link ID | JBoss Issue Tracker ISPN-1948 | |||
| QA Contact | mlinhard | |||
| Type | --- | Bug | ||
| mark yarborough | 2012-03-29 11:52:52 UTC | Target Release | 6.0.0.ER6 | 6.0.0.ER7 |
| CC | myarboro | |||
| Michal Linhard | 2012-04-02 17:59:51 UTC | Version | 6.0.0.ER6 | |
| Tristan Tarrant | 2012-04-03 07:32:29 UTC | Status | NEW | ASSIGNED |
| mark yarborough | 2012-04-04 13:18:26 UTC | CC | msurtani | |
| Misha H. Ali | 2012-04-05 14:26:59 UTC | CC | mhusnain | |
| Tristan Tarrant | 2012-04-26 20:25:13 UTC | Status | ASSIGNED | ON_QA |
| Michal Linhard | 2012-05-08 16:38:58 UTC | Status | ON_QA | ON_DEV |
| Target Release | 6.0.0.ER7 | 6.0.0.ER8 | ||
| Version | 6.0.0.ER7 | |||
| mark yarborough | 2012-05-09 13:23:24 UTC | Target Release | 6.0.0.ER8 | 6.0.0.ER9 |
| Tristan Tarrant | 2012-05-16 21:16:12 UTC | Status | ON_DEV | ON_QA |
| Michal Linhard | 2012-05-22 18:35:23 UTC | Status | ON_QA | ON_DEV |
| Version | 6.0.0.ER10 | |||
| mark yarborough | 2012-05-23 13:26:52 UTC | Target Release | 6.0.0.ER9 | 6.0.0.CR1 |
| Summary | Invalid magic number | Reopened: Invalid magic number | ||
| mark yarborough | 2012-05-23 14:19:19 UTC | Target Release | 6.0.0.CR1 | 6.0.1.GA |
| Michal Linhard | 2012-06-05 16:01:15 UTC | Version | 6.0.0.ER11 | |
| Misha H. Ali | 2012-06-06 03:26:17 UTC | Flags | needinfo?(ttarrant) | |
| Galder Zamarreño | 2012-06-08 08:53:05 UTC | CC | galder.zamarreno | |
| Misha H. Ali | 2012-06-12 05:07:57 UTC | Flags | needinfo?(ttarrant) | |
| mark yarborough | 2012-08-15 14:45:25 UTC | Version | 6.0.0.ER5, 6.0.0.ER10, 6.0.0.ER11, 6.0.0.ER6, 6.0.0.ER7 | 6.0.0 |
| mark yarborough | 2012-08-16 13:06:27 UTC | Status | ON_DEV | ASSIGNED |
| Target Milestone | --- | ER3 | ||
| Tristan Tarrant | 2012-08-20 09:21:18 UTC | Link ID | JBoss Issue Tracker ISPN-1948 | JBoss Issue Tracker ISPN-2209 |
| Tristan Tarrant | 2012-08-22 13:12:36 UTC | Target Milestone | ER3 | ER4 |
| mark yarborough | 2012-08-22 13:56:35 UTC | Target Release | 6.0.1 | 6.1.0 |
| mark yarborough | 2012-09-05 13:40:29 UTC | Doc Text | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. </para> <para> When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted on some occasions, the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added resulting in uneven request distribution. | ttarrant to marshall CCFR (if required) by EOD 6-Sep |
| Doc Type | Bug Fix | Known Issue | ||
| mark yarborough | 2012-09-05 13:44:43 UTC | Target Milestone | ER4 | --- |
| Tristan Tarrant | 2012-09-06 09:14:57 UTC | Doc Text | ttarrant to marshall CCFR (if required) by EOD 6-Sep | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. |
| Misha H. Ali | 2012-09-18 03:49:20 UTC | CC | gsheldon | |
| Doc Text | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | The issue is a rare occurrence on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | ||
| Doc Text | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions | ||
| Doc Text | the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. | the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. | ||
| Doc Text | The issue is a rare occurrence on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | ||
| Doc Text | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions | ||
| Doc Text | the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. | the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. | ||
| Doc Text | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears | ||
| Doc Text | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted, on some occasions | clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. </para> <para> When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted | ||
| Doc Text | the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. | on some occasions, the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added | ||
| Doc Text | resulting in uneven request distribution. | |||
| Doc Text | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears clients will start seeing "Invalid magic number" error messages as a result of unexpected data within the stream. </para> <para> When this problem is encountered, the recommended approach is to restart the client. If the client is not restarted on some occasions, the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added resulting in uneven request distribution. | The issue is a race condition on the Hot Rod server, which can lead to topologies being sent erroneously as a result of addition of a new node to the cluster. When the issue appears clients view "Invalid magic number" error messages due to unexpected data within the stream. </para> <para> In such a situation, the recommended approach is to restart the client. If the client is not restarted the client may recover after the unexpected data is consumed but this is not guaranteed. If the client recovers with a restart, the view topology displayed does not display one of the nodes added, resulting in uneven request distribution. |
||
| mark yarborough | 2012-11-14 14:42:41 UTC | Target Milestone | --- | ER4 |
| mark yarborough | 2012-12-05 14:26:34 UTC | Status | ASSIGNED | ON_QA |
| Target Milestone | ER4 | ER5 | ||
| Michal Linhard | 2012-12-17 09:36:32 UTC | Status | ON_QA | VERIFIED |
| John Skeoch | 2013-11-01 01:30:51 UTC | CC | msurtani | sjacobs |
| John Skeoch | 2014-03-17 04:02:51 UTC | CC | nobody | |
| John Skeoch | 2014-03-17 04:03:42 UTC | QA Contact | mlinhard | nobody |
| PnT Account Manager | 2018-09-12 22:19:50 UTC | CC | gsheldon | |
| PnT Account Manager | 2018-09-12 22:30:11 UTC | CC | mhusnain |
Back to bug 807741