Hi Alexey,
Oleksiy Stashok wrote:
> Hi Jeanfrancois,
>
> Jeanfrancois Arcand wrote:
>> Hi Sudhir,
>>
>> something is pinging Grizzly with an empty bytes request. I will need
>> to find someone that knows lbplugin but I suspect the component send
>> those requests to ping the instance.
>>
>> I would probably needs to change the log level so this warning goes
>> away, but just to make sure, are you seeing some failures?
> I noticed the same in SOAP/TCP. Seems this happens when a client closes
> connection - READ_EVENT occurs in Grizzly, it passes it to
> ProtocolHandler, which tries to read from a closed socket. Read
> operation throws Exception, this exception comes back to Grizzly and
> then "Invalid protocol".
> Seems it's the usecase for me.
Thanks for the clear explanation! I will try to see if I can detect if
the connection has been closed.
A+
-- Jeanfrancois
>
> WBR,
> Alexey.
>>
>> Thanks
>>
>> -- Jeanfrancois
>>
>> Sudhir Prabhu wrote:
>>> Hi Jeanfrancois,
>>>
>>> The issue you have listed has the port unification exception. You
>>> think that the messages I am getting is related to the same issue?
>>>
>>> In any case, I do have the LB configured. But as I have stated
>>> earlier I havent started accessing the instance through LB yet.
>>>
>>> Here is the lb.xml .
>>>
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <!DOCTYPE loadbalancer PUBLIC "-//Sun Microsystems Inc.//DTD Sun Java
>>> System Application Server 9.0//EN" "sun-loadbalancer_1_2.dtd">
>>> <loadbalancer>
>>> <cluster name="cluster1" policy="round-robin">
>>> <instance disable-timeout-in-minutes="30" enabled="true"
>>> listeners="http://eas-v20-7.India.Sun.COM:1111
>>> https://eas-v20-7.India.Sun.COM:38181" name="instance1" weight="100"/>
>>> <instance disable-timeout-in-minutes="30" enabled="true"
>>> listeners="http://eas-v20-7.India.Sun.COM:1112
>>> https://eas-v20-7.India.Sun.COM:38182" name="instance2" weight="100"/>
>>> <instance disable-timeout-in-minutes="30" enabled="true"
>>> listeners="http://eas-v20-7.India.Sun.COM:1113
>>> https://eas-v20-7.India.Sun.COM:38183" name="instance3" weight="100"/>
>>> <health-checker interval-in-seconds="30" timeout-in-seconds="10"
>>> url="/"/>
>>> </cluster>
>>> <property name="response-timeout-in-seconds" value="120"/>
>>> <property name="reload-poll-interval-in-seconds" value="7"/>
>>> <property name="https-routing" value="false"/>
>>> <property name="require-monitor-data" value="false"/>
>>> <property name="active-healthcheck-enabled" value="false"/>
>>> <property name="number-healthcheck-retries" value="3"/>
>>> <property name="rewrite-location" value="true"/>
>>> </loadbalancer>
>>> <!--
>>> This file was generated on: [Mon Jan 15 10:59:50 IST 2007].
>>> Debugging Tips:
>>> By default, instances and web-modules are not enabled. Please enable
>>> them manually if you have not done that using asadmin.
>>> -->
>>>
>>>
>>> Thanks
>>> Sudhir
>>>
>>> Jeanfrancois Arcand wrote:
>>>> Hi Sudhir,
>>>>
>>>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=1916
>>>>
>>>> Can you add your setup information to the issue? Are you using
>>>> lbplugin? I need to understand why lbplugin send empty ping to
>>>> Grizzly (kind of strange ;-))
>>>>
>>>> Thanks
>>>>
>>>> -- Jeanfrancois
>>>>
>>>> Sudhir Prabhu wrote:
>>>>> I keep getting the following exceptions in the server.log of
>>>>> instances. Any reason why should I be getting this? I have only
>>>>> started the instance and havent done anything with it yet. Havent
>>>>> even accessed the home page.
>>>>>
>>>>>
>>>>>
>>>>> [#|2007-01-12T15:16:45.523+0530|WARNING|sun-appserver9.1|GRIZZLY|_ThreadID=12;_ThreadName=httpSSLWorkerThread-1111-1;;_RequestID=4e04744d-7108-44d5-87d3-44ee42ffe820;|Invalid
>>>>> protocol: |#]
>>>>>
>>>>> [#|2007-01-12T15:16:45.524+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=12;_ThreadName=httpSSLWorkerThread-1111-1;_RequestID=4e04744d-7108-44d5-87d3-44ee42ffe820;|Invalid
>>>>> protocol|#]
>>>>>
>>>>> [#|2007-01-12T15:16:50.524+0530|WARNING|sun-appserver9.1|GRIZZLY|_ThreadID=13;_ThreadName=httpSSLWorkerThread-1111-0;;_RequestID=ee444448-b68d-41ed-8ad2-a94b73956c2a;|Invalid
>>>>> protocol: |#]
>>>>>
>>>>> [#|2007-01-12T15:16:50.525+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=13;_ThreadName=httpSSLWorkerThread-1111-0;_RequestID=ee444448-b68d-41ed-8ad2-a94b73956c2a;|Invalid
>>>>> protocol|#]
>>>>>
>>>>> [#|2007-01-12T15:16:55.524+0530|WARNING|sun-appserver9.1|GRIZZLY|_ThreadID=12;_ThreadName=httpSSLWorkerThread-1111-1;;_RequestID=4e04744d-7108-44d5-87d3-44ee42ffe820;|Invalid
>>>>> protocol: |#]
>>>>>
>>>>> [#|2007-01-12T15:16:55.525+0530|WARNING|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=12;_ThreadName=httpSSLWorkerThread-1111-1;_RequestID=4e04744d-7108-44d5-87d3-44ee42ffe820;|Invalid
>>>>> protocol|#]
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
>