Re: Shall we decrease the default suspension time for endpoints?

+1 it will be more convenient and more closer to real user requirements. 1 hour is to much. I think 1min is more appropriate. On Sun, May 16, 2010 at 10:17 AM, Supun Kamburugamuva wrote: > At the moment default endpoint suspension time is set to 60 * 60 * 1000 > miliseconds. This means with s

Hudson build is back to normal : Synapse - Trunk #2182

See - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org

Shall we decrease the default suspension time for endpoints?

At the moment default endpoint suspension time is set to 60 * 60 * 1000 miliseconds. This means with simple scenarios if a endpoint gets suspended user has to restart synapse. How about reducing this default value to lets say 30 secs or 1 min? Thanks, Supun.. -- Software Engineer, WSO2 Inc http:

Re: Synapse Message Store

On Sun, May 16, 2010 at 12:03 AM, Ruwan Linton wrote: > Hi Charith, > > The implementation seems to be pretty straight forward by reading your > explanation. To start with inMemory message store will work, but for any > useful scenario DLC should be persistable, meaning that the message store > ha

Build failed in Hudson: Synapse - Trunk #2181

See -- [...truncated 2171 lines...] [INFO] [dependency:copy {execution: copy}] [INFO] Configured Artifact: org.apache.axis2:addressing:1.5:mar [INFO] Configured Artifact: org.apache.sandes

Synapse schema and the changes to the configuration builders

Folks, I have committed the initial version of the schema of the Synapse Configuration. We need to do certain changes in the configuration building code to make sure we can write a proper schema. In any case if we do any change into the configuration factories/serializers please make sure to add

Re: ClientConnectionDebug question

Hi Andreas, Although the existing code calls requestCompletionTime unnecessarily even before the encoder gets completed, it captures the requestCompletionTime even in error cases. For example the request transmission not getting completed properly. Basically when ever we write some bytes to the ch

Hudson build is back to normal : Synapse - Trunk #2180

See - To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org

Build failed in Hudson: Synapse - Trunk #2179

See -- [...truncated 2106 lines...] [INFO] [install:install {execution: default-install}] [INFO] Installing

Re: Intermittent NHTTP Test Failures

I've fixed a couple of issues in the tests for the Axis2 transports, but none of these issues accounts for the NHTTP test failures. I think/hope those are fixed by r944697/r944701, but we need some more builds before this can be confirmed. In the meantime I (re)enabled the failure notifications for

ClientConnectionDebug question

Could the people who did the ClientConnectionDebug stuff please have a look at the TODO item below. I don't think that the code is executed in the right place. Andreas -- Forwarded message -- From: Date: Sat, May 15, 2010 at 21:15 Subject: svn commit: r944701 - /synapse/trunk/j

Re: problem occured in message mediation samples

Btw you should specify the addurl correctly. Try running the client with following command. ant stockquote -Daddurl= http://localhost:9000/services/SimpleStockQuoteService -Dtrpurl= http://localhost:8280/ On Sat, May 15, 2010 at 11:12 PM, Heshan Suriyaarachchi < heshan.suriyaarach...@gmail.com>

Re: Synapse Message Store

Hi Charith, The implementation seems to be pretty straight forward by reading your explanation. To start with inMemory message store will work, but for any useful scenario DLC should be persistable, meaning that the message store has to support persistence. When it comes to implementation, it is

Re: problem occured in message mediation samples

FYI http://synapse.apache.org/Synapse_QuickStart.html On Sat, May 15, 2010 at 7:40 PM, Subash Chaturanga wrote: > Hi, > I'am new to synapse and built synapse and tried some samples as guided in > the documentation. > > So I started axis2 server and started message mediation samples. > > Sample 0

Synapse Message Store

Hi devs, After looking in to the code of i was able to implement a POC of InMemory Message store for the Synapse with a simple redelevery processor. I'll explain the current implementation. Message Store is a top level element. And It has a associated redelivery processor . I'm assuming there ca

Re: problem occured in message mediation samples

You need to build and deploy the SimpleStockQuote service which is inside the samples/axis2Server/src/SimpleStockQuoteSerivice. Switch into that folder and run ant from there. Rajika On Sat, May 15, 2010 at 7:40 PM, Subash Chaturanga wrote: > Hi, > I'am new to synapse and built synapse and trie

problem occured in message mediation samples

Hi, I'am new to synapse and built synapse and tried some samples as guided in the documentation. So I started axis2 server and started message mediation samples. Sample 0: Introduction to Synapse* I started the synapse server by - ./synapse.sh -sample 0 inside synapse-home/bin * inside , syna