| Summary: | WSRP prevents server from starting and requires a force quit | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Portal Platform 5 | Reporter: | Matt Wringe <mwringe> | ||||
| Component: | Portal | Assignee: | claprun <claprun> | ||||
| Status: | CLOSED NEXTRELEASE | QA Contact: | |||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | unspecified | CC: | chris.laprun, mcupak, theute | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 5.2.0.ER06 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://jira.jboss.org/jira/browse/JBEPP-1319 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-12-04 16:44:08 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: | |||||
| Attachments: |
|
||||||
|
Description
Matt Wringe
2011-10-27 18:55:08 UTC
Thread dump when the server is stuck waiting Attachment: Added: thread.dump 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. Affects: Added: Documentation (Ref Guide, User Guide, etc.) 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. 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. Link: Added: This issue Cloned to JBEPP-1419 Chris, I'm sble to reproduce issue with 5.2.0 GA build. Any idea if that can be solved by configuration change? 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 |