Skip to content
This repository has been archived by the owner on Aug 10, 2023. It is now read-only.

Decoupled endpoint in AcksTo address never receives sequenceacknowledgements #23

Open
glassfishrobot opened this issue Mar 3, 2014 · 3 comments

Comments

@glassfishrobot
Copy link

When using metro with a decoupled endpoint, so we can use the asynchronous functionality of WSRM, the sequenceacknowledgements never arrive at the destination.

The other responses (CreateSequenceResponse, CloseSequenceResponse and TerminateSequenceResponse) do arrive at this endpoint, but the SequenceAcknowledgement is lost.

When looking through the code i found the following:
class: ClientTube , starting from linenumber 145

// TODO P3 we should also take into account addressable clients
final WsmcRuntimeProvider wsmcRuntimeProvider = context.getImplementation(WsmcRuntimeProvider.class);
if (configuration.isMakeConnectionSupportEnabled()) {
assert wsmcRuntimeProvider != null;

this.rmSourceReference = wsmcRuntimeProvider.getWsmcAnonymousEndpointReference();
wsmcRuntimeProvider.registerProtocolMessageHandler(createRmProtocolMessageHandler(rc));
} else {
this.rmSourceReference = configuration.getAddressingVersion().anonymousEpr;
}

This looks like it means that the source is always anonymous.

For this project the use of MakeConnection is not a possibilty, because we want the users to have as little dependencies as possible.

Is this something which has not been added yet, or do i need to look somewhere else to send the sequenceacknowledgements to a decoupled endpoint?

Environment

Windows 7

Affected Versions

[2.2.1-1]

@glassfishrobot
Copy link
Author

Reported by gerhardboer

@glassfishrobot
Copy link
Author

Was assigned to snajper

@glassfishrobot
Copy link
Author

This issue was imported from java.net JIRA METRO-23

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant