Bug 794374 (JBEPP-1419)

Summary: DOCUMENT - WSRP prevents server from starting and requires a force quit
Product: [JBoss] JBoss Enterprise Portal Platform 5 Reporter: Matt Wringe <mwringe>
Component: DocumentationAssignee: Jared MORGAN <jmorgan>
Status: CLOSED NOTABUG QA Contact: ecs-bugs
Severity: urgent Docs Contact:
Priority: urgent    
Version: 5.2.0.ER06CC: chris.laprun, epp-bugs, mmurray, smumford
Target Milestone: ---   
Target Release: TBD_EPP_5   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/JBEPP-1419
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-01 03:06:19 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:

Description Matt Wringe 2011-11-29 23:03:16 UTC
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: JBEPP

GTNPORTAL-2241 contains information about the new parameter available in portal/trunk/wsrp-integration/extension-war/src/main/webapp/WEB-INF/conf/wsrp/wsrp-configuration.xml. The release note in the issue captures the basic changes.

RN Text:

If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published.

Comment 1 Jared MORGAN 2011-11-29 23:03:16 UTC
Link: Added: This issue Cloned from JBEPP-1319


Comment 2 Jared MORGAN 2011-11-29 23:09:15 UTC
Release Notes Docs Status: Removed: Documented as Resolved Issue Added: Not Required
Release Notes Text: Removed: If the WSRP consumer was refreshed and activated, WSRP selfv2 prevented the server from starting when it was rebooted. The only way to work around this issue was to perform a force quit. The fix adds a &lt;value-param&gt; configuration option to the main WSRP configuration. consumersInitDelay provides a way to specify a delayed start (configurable, in seconds) of the ConsumerRegistry, which prevents a deadlock situation while the self consumers wait for the producer WSDL to be published. 


Comment 3 Scott Mumford 2011-11-29 23:14:06 UTC
Waiting on SME confirmation that this belongs in the documentation.

Comment 4 Chris Laprun 2011-11-30 14:18:26 UTC
This is not something that needs to be documented as it is an internal setting, which might (or not) be made available to end users but currently isn't.

Comment 5 Scott Mumford 2011-12-01 03:06:19 UTC
See SME comment above.