Hi , Richard
I know that is not very concerned about Clearwater , Thanks for your time
to answer my question .
Thank you very much .
Morris
2016-09-07 0:58 GMT+08:00 Richard Whitehouse (projectclearwater.org) <
richard.whiteho...@projectclearwater.org>:
> Morris,
>
>
>
> Yes that is possible.
Morris,
Yes that is possible. You could either spawn a new thread for each request, or
dispatch it to a worker pool. What you choose to do is really an implementation
detail of the application server you write, and not really related to how
Clearwater is structured.
Richard
From: yan morris
Aravind,
The maximum expiry time that a subscriber can register for is configurable. By
default, it's 300 seconds, but it can be configured by changing the value of
reg_max_expires which can be shared in Clearwater's shared configuration.
There's further documentation on this at
Stanislav,
Sorry to hear you are having these problems. We run stress regularly against
Project Clearwater deployments, and we don't see such problems, so it's down to
a difference in your setup.
We wouldn't ever expect to run stress against an all in one node - it's not
designed for any
Hello again,
I'm sorry for spamming the mail list but we continue our testing and come
across new crashes. This time we took all-in-one VM and limited CPU to 1 core
(to avoid Bono crashes). We found out that crashes begin when we hit ~15k open
live sockets. The thing is we expect that
Hi,
We are testing project clear water (clearwater-infrastructure
1.0-160518.173307) , we observed that IMS core network registration expiry time
is always 300 sec; it's not considering the Expiry timer in the successful
Registration message. Any configuration to set the Registration Expiry
