The phrase saxon(8-9) covers a very large number of different releases, and it's important to be specific which release you are using. There have been a few developments designed to reduce the risk of the NamePool filling up.

In particular, it's filling here during resolveCallsToCurrentFunction, which generates a random variable name; in earlier releases variable names were added to the NamePool, but that is no longer the case.

Michael Kay
Saxonica

On 29/12/2010 13:58, Bavin Victor wrote:
Hi! I use saxon (8-9) intensivly as I know it as the most productive solution for XSLT-transformation  for web-applications.
Usually uptime is about couple of weeks, then appear this problem in one exact module:
Caused by: net.sf.saxon.om.NamePool$NamePoolLimitException: Saxon name pool is full
       at net.sf.saxon.om.NamePool.allocateInternal(NamePool.java:524)
       at net.sf.saxon.om.NamePool.allocate(NamePool.java:461)
       at net.sf.saxon.expr.ExpressionTool.resolveCallsToCurrentFunction(ExpressionTool.java:529)

Does anybody have this kind of problems, can it be solved in other ways then restarting servlet-container ?
------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________ saxon-help mailing list archived at http://saxon.markmail.org/ saxon-help@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/saxon-help