On Wed, Oct 20, 2010 at 12:01 PM, Prabath Abeysekera <[email protected]>wrote:
> > $subject has been carried out in order to test the fault tolerance of the > message delivery process of Data Server using JMS and HTTP protocols. > Mentioned below is the steps followed together with the results obtained. > > *Tested scenarios:* > 1.Sending messages to the DS interface while the database is disabled. > 2.Sending messages to the DS interface without deploying the relevant .dbs > file of a particular data service. > > > *Test for JMS message delivery process* > JMS messages routing process was tested using ActiveMQ and Qpid JMS > providres. > > * > * > *Results:* > In both the aforementioned testing scenarios it was possible to observe > that the JMS provider was keeping track of messages until it gets a chance > to send them towards the destination. If the JMS provider is unable send the > desired messages to the intended end point at a particular moment, it always > keeps those messages in its message queue until the database is made active > or the maximum retry attempts expire. The property “maximum retry attempts” > can be configured as per the requirements of the client. > *This guarantees the zero message loss of the JMS message delivery > process.* > > Hi Prabath , > Does this DB update happen in a Transaction ? Or can we make in transactional ? As i understand per your description JMS message will not get deleted till you update the database. I m interested to know weather this all round happen in a Atomic way. Example what will happen in a scenario where the Message update the database and in the response phase. The response fail (say due to a network problem ) So does it revert the data base update or will it try to retry the Message since the it will be counted as a failure to the endpoint (since the response has failed ) . If we can support to do this in an Atomic way that will be really great. :) thanks, charith. > *Test of HTTP messages delivery process* > This was tested using a my own Http client application. > > *Results:* > The interface discards the messages sent towards it while the database is > offline and the relevant .dbs file is not deployed. > > > > > > Regards, > -- > Prabath Abeysekara > Software Engineer > WSO2 Inc. > Email: [email protected] <[email protected]> > Mobile: +94718124514 > > <http://harshana05.blogspot.com/> > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Charith Dhanushka Wickramarachchi Software Engineer WSO2 Inc http://wso2.com/ http://wso2.org/ blog http://charithwiki.blogspot.com/ twitter http://twitter.com/charithwiki
_______________________________________________ Carbon-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/carbon-dev
