Hi Arun,
I agree this is a typical developer scenario. Hopefully we're not at
the mercy of Vista's default security mechanisms.
If you've seen this working ok in previous builds while keeping Vista
constant, (i.e no upgrade, no patches / update manager updates, etc),
then yes this may indeed be a bug.
From the stack trace it appear the client that initiated the connection
closed the shortly after the connection was accepted by the server. Or,
something between the client & server terminated the connection right
after it was accepted. It'll take some investigation to determine
exactly what it is ... Can you easily reproduce it on Vista ?
thanks,
charlie ...
Arun Gupta wrote:
> Charlie,
>
> For verification purposes, I can disable security in Vista. But how do
> I do it ? But I still feel this is a typical developer scenario and
> either needs to be fixed or documented.
>
> I've not seen this problem in the previous builds. So something has
> changed recently only that is causing this new exception. Any idea
> about that ?
>
> -Arun
>
> charlie hunt wrote:
>> Took everyone else of this reply.
>>
>> This is likely a Vista problem. Vista introduces a whole bunch of
>> security crap.
>>
>> You might consider asking Arun to disable security crap in Vista and
>> see if he sees the problem.
>>
>> I don't know how we're gonna handle the remote socket connection
>> stuff on Vista platforms given they've gone so overboard with their
>> security blocking $hit.
>>
>> charlie ...
>>
>>
>> Jeanfrancois Arcand wrote:
>>> Arun Gupta wrote:
>>>>> Arun Gupta wrote:
>>>>>> Why do I see the following exception when starting b53 ?
>>>>>
>>>>> Which platform are you using?
>>>> Windows Vista Ultimate
>>>
>>> Have you update it recently? I need to look at the JDK bug list to
>>> see if this exception has been reported.
>>>
>>>>
>>>>> Is the connection broken after that exception?
>>>> Connection to what ?
>>>>
>>>> The server is up & running even with this exception but the
>>>> exception is last but one statement in the console and looks ugly.
>>>
>>> Is the exception happens on every request?
>>>
>>> The exception is most probably useless but can you still file a p3?
>>> It probably happens only on that platform. Which JDK are you using?
>>>
>>> Thanks
>>>
>>> -- Jeanfrancois
>>>>
>>>> -Arun
>>>>
>>>>>
>>>>> Thanks
>>>>>
>>>>> -- Jeanfrancois
>>>>>>
>>>>>> -- cut here --
>>>>>> [#|2007-06-29T09:00:34.623-0700|WARNING|sun-appserver9.1|javax.enterprise.system.container.web|_ThreadID=15;_ThreadName=SelectorThread-8080;_RequestID=dcde1574-f3c4-4d5c-900a-aedc30959ba7;|setTcpNoDelay
>>>>>> exception
>>>>>> java.net.SocketException: Connection reset by peer:
>>>>>> sun.nio.ch.Net.setIntOption
>>>>>> at sun.nio.ch.Net.setIntOption0(Native Method)
>>>>>> at sun.nio.ch.Net.setIntOption(Net.java:152)
>>>>>> at
>>>>>> sun.nio.ch.SocketChannelImpl$1.setInt(SocketChannelImpl.java:372)
>>>>>> at sun.nio.ch.SocketOptsImpl.setBoolean(SocketOptsImpl.java:38)
>>>>>> at
>>>>>> sun.nio.ch.SocketOptsImpl$IP$TCP.noDelay(SocketOptsImpl.java:284)
>>>>>> at sun.nio.ch.OptionAdaptor.setTcpNoDelay(OptionAdaptor.java:48)
>>>>>> at
>>>>>> sun.nio.ch.SocketAdaptor.setTcpNoDelay(SocketAdaptor.java:268)
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.setSocketOptions(SelectorThread.java:1835)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.handleAccept(SelectorThread.java:1408)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.handleConnection(SelectorThread.java:1372)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.doSelect(SelectorThread.java:1289)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.startListener(SelectorThread.java:1223)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.startEndpoint(SelectorThread.java:1186)
>>>>>>
>>>>>> at
>>>>>> com.sun.enterprise.web.connector.grizzly.SelectorThread.run(SelectorThread.java:1162)
>>>>>>
>>>>>> |#]
>>>>>> -- cut here --
>>>>>>
>>>>>> -Arun
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>>
>>
>
--
Charlie Hunt
Java Performance Engineer
630.285.7708 x47708 (Internal)
<http://java.sun.com/docs/performance/>