Yes, I've tried to change this parameters but it didn't help.
I've also enable the parameter recommended by Jean-François that shown me
that the log file is plenty of this kind of line entry when we start our
client test:
[#|2009-10-19T17:13:59.428+0200|INFO|sun-glassfish-comms-server1.5|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=SelectorThread-8888;|Handling
OP_ACCEPT on SocketChannel java.nio.channels.SocketChannel[connected local=/
213.151.105.170:8888
remote=/80.36.224.214:13398]|#][#|2009-10-19T17:13:59.431+0200|INFO|sun-glassfish-comms-server1.5|javax.enterprise.system.container.web|_ThreadID=17;_ThreadName=SelectorThread-8888;|Handling
OP_ACCEPT on SocketChannel java.nio.channels.SocketChannel[connected local=/
213.151.105.170:8888 remote=/80.36.224.214:13403]|#]
[...]
Our client is developped in .NET and we discovered that there are several
issues in the th Miscrosoft API. So far we couldn't set any conclusion.
Thanks for your help !
Cheers
Pascal
On Mon, Oct 19, 2009 at 9:53 PM, Sigal Shaharabani <
Sigal.Shaharabani_at_teledata-networks.com> wrote:
> You can configure glassfish's number of HTTP threads, if I'm not mistaken
> the default is 5 which is very low
>
> Have you tried changing it?
>
>
>
> P please consider the environment - do you really need to print this
> email?
> ------------------------------
>
> *From:* Pascal Maugeri [mailto:pascal.maugeri_at_gmail.com]
> *Sent:* Monday, October 19, 2009 3:39 PM
> *To:* users_at_glassfish.dev.java.net
> *Subject:* Blocking glassfish with a load of HTTP requests
>
>
>
> Hi
>
> Using: Sun GlassFish Communications Server 1.5 (9.1.1) (build b60g-fcs)
>
> Our glassfish web service gets blocked when receiving several HTTP requests
> at the same time. We're talking about 100 threads sending 1 HTTP request at
> the same time. This should not be a big deal for Glassfish IMO.
>
> This is weird because using JMeter I'm not able to reproduce the same
> problem, this is only related to our client.
>
> There is most probably something wrong in our client but this blocks
> completly our glassfish instance and a restart is needed (no more HTTP
> requests are accepted) :-(
>
> Any idea why this is happening ?
>
> Regards,
> Pascal
>
>
>
>