Last updated on NOVEMBER 05, 2016
Applies to:Oracle GlassFish Server - Version 2.1.1 and later
The Oracle GlassFish Server runs without issues for a significant period of time. However, over that period the amount of free memory in the Window's kernel's non-paged buffer pool decreases to the point where the pool is completely full and the instance stops responding to incoming requests. The only way to recover from the problem is to power cycle the machine.
Defect 6575349 describes a similar scenario, however to determine if this is the same problem, the memory allocations in the non-paged pool need to be examined as the allocations are tagged with labels that can be used to identify which driver is responsible for the leak. With this defect the build up was memory allocations tagged with "AfdP", which is associated with the Microsoft TCP/IP winsock driver.
Microsoft provide a utility called poolmon.exe which can be used to examine the contents of both the operating system's non-paged and paged buffer pools. This utility isn't installed with the operating system and will need to be added to the installation. Please refer to the Microsoft Knowledge Base article which provides full details on how to setup, install and use the poolmon.exe utility and references another article which provides information on how to identify which driver is responsible for which tagged allocations.
Here is example data obtained with the utility:
In the above output the top consumers of the non-paged pool are not tagged with "AdfP" and hence the leak is highly unlikely to be due to defect 6575349. The top entry is for "MFE0", which is a tag associated with McAfee security products and there is a large inbalance between the number of frees and the number of allocations which is a good indicator that this is a potential leak. The fourth entry, "File", also shows a marked difference in the number of frees compared to the number of allocations.
If the "AfdP" tag is at the top of the list, or close to it, then potentially you have encountered the issue reported in defect 6575349.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms