Re: Limit Concurrent Access

Hello Vitalii, I have in past extended throttler successfully to limit concurrent request, that too in a clustered environment across nodes. The scenario used in was to limit our clients based on certain number of concurrent requests they can send. The number of concurrent requests was based on

Re: CamelSmppError=034,CamelSmppStatus=UNDELIV

check you error code meaning SMPP Error Code and modify accordingly -- View this message in context: http://camel.465427.n5.nabble.com/CamelSmppError-034-CamelSmppStatus-UNDELIV-tp5788288p5788337.html Sent from the Camel - Users mailing list

Re: Limit Concurrent Access

I am not sure that Debraj was talking about incoming calls. And I was also looking for a way to limit number of concurrent exchanges being sent to given endpoint. In the Async scenario even thread pool can't help because one can make unlimited number of exchanges with one thread. And Throttler

Re: Splitting a Body and losting old informations

What do you mean the "file had been rewriting"? Do you mean it had already been written to? Are you always writing to the same file name? When a new transaction starts you can change the file name it is writing to or you can move the existing file somewhere else. At some point I assume that you

Re: Limit Concurrent Access

@Debraj, Until you can accurately characterize the request/response that users are sending as input it's hard to give good advice on this. If they are sending a bunch of data and just expecting an acknowledgement back that you've receive it and are processing it then there are fairly simple ways

Re: Splitting a Body and losting old informations

Yes, but if I use fileExiste=append, my file will have redundancy, because when I recompile the code with fileExiste=append, the file had been rewriting... you undesrtand? Ranx wrote > This a rather nebulous question. Can you post the routes you are using? > I > suspect you are not setting the

Access responseRequired ActiveMQTextMessage

Hi all, I send a message to a queue named test .Below is some code I used and sent successfully. ActiveMQTextMessage message = new ActiveMQTextMessage(); message.setResponseRequired(true); message.setText("9");

Re: Access responseRequired ActiveMQTextMessage

I think setResponseRequired is ActiveMQ specific and isnt available as part of JMS API as such. Try using replyTo instead. usage examples can be found @ camel - jms -- View this message in context:

Re: CamelSmppError=034,CamelSmppStatus=UNDELIV

Hi All, Can you please provide any help on this please? Your response was highly appreciate. On Sun, Oct 2, 2016 at 10:00 AM, raju jwala wrote: > Moreover, I am not getting help from any one. You are the only hope for me. > > Thanks > > On Sun, Oct 2, 2016 at 9:53 AM,

Re: Limit Concurrent Access

I think throttler can be used in your case. Unless you feel there couldnt be a issue when you use it. Other approach is by using Route Policy Regards, -Yogesh -- View this message in context:

Re: Access responseRequired ActiveMQTextMessage

I did it use replyto. Thanks. -- View this message in context: http://camel.465427.n5.nabble.com/Access-responseRequired-ActiveMQTextMessage-tp5788302p5788306.html Sent from the Camel - Users mailing list archive at Nabble.com.