Hi Asanka, Addressing the JMSDeliveryMode , in MB all the messages are PERSISTENT as we write the messages to Cassandra storage before they are getting delivered. Therefore IIRC if you make the Delivery Mode into Non-Persistent in message level it will be handled as Persistent by Qpid level.
I will go through these JIRAs and verify. Will be updating the documentation according to the results found. @Shammi/Hasitha, In case that some of these message attributes are not configurable, how about removing the corresponding columns from the queue browser view? i.e. The Delivery Mode is always set into '2' (which is persistent mode) even if a publisher client set it to '1' and sent to the queue. In that case the user might feel doubtful of the results he sees in the browser view. If not as Asanka has suggested we should be explaining these info in the doc. Thanks! Ishara On Wed, May 29, 2013 at 7:47 PM, Asanka Vithanage <asan...@wso2.com> wrote: > Hi All, > > I have cover up the test on MB compatibility on JMS Message Types with > queue and Topic scenarios.According to that observed MB can support the all > JMS message types but with empty payload message observed > https://wso2.org/jira/browse/MB-262 issue. > Further found https://wso2.org/jira/browse/MB-271 issue while trying to > browse the queue with ObectMessages. > > > According to the JMS API following Message header properties should be > settable at message level, > > JMSCorrelationID > JMSCorrelationIDAsBytes > JMSDeliveryMode > JMSDestination > JMSExpiration > JMSMessageID > JMSPriority > JMSRedelivered > JMSReplyTo > JMSTimestamp > JMSType > > But when we set the following properties at message level,It seems MB > overwrites the property values > JMSDeliveryMode https://wso2.org/jira/browse/MB-264 > JMSExpiration https://wso2.org/jira/browse/MB-267 > JMSMessageID https://wso2.org/jira/browse/MB-273 > JMSPriority MB currently not providing message priority > feature,so we can skip this for now > JMSRedelivered https://wso2.org/jira/browse/MB-268 > JMSTimestamp https://wso2.org/jira/browse/MB-274 > > > Further observed when we set the following properties at the > MessageProducer level, they won't get overwrites by the MB and delivered as > set. > > JMSDeliveryMode > queueSender.setDeliveryMode(DeliveryMode.NON_PERSISTENT); > JMSPriority queueSender.setPriority(1); > JMSExpiration queueSender.setTimeToLive(900000000); > > > So are we intentionally overwriting these properties at MB level or are we > yet to implement these features? > Can we update the documentation on these, so users can understand what we > support exactly and what are the possible workarounds? ( > https://wso2.org/jira/browse/MB-272) > > > > > > -- > Asanka Vithanage > Senior Software Engineer -QA > Mobile: +94 0716286708 > Email: asan...@wso2.com > WSO2 Inc. www.wso2.com > > -- Ishara Premasada Software Engineer, Integrations TG WSO2 Inc. http://wso2.com/ *Blog : http://isharapremadasa.blogspot.com/ Twitter : https://twitter.com/ishadil Mobile : +94 714445832*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
