Back to bug 1297499

Who When What Removed Added
John Prause 2016-01-11 16:49:43 UTC Keywords ZStream
Status NEW ASSIGNED
Target Release 5.6.0 5.5.2
Assignee gmccullo mkanoor
John Prause 2016-01-12 15:30:02 UTC Target Release 5.5.2 5.5.3
Chris Pelland 2016-01-12 20:28:17 UTC Depends On 1297952
Greg McCullough 2016-02-10 20:25:04 UTC Status ASSIGNED ON_DEV
Status ON_DEV POST
CC gmccullo
John Prause 2016-02-10 20:27:59 UTC Status POST MODIFIED
Marianne Feifer 2016-02-12 16:10:02 UTC CC mfeifer
Doc Text Cause: Previously we have been using our own caching mechanism to
cache objects sent as references to the Automate Methods. We have
gotten DRb recycled object errors, since some of the objects which
were sent as references were not being cached.
DRb has a builtin caching mechanism based on TimerIdConv, which
we are starting to use in this PR.

Consequence: After the 3.2 migration, Automation code throwing "0x000... is recycled object" exceptions.

Fix: Use DRb's builtin caching mechanism


Result: No more exceptions.
James Beal 2016-02-16 13:09:42 UTC CC james.beal
errata-xmlrpc 2016-03-22 10:57:11 UTC Status MODIFIED ON_QA
John Prause 2016-03-22 12:33:07 UTC Fixed In Version 5.5.3.2
Dayle Parker 2016-03-24 01:12:17 UTC Doc Text Cause: Previously we have been using our own caching mechanism to
cache objects sent as references to the Automate Methods. We have
gotten DRb recycled object errors, since some of the objects which
were sent as references were not being cached.
DRb has a builtin caching mechanism based on TimerIdConv, which
we are starting to use in this PR.

Consequence: After the 3.2 migration, Automation code throwing "0x000... is recycled object" exceptions.

Fix: Use DRb's builtin caching mechanism


Result: No more exceptions.
Previously, the CloudForms Management Engine used a custom mechanism to cache objects sent as references to the Automate methods. However, some of the objects were not cached by the mechanism, resulting in Distributed Ruby (DRb) recycled object errors. DRb has a built-in caching mechanism based on TimerIdConv, so this release of Red Hat CloudForms will use DRb's built-in caching mechanism to avoid these errors.
Dayle Parker 2016-03-24 01:13:02 UTC Doc Text Previously, the CloudForms Management Engine used a custom mechanism to cache objects sent as references to the Automate methods. However, some of the objects were not cached by the mechanism, resulting in Distributed Ruby (DRb) recycled object errors. DRb has a built-in caching mechanism based on TimerIdConv, so this release of Red Hat CloudForms will use DRb's built-in caching mechanism to avoid these errors. Previously, the CloudForms Management Engine used a custom mechanism to cache objects sent as references to the Automate methods. However, some of the objects were not cached by the mechanism, resulting in Distributed Ruby (DRb) recycled object errors. DRb has a built-in caching mechanism based on TimerIdConv, so this release of Red Hat CloudForms will use DRb's built-in caching mechanism instead to avoid these errors.
Dayle Parker 2016-03-24 01:19:33 UTC Doc Text Previously, the CloudForms Management Engine used a custom mechanism to cache objects sent as references to the Automate methods. However, some of the objects were not cached by the mechanism, resulting in Distributed Ruby (DRb) recycled object errors. DRb has a built-in caching mechanism based on TimerIdConv, so this release of Red Hat CloudForms will use DRb's built-in caching mechanism instead to avoid these errors. Previously, the CloudForms Management Engine used a custom mechanism to cache objects sent as references to the Automate methods. However, some of the objects were not cached by the mechanism, resulting in Distributed Ruby (DRb) recycled object errors. DRb has a built-in caching mechanism based on TimerIdConv, so this release of Red Hat CloudForms will use DRb's caching mechanism instead to avoid these errors.
dajohnso 2016-03-24 21:12:46 UTC QA Contact dajohnso sshveta
Dave Johnson 2016-03-28 14:21:39 UTC QA Contact sshveta mfalesni
Milan Falešník 2016-03-31 15:12:45 UTC Status ON_QA VERIFIED
errata-xmlrpc 2016-04-13 03:45:40 UTC Status VERIFIED RELEASE_PENDING
errata-xmlrpc 2016-04-13 18:41:04 UTC Status RELEASE_PENDING CLOSED
Resolution --- ERRATA
Last Closed 2016-04-13 14:41:04 UTC
Satoe Imaishi 2017-07-14 15:19:57 UTC CC simaishi

Back to bug 1297499