Bug 794118 (JBEPP-1184)

Summary:	Can't register a consumer if an error occurs during the intial registration
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	Matt Wringe <mwringe>
Component:	unspecified	Assignee:	claprun <claprun>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	high	Docs Contact:
Priority:	high
Version:	unspecified	CC:	boleslaw.dawidowicz, chris.laprun, theute
Target Milestone:	---
Target Release:	5.2.x
Hardware:	Unspecified
OS:	Unspecified
URL:	http://jira.jboss.org/jira/browse/JBEPP-1184
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-01-13 14:10:28 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-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