Ryan,
I checked the status of bug 6575349 and there is a note that the bug was
only found on Windows 2003. There is an entry in the 9.1pe release notes
about downloading a HotFix from Microsoft:
Case Number: SRX070906600011
Workspace URL:
(
https://sftus.one.microsoft.com/ChooseTransfer.aspx?key=a9c9b140-aa2f-4e0d-a39c-7e89ba067af6)
HTH,
Paul
GlassFish Community Manager
On 1/23/2009 11:06 PM, Ryan de Laplante wrote:
> Hi,
>
> We are one of the unlucky customers suffering from this problem on
> Windows 2003 Server:
>
>>
>> Win2003 only: Non-paged pool leak memory, breaking tcp stack and
>> richaccess test (6575349)
>>
>>
>> Description
>>
>> *(Windows 2003 only)* There are memory leaks on Windows 2003 systems
>> when performing rich access functions. The problem occurs because the
>> Win32 nonpaged pool keeps growing, eventually bringing down the entire
>> TCP/IP stack. Once the failure happens, the TCP/IP stack is left in an
>> recoverable state, and the only way restore it is by rebooting the
>> Windows 2003 system.
>>
>>
>> Workaround
>>
>> There are two workarounds to this issue:
>>
>> *
>>
>> Use Grizzly blocking mode by configuring the domain.xml
>> http-listener attribute, blocking-enabled="true" or add the
>> following http-listener property:
>>
>>
>> <property name="blocking" value="true"/>
>>
>> *
>>
>> Use Windows Vista or Windows XP.
>>
>
> I noticed that GlassFish V2.1 is certified for use on Windows 2008
> server. Does that mean Sun and Microsoft have confirmed that the problem
> does not exist on Windows 2008? If so, they must have found the source
> of the problem and created a patch for Windows 2003?
>
>
> Thanks,
> Ryan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>
--
Paul