Bug 794267 (JBEPP-1319) - WSRP prevents server from starting and requires a force quit
Summary: WSRP prevents server from starting and requires a force quit
Keywords:
Status: CLOSED NEXTRELEASE
Alias: JBEPP-1319
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: Portal
Version: unspecified
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: 5.2.0.ER06
Assignee: claprun@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-27 18:55 UTC by Matt Wringe
Modified: 2013-09-02 05:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-04 16:44:08 UTC
Type: Bug

Attachments (Terms of Use)
thread.dump (65.10 KB, application/octet-stream)
2011-10-27 19:36 UTC, Matt Wringe 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 794374 0 urgent CLOSED DOCUMENT - WSRP prevents server from starting and requires a force quit 2021-02-22 00:41:40 UTC
Red Hat Issue Tracker JBEPP-1319 0 None Closed WSRP prevents server from starting and requires a force quit 2012-03-22 09:53:43 UTC

Internal Links: 794374

Description Matt Wringe 2011-10-27 18:55:08 UTC 
Affects: Documentation (Ref Guide, User Guide, etc.)
project_key: JBEPP

this issue also exists in EPP: GTNPORTAL-2241
Comment 1 Matt Wringe 2011-10-27 19:36:22 UTC 
Thread dump when the server is stuck waiting
Comment 2 Matt Wringe 2011-10-27 19:36:22 UTC 
Attachment: Added: thread.dump
Comment 3 Chris Laprun 2011-10-28 12:49:10 UTC 
Based on the thread dump and the state of the server when it blocks it seems that something funky is going on with the WSDL deployment/reading... Looking into it.
Comment 4 Chris Laprun 2011-10-28 16:12:14 UTC 
Affects: Added: Documentation (Ref Guide, User Guide, etc.)
Comment 5 Chris Laprun 2011-10-28 16:16:19 UTC 
Release Notes Docs Status: Added: Not Yet Documented
Release Notes Text: Added: A new configuration option has been added to the main WSRP configuration to allow for delayed starting of the ConsumerRegistry so as to avoid the self consumers to block the portal in a deadlock by waiting on the producer's WSDL to be published. This delay in configurable.
Comment 6 Jared MORGAN 2011-11-29 23:02:45 UTC 
Release Notes Docs Status: Removed: Not Yet Documented Added: Documented as Resolved Issue
Release Notes Text: Removed: A new configuration option has been added to the main WSRP configuration to allow for delayed starting of the ConsumerRegistry so as to avoid the self consumers to block the portal in a deadlock by waiting on the producer's WSDL to be published. This delay in configurable. Added: 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 7 Jared MORGAN 2011-11-29 23:03:16 UTC 
Link: Added: This issue Cloned to JBEPP-1419
Comment 8 Michal Vanco 2011-12-03 19:30:22 UTC 
Chris, I'm sble to reproduce issue with 5.2.0 GA build. Any idea if that can be solved by configuration change?
Comment 9 Michal Vanco 2011-12-04 16:44:08 UTC 
Resolving, I'm not able to reproduce that anymore. It had to be some kind of environment problem because I tried many combinations and all started properly.
Now I didn't have to increase consumersInitDelay at it works.
Sorry for concern
Note You need to log in before you can comment on or make changes to this bug.