Hi Reich, Lloyd, Chris,
Finally the issue is resolved by enabling APR feature in tomcat. Now
the NM can use 40 concurrent threads to talk with 100 simulated
devices with 70s delay on each successfully.
But I am not very clear yet why I have to use APR instead of NIO
connector in the scenario :)
IGNED MESSAGE-
> Hash: SHA1
>
> Han,
>
> Wang Han wrote:
> | I have tried Thread.sleep() in my servlet and it fails.
> | My NM app throws exception and can't handle such response..
>
> What exception is thrown? I can't see a reason why Thread.sleep wou
Hi all,
Thanks for your interesting suggestion.
I have tried Thread.sleep() in my servlet and it fails.
My NM app throws exception and can't handle such response..
Will try he other 2 method and see what will happen.
B.R
Hanks
On Thu, Apr 17, 2008 at 3:18 PM, Benjamin Lerman <[EMAIL PROTECTED]
opher Schultz
<[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Han,
>
>
> Wang Han wrote:
> | But in the servlet side, it handles the request too fast and always
> | sends response back to app in 30 seconds.
>
> Maybe y
Hi all,
The story is:
http
NM app <> servlet
the app sends some request to servlet and will handle the response
after 5 minutes.
But in the servlet side, it handles the request too fast and always
sends response back to app in 30 seconds.
So I wonder is t