Bug 794118 (JBEPP-1184) - Can't register a consumer if an error occurs during the intial registration
Summary: Can't register a consumer if an error occurs during the intial registration
Keywords:
Status: CLOSED WONTFIX
Alias: JBEPP-1184
Product: JBoss Enterprise Portal Platform 5
Classification: JBoss
Component: unspecified
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.x
Assignee: claprun@redhat.com
QA Contact:
URL: http://jira.jboss.org/jira/browse/JBE...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-16 16:01 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: 2012-01-13 14:10:28 UTC
Type: Bug


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBEPP-1184 0 None None None Never

Description Matt Wringe 2011-09-16 16:01:51 UTC
project_key: JBEPP

see GTNPORTAL-2107

Steps to reproduce:
1) build current EPP with a wsrp component from the wsrp trunk (ie 2.1.0-Beta06-SNAPSHOT)
2) start the server
3) notice that there is an error about a missing class (due to update in pc) when trying to start the selfv2 consumer
4) copy a snapshot of the pc-federation jar with the updated class into gatein
5) start the server, and try to start the selfv2 consumer, you will not be able to start the consumer due to:
Caused by: org.oasis.wsrp.v2.OperationFailed: Could not register consumer named 'localhost.localdomain WSRP v2 version' Cause: Consumer named 'localhost.localdomain WSRP v2 version' has already been registered with the same set of registration properties. Registration rejected!

Comment 1 Matt Wringe 2011-09-16 16:02:08 UTC
Link: Added: This issue is a dependency of GTNPORTAL-2107


Comment 2 Chris Laprun 2012-01-05 11:14:22 UTC
This is a troublesome issue: basically, if the registration process ends up with an error on the consumer *after* the WS message has been sent, it can happen that the registration ends up being successful on the producer (as a result of a proper WS interaction) but the consumer, due to an exception on its side, still thinks that it didn't happen properly. Basically, this is an issue with lack of transactions with WS protocols.
I'm afraid there is no easy workaround for this issue since deregistering the consumer in case something went wrong to perform a kind of rollback is not possible if the consumer didn't receive the registration handle from the producer… :(

Comment 4 Thomas Heute 2012-01-13 14:10:28 UTC
Release Notes Docs Status: Added: Not Required



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