Salut,
glassfish_at_javadesktop.org wrote:
>> Salut,
>>
>> glassfish_at_javadesktop.org wrote:
>>> Any idea what this is about? It appears every 5
>> secs in one particular. The log level is FINE
>> though.. I am using
>> -Dcom.sun.enterprise.web.useCoyoteConnector=true. So,
>> does that mean that the setting isn't working? Is it
>> still using Grizzly?
>
> First, the setting to use coyote using the above JVM option wasn't working because the setting is wrong! It is missing a .connector - It should have been: -Dcom.sun.enterprise.web.connector.useCoyoteConnector=true
>
> After using the proper setting, coyote was used by the server instead of Grizzly as expected.
>
> The reason for switching in the first place: The max-connections-reached: 4096 problem.
You can increase that value by editing domain.xml:
<connection-pool ... queue-size-in-bytes="4096"/>
What was the problem you were facing? Sorry for asking again...
I used coyote wit these settings: keep alive max-connections = 1, and
timeout = 30 seconds. I also set request processing threads to 500. The
'real' reason for the connections is most likely in the application -
maybe some JDBC connections weren't being closed or whatever.. I
couldn't see the code in the very limited time I was allowed..
Hum...but performance wise, it means the client will connect to the
server, execute a single request and then the server will close the
connection. Performance wise the network latency will not be good
because browser will always have to open a connection to the server. It
probably works, but I suspect you can improve the performance by not
setting the max-connections to 1.
A+
-- Jeanfrancois
>
>
>> Can you share a test case? I don't think that
>> exception is the reason to
>> your failure (if failures you have :-))
>>
>> A+
>>
>> -- Jeanfrancois
>>
>>
>
> Unfortunately not. I don't own the code or have even looked at it. A colleague of mine told me that it was a bug in Grizzly that had been fixed - something about a FileInputStream not being closed. I don't have much more information though. If I find the bug id, I will post it. -- as a side note: I don't think this had anything to do with the max-connections-reached:4096 problem that I mentioned above.. Using coyote was a woraround that solved that particular problem. The below error was for a different app. This one also has problems with in-memory replication failing. I have a feeling that these 2 are related (pure speculation) and maybe it was because there was something that could not be serializable in the session.. don't know for sure though.
>
>
>>> Thanks
>>> ---------------------------------
>>>
>>> Unwrap error: CLOSED at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLUtils.
>> unwrapAll(SSLUtils.java:321) at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLByteBu
>> fferInputStream.doRead(SSLByteBufferInputStream.java:7
>> 9) at
>> com.sun.enterprise.web.connector.grizzly.ByteBufferInp
>> utStream.read(ByteBufferInputStream.java:167) at
>> org.apache.coyote.http11.InternalInputBuffer.fill(Inte
>> rnalInputBuffer.java:727) at
>> org.apache.coyote.http11.InternalInputBuffer.parseRequ
>> estLine(InternalInputBuffer.java:401) at
>> com.sun.enterprise.web.connector.grizzly.DefaultProces
>> sorTask.parseRequest(DefaultProcessorTask.java:684)
>> at
>> com.sun.enterprise.web.connector.grizzly.DefaultProces
>> sorTask.doProcess(DefaultProcessorTask.java:566) at
>> com.sun.enterprise.web.connector.grizzly.DefaultProces
>> sorTask.process(DefaultProcessorTask.java:813) at
>> com.sun.enterprise.web.connector.grizzly.DefaultReadTa
>> sk.executeProcessorTask(DefaultReadTask.java:339) at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTa
>> sk.
>> process(SSLReadTask.java:440) at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLReadTa
>> sk.doTask(SSLReadTask.java:228) at
>> com.sun.enterprise.web.connector.grizzly.TaskBase.run(
>> TaskBase.java:265) at
>> com.sun.enterprise.web.connector.grizzly.ssl.SSLWorker
>> Thread.run(SSLWorkerThread.java:106)
>>> [Message sent by forum member 'chilak' (chilak)]
>>>
>>>
>> http://forums.java.net/jive/thread.jspa?messageID=2916
>> 41
>>>
>> ------------------------------------------------------
>> ---------------
>>> To unsubscribe, e-mail:
>> users-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail:
>> users-help_at_glassfish.dev.java.net
>> ------------------------------------------------------
>> ---------------
>> To unsubscribe, e-mail:
>> users-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail:
>> users-help_at_glassfish.dev.java.net
> [Message sent by forum member 'chilak' (chilak)]
>
> http://forums.java.net/jive/thread.jspa?messageID=295392
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>