[Architecture] [MB] Delayed Delivery for Rejected Messages.

Hi All, Currently when a message is being rejected by a subscriber client, the client is able to delay returning the message to the server. This is done by setting the "AndesAckWaitTimeOut" system property. But the message cannot be delayed from the server side. I.E when a message rejected is

Re: [Architecture] How do we get DAS server location?

Hi all, I have completed implementation of this component, and the relevant PR may be found at [1]. If I explain the mechanism a bit, an mDNS service is registered for the Thrift server (i.e. DAS, CEP or product-analytics distributions), provided that a system flag "receiverDiscoveryEnabled" is

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

Hi Nisala and Kasun, Great. This will help us to include AS6 as a jaggery runtime in AppCloud. thank you. On Mon, Jul 4, 2016 at 3:04 PM, KasunG Gajasinghe wrote: > > > On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara > wrote: > >> Hi Manjula, >> >>

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

On Mon, Jul 4, 2016 at 12:42 PM, Sinthuja Ragendran wrote: > Hi, > > Anyhow ultimately when all the carbon products move to AS 6.0 based > platform, we can merge all those into one. > Since, Carbon products will still be OSGi based using the embedded Tomcat, Jaggery needs to

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

On Mon, Jul 4, 2016 at 1:48 PM, Nisala Nanayakkara wrote: > Hi Manjula, > > Yes.Jaggery support will be inbuilt into the server with the release of > AS-6.0.0 next milestone. This email and documentation is provided to inform > the procedure of running jaggery apps in a pure

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

Hi Manjula, Yes.Jaggery support will be inbuilt into the server with the release of AS-6.0.0 next milestone. This email and documentation is provided to inform the procedure of running jaggery apps in a pure tomcat server, not in the AS-6.0.0. I will update the finalized documentation and

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

Hi, Anyhow ultimately when all the carbon products move to AS 6.0 based platform, we can merge all those into one. Thanks, Sinthuja. On Mon, Jul 4, 2016 at 12:38 PM, Nisala Nanayakkara wrote: > Hi Kasun, > > Yes.We can do a performance round. Currently we manage the Tomcat

Re: [Architecture] [Dev] Provide Support to run Jaggery apps in Tomcat Server

Hi Kasun, Yes.We can do a performance round. Currently we manage the Tomcat Jaggery/ AS6 support code base under a new branch [1] in our jaggery repository. Current jaggery is based on tomcat version 7 and Tomcat Jaggery implementation is based on tomcat version 8. So there are some api changes

Re: [Architecture] Supporting coordination for non worker-manager clusters

Hi All, Public jira for this is [1], and documentation jira is [2] [1] - https://wso2.org/jira/browse/ESBJAVA-4677 [2] - https://wso2.org/jira/browse/DOCUMENTATION-3554 Thanks, On Mon, Jul 4, 2016 at 12:04 PM, Rajith Vitharana wrote: > Hi All, > > This is done as mentioned

Re: [Architecture] Supporting coordination for non worker-manager clusters

Hi All, This is done as mentioned in previous mail with git pull [1], [2], currently we just identify clustering pattern as *not* "WorkerManager" for ESB task purposes, hence may need to come up with other possible pattern names in future. [1] - https://github.com/wso2/carbon-mediation/pull/652