| Summary: | WSRP strict mode is not properly restored at startup | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Chris Laprun <chris.laprun> |
| Component: | Portal | Assignee: | claprun <claprun> |
| Status: | CLOSED NEXTRELEASE | QA Contact: | |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.1.0.GA | CC: | theute |
| Target Milestone: | --- | ||
| Target Release: | 5.1.1.DEV01 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-857 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-22 09:26:39 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | 793714 | ||
| Bug Blocks: | |||
|
Description
Chris Laprun
2011-03-18 15:50:15 UTC
Link: Added: This issue depends GTNWSRP-213 Link: Added: This issue depends JBEPP-789 Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Needs More Info Release Notes Text: Removed: WSRP strict mode was not properly restored when EPP was started. This has now been addressed. Added: Cause: NEEDINFO (Code bug? Caching issue? Data writing issue? Permission issue?) Consequence: WSRP 'Strict Mode' was not properly restored when EPP was started. Fix: An upgrade to WSRP 2.0.1 GA corrects this issue. Result: WSRP Strict Mode is now implemented at startup. Release Notes Docs Status: Removed: Needs More Info Added: Documented as Resolved Issue Release Notes Text: Removed: Cause: NEEDINFO (Code bug? Caching issue? Data writing issue? Permission issue?) Consequence: WSRP 'Strict Mode' was not properly restored when EPP was started. Fix: An upgrade to WSRP 2.0.1 GA corrects this issue. Result: WSRP Strict Mode is now implemented at startup. Added: Cause: Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. Consequence: WSRP 'Strict Mode' was not properly restored when EPP was started. Fix: An upgrade to WSRP 2.0.1 GA corrects this issue. Result: WSRP Strict Mode is now properly restored from persistent state at startup. Release Notes Text: Removed: Cause: Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. Consequence: WSRP 'Strict Mode' was not properly restored when EPP was started. Fix: An upgrade to WSRP 2.0.1 GA corrects this issue. Result: WSRP Strict Mode is now properly restored from persistent state at startup. Added: WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup. Release Notes Text: Removed: WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup. Added: WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup. Possibly the same issue as JBEPP-788. Awaiting feedback from Chris Laprun. Release Notes Text: Removed: WSRP Strict mode was previously set only via listeners, which were not triggered at startup since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at startup. Possibly the same issue as JBEPP-788. Awaiting feedback from Chris Laprun. Added: WSRP Strict mode was previously set only via listeners, which were not triggered at start up since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up. Release Notes Text: Removed: WSRP Strict mode was previously set only via listeners, which were not triggered at start up since they don't yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up. Added: WSRP Strict mode was previously set only via listeners, which were not triggered when the service started since they did not yet exist at that time. This meant that WSRP Strict Mode was not properly restored when JBoss Enterprise Portal Platform was started. An upgrade to WSRP 2.0.1 GA corrects this issue and WSRP Strict Mode is now properly restored from persistent state at start up. |