Back to bug 1011499
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| mark yarborough | 2013-09-25 13:10:20 UTC | Target Release | --- | 6.2.0 |
| CC | myarboro | |||
| mark yarborough | 2013-10-09 12:57:15 UTC | Blocks | 1017190 | |
| Red Hat Bugzilla | 2013-11-03 23:56:54 UTC | CC | gsheldon | |
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Martin Gencur | 2013-11-04 09:34:57 UTC | Doc Text | Cause: The process of rolling upgrade for HotRod fails with MBeanException when the new cluster is being desconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and synchronizeData) work properly but it's not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequence: It is not possible to successfully finish the process of rolling upgrade for HotRod client from version JDG 6.1.0.GA to JDG 6.2.0.Beta. Fix: - Result: - |
|
| Red Hat Bugzilla | 2013-11-05 05:26:46 UTC | Doc Text | Cause: The process of rolling upgrade for HotRod fails with MBeanException when the new cluster is being desconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and | The process of rolling upgrade for HotRod fails with MBeanException when the new cluster is being disconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and |
| Doc Text | synchronizeData) work properly but it's not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequence: It is not possible to successfully finish the process of rolling upgrade for HotRod client from | synchronizeData) work correctly, however it is not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequently | ||
| Doc Text | version JDG 6.1.0.GA to JDG 6.2.0.Beta. Fix: - Result: - | , it is not possible to successfully finish the process of rolling upgrade for HotRod client from version JBoss Data Grid 6.1.0.GA to JBoss Data Grid 6.2.0.Beta. | ||
| Doc Text | The process of rolling upgrade for HotRod fails with MBeanException when the new cluster is being disconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and | The process of rolling upgrade for Hot Rod fails with MBeanException when the new cluster is being disconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and | ||
| Doc Text | synchronizeData) work correctly, however it is not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequently | synchronizeData) work correctly, however it is not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequently | ||
| Doc Text | , it is not possible to successfully finish the process of rolling upgrade for HotRod client from version JBoss Data Grid 6.1.0.GA to JBoss Data Grid 6.2.0.Beta. | , it is not possible to successfully finish the process of rolling upgrade for Hot Rod client from version JBoss Data Grid 6.1.0.GA to JBoss Data Grid 6.2.0.Beta. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Doc Type | Known Issue | Bug Fix | ||
| Tomas Sykora | 2013-11-05 14:48:15 UTC | Doc Text | The process of rolling upgrade for Hot Rod fails with MBeanException when the new cluster is being disconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and | The rolling upgrade process for Hot Rod fails with MBeanException when the new cluster is being disconnected from the old cluster after migrating all the data. The previous steps (being invoked via JMX operations recordKnownGlobalKeyset and |
| Doc Text | synchronizeData) work correctly, however it is not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequently | synchronizeData) work correctly, however it is not possible to finish the whole procedure by disconnecting the two clusters from one another. Consequently | ||
| Doc Text | , it is not possible to successfully finish the process of rolling upgrade for Hot Rod client from version JBoss Data Grid 6.1.0.GA to JBoss Data Grid 6.2.0.Beta. | , it is not possible to successfully finish the process of rolling upgrade for Hot Rod client from version JBoss Data Grid 6.1.0.GA to JBoss Data Grid 6.2.0.Beta. | ||
| Doc Type | Bug Fix | Known Issue | ||
| Depends On | 1026862 | |||
| Tristan Tarrant | 2013-11-19 13:44:04 UTC | Status | NEW | ON_QA |
| Target Milestone | --- | ER4 | ||
| Tomas Sykora | 2013-11-25 12:33:32 UTC | Status | ON_QA | VERIFIED |
| PnT Account Manager | 2018-09-12 22:21:12 UTC | CC | gsheldon |
Back to bug 1011499