Hi Rajkumar, You will need to use a blocking call when JMS transactions are involved. In other cases, JMS can be used without this.
Furthermore, since Callout mediator is used when implementing JMS transactions, it will be a blocking call anyway. So this property documentation might need some changes. Thanks, Akalanka. On Mon, Jun 15, 2015 at 1:43 PM, Rajkumar Rajaratnam <[email protected]> wrote: > Hi, > > Doc [1] says that removal of ClientApiNonBlocking property could be vital > when queueing transports like JMS are involved. > > - Does it mean that we should always remove this property when JMS is > involved somewhere in our proxy? Lets say, I am consuming messages using > JMS and sending it out using JMS, do I still need to remove this property? > Or do we need to remove this property only if ESB consumes messages using a > streaming transports (like VFS) and sending it out using JMS? If yes, then > doc seems to be confusing. > > Please share your thoughts on this. > > [1] > https://docs.wso2.com/display/ESB481/Generic+Properties#GenericProperties-ClientApiNonBlockingBlocking > > Thanks. > > -- > Rajkumar Rajaratnam > Committer & PMC Member, Apache Stratos > Software Engineer, WSO2 > > Mobile : +94777568639 > Blog : rajkumarr.com > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Darshana Akalanka Pagoda Arachchi,* *Software Engineer* *078-4721791*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
