This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 134923

Summary:	FAST:EAP:KBC FAST:PRIORITY:3-IMPORTANT XA mode causes immediate and infinite redelivery
Product:	soa	Reporter:	mfoster <mfoster>
Component:	Binding Components	Assignee:	Venkat Chellasamy <vchellasamy>
Status:	NEW ---
Severity:	blocker
Priority:	P3
Version:	6.x
Hardware:	All
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description mfoster 2008-05-13 09:32:02 UTC

Take the following example.... MQ BC (XA) -> BPEL (atomic) -> JMS BC (XA)

If the PUT of the message in the JMS BC fails for a network reason (not available, invalid password etc...) then the
message is correctly rolled back to MQ. The problem I see, is that it is immediately retried ad-infinitum.
I believe that this should be handled in the same manner as QoS, i.e. try "x" times with a "y" interval then do
something with the message (DLQ for example).
There is no way for a business developer to catch errors like this (as far as I can tell) and therefore no way to do
anything about this situation, the framework should be more flexible.