9310 2010-03-24 17:32:58 +0000 unknownNameCode NamePool exceptions found in logs 2010-03-26 02:16:27 +0000 1 1 1 Unclassified mobileOK Basic checker Java Library unspecified PC Linux RESOLVED FIXED P2 normal --- 1 fd fd oldest_to_newest 33873 0 fd 2010-03-24 17:32:58 +0000 An net.sf.saxon.om.NamePool.unknownNameCode exception gets thrown from time to time when the library is deployed within a Web service. I suspect that this happens because the TransformerFactory that is used to create the source and stylesheet documents is not always the same. The bug is not easily reproductible as the same NamePool seems to be used most of the time, but it does occur a few times per day. 33927 1 fd 2010-03-26 02:16:27 +0000 The Saxon Configuration instance was defined as static in AbstractXsltTestImplementation causing the instance to be shared amongst threads. The configuration object was given to the function that loads a compiled stylesheet. This function starts by changing the NamePool to the one that was used to compile the stylesheet. When multiple threads use the same library at the same time, the UnknownNamePool exception could be raised as a consequence.