Salut,
glassfish_at_javadesktop.org wrote:
> I seem to have found a fix... but i'm not sure if its good.
>
> Under the HTTPS listener... I checked the box "Blocking Enabled".
> Doing so I restarted SJSAS9.1 U2 and HTTPS is now as fast as HTTP was - without the delays...
>
> Are there any side affects?
> I noticed that grizzly is no longer displaying its config upon startup for HTTPS ...
> ie: only displaying HTTP info:
>
> Grizzly configuration for port 38080
> maxThreads: 130
> minThreads: 10
> ByteBuffer size: 4096
> useDirectByteBuffer: false
> useByteBufferView: false
> maxHttpHeaderSize: 8192
> maxKeepAliveRequests: -1
> keepAliveTimeoutInSeconds: 30
> Static File Cache enabled: true
> Stream Algorithm : com.sun.enterprise.web.connector.grizzly.algorithms.
> NoParsingAlgorithm
> Pipeline : com.sun.enterprise.web.portunif.PortUnificationPipeline
> Round Robin Selector Algorithm enabled: true
> Round Robin Selector pool size: 8
> recycleTasks: true
> Asynchronous Request Processing enabled: false|#]
>
> This change seems to have "fixed" the problem, but not sure if I'm doing anything that's not recommended as there's not much documentation on the "blocking" setting.
>
Hum :-) You switched to blocking socket, which will improve throughput
(as you noted) but will have a strong impact on scalability. Can you
file an issue here:
https://glassfish.dev.java.net/servlets/ProjectIssues
There should not be a perf difference like that.
Thanks
-- Jeanfrancois
[Message sent by forum member 'coreyjohnston' (coreyjohnston)]
>
> http://forums.java.net/jive/thread.jspa?messageID=299023
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>