Bugfix for receiving hint messages on node
Due to buggy consistency checks, no hints were accepted
@@ -86,20 +86,15 @@ public class UriConsistencyCheckingWonMessageProcessor implements WonMessageProc
"Could not load recipient WonNodeInfo (won node " + recipientNode.get() + ")");
}
sw.stop();
+ if (!message.getMessageType().isHintMessage()) {
sw.start("senderAtomUriCheck");
checkAtomUri(message.getSenderAtomURI(), senderNodeInfo);
sw.stop();
sw.start("senderSocketUriCheck");
checkSocketUri(message.getSenderSocketURI(), senderNodeInfo);
sw.stop();
- sw.start("recipientAtomUriCheck");
- checkAtomUri(message.getRecipientAtomURI(), recipientNodeInfo);
- sw.stop();
- sw.start("recipientSocketUriCheck");
- checkSocketUri(message.getRecipientSocketURI(), recipientNodeInfo);
// there is no way atom or connection uri can be on the recipient node and the
// recipient node is different from the sender node
- sw.stop();
sw.start("atomUriCheck");
checkAtomUri(message.getAtomURI(), senderNodeInfo);
sw.stop();
@@ -110,6 +105,13 @@ public class UriConsistencyCheckingWonMessageProcessor implements WonMessageProc
sw.start("createMsgAtomUriCheck");
checkCreateMsgAtomURI(message, senderNodeInfo);
sw.stop();
+ }
+ sw.start("recipientAtomUriCheck");
+ checkAtomUri(message.getRecipientAtomURI(), recipientNodeInfo);
+ sw.stop();
+ sw.start("recipientSocketUriCheck");
+ checkSocketUri(message.getRecipientSocketURI(), recipientNodeInfo);
+ sw.stop();
sw.start("signerCheck");
WonMessageDirection statedDirection = message.getEnvelopeType();
if (statedDirection.isFromOwner()) {
