[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster-devel] subscribe qos / notify=false but still getting ERASED notifications



Hi Brad,

this bug was introduced in a former release.
It is fixed now and a test case has been added.

Thanks for reporting,

Marcel


Brad Clements wrote:
In my subscribe qos I set <qos>
<notify>false</notify>
</qos>


But I'm still getting erased notifications.

Is there something else I need to do to not get ERASED notifications for subscriptions?

**callback InboundMessage[Begin]
methodName: 'update'
message_type: 'I'
requestId: 'customs:1151349646857000001'
InboundMessage[End]
MessageUnit[Begin]
qos: "\n <qos>\n <state id='ERASED'/>\n <destination>/node/xmlBlaster_127_0_0_1_3412/client/customs/1</destination>\
n <sender>/node/xmlBlaster_127_0_0_1_3412/client/customs_client/-
9237</sender>\n <subscribe id='_subId:customs_lookup'/>\n <expiration lifeTime='0' remainingLife='0' forceDestroy='false'/>\n <rcvTimestamp nanos='1151349646846000000'/>\n <queue index='0' size='1'/>\n <isPublish/>\n </qos>"
key: "\n <key oid='xmlBlaster_127_0_0_1_3412-1151349286842000000' contentMimeExtended='1.0'/>"
content: 'xmlBlaster_127_0_0_1_3412/topic/xmlBlaster_127_0_0_1_3412-
1151349286842000000'
MessageUnit[End]