Short of changing the OS, the workaround and Microsoft patches did not
solve the issue for us.
http://docs.sun.com/app/docs/doc/820-3530/gawlz?a=view
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.
Ryan de Laplante wrote:
> This sounds like an open case we've had with Sun since October.
> There is a problem with asynchronous sockets leaking Non Paged Pool
> memory on Windows 2003 Server. According to Sun it only happens on
> Windows 2003. They said it's not a JRE/JDK or GlassFish bug, it's a
> Windows bug. Microsoft has some patches to try and solve it, but none
> of them have worked for us. They also said we are one of only two
> customers who have reported this issue and they are having difficulty
> reproducing it. The other customer recently submitted the source to
> their full app to help Sun and Microsoft reproduce the issue.
> In Windows task manager, add the "NP Pool" column to processes list.
> It will probably be quite high. I've seen our system go down when it
> was at 800K, but it has also lived up until 1400K and even 2200K.
>
> For now, we've resorted to restarting SJSAS 9.1 every Friday. Our
> other option is to change OS.
>
> Jeanfrancois of the Grizzly subproject can explain in more detail.
>
> Ryan
>
> glassfish_at_javadesktop.org wrote:
>> Hello,
>>
>> I'm having trouble with a web app that suddenly stops responding to
>> requests. My vital stats: Sun Java System Application Server Platform
>> Edition 9.0_01 (build b02-p01) running on Windows Server 2003.
>>
>> This web app communicates with a bunch of EJBs floating around in the
>> same application server instance when processing requests. This works
>> fine for a while, but after a few dozen requests, the server suddenly
>> stops responding to HTTP requests on the webapp's port (2976). The
>> client browser seems to connect fine, but the server doesn't return
>> anything. The admin console (port 1138) is still perfectly accessible.
>>
>> I believe I have successfully narrowed this problem down to the
>> following: the servlet is attempting to connect to a stateless EJB,
>> however the MyEjbClass.getEpisodeByID() method seems to not be
>> responding, causing the servlet to idle while it waits for the response.
>>
>> I started the domain using --verbose, and have attached the jstack dump.
>>
>> Any pointers on what I might be doing wrong would be well
>> appreciated... thanks!
>>
>> Regards,
>> Ben
>> [Message sent by forum member 'bh' (bh)]
>>
>> http://forums.java.net/jive/thread.jspa?messageID=270698
>>
>> ---------------------------------------------------------------------
>> 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
>
>