Bug 794374 (JBEPP-1419) - DOCUMENT - WSRP prevents server from starting and requires a force quit
Summary: DOCUMENT - WSRP prevents server from starting and requires a force quit
Keywords:
Status: CLOSED NOTABUG
Alias: JBEPP-1419
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Documentation
Version: 5.2.0.ER06
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: TBD_EPP_5
Assignee: Jared MORGAN
QA Contact: ecs-bugs
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-29 23:03 UTC by Matt Wringe
Modified: 2015-08-10 01:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-01 03:06:19 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 794267 0 urgent CLOSED WSRP prevents server from starting and requires a force quit 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-1419 0 None None None Never

Internal Links: 794267

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 <value-param> 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 <value-param> 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.


Note You need to log in before you can comment on or make changes to this bug.