Saxon

Legacy ID: #6102758 Legacy Poster: Michael Kay (mhkay)

The most likely explanation for "Unknown name code" is that there is more than one NamePool in play, and the most likely reason for that if you are using s9api is that there is more than one s9api Processor object. Saxon tries to catch this error but doesn't always succeed.

Legacy ID: #6102952 Legacy Poster: sshetty (sshetty123)

Thank you Michael. Here is the java code that runs the xquery. Configuration config = new Configuration(); config.setHostLanguage(Configuration.XQUERY); StaticQueryContext sqc = new StaticQueryContext(config); XQueryExpression exp; try { exp = store.getXQuery(xqName); final DynamicQueryContext dynamicContext = new DynamicQueryContext(config); dynamicContext.setContextItem(sqc.buildDocument(inXml)); if (params != null && params.size() > 0) { for (String name : params.keySet()) { dynamicContext.setParameter(name, params.get(name)); } } Result r = new StreamResult(result); exp.run(dynamicContext, r, props); } catch (Exception e) { e.printStackTrace(); throw e; } Is there a workaround for this issue ? How can I find the number of processors being used and how can I limit it to 1 ? Thanks again :) SShetty

Legacy ID: #6103137 Legacy Poster: Michael Kay (mhkay)

Sorry, I misread your post as saying you were using the s9api interface. I can't see anything obviously wrong with your code. I will have to see if I can reproduce it (when I get home later this week). If you can put together a complete repro (Java code, XML and XQuery source) that will help. Michael Kay

Legacy ID: #6103888 Legacy Poster: sshetty (sshetty123)

Thank you Michael. Here is the java code that runs the xquery. Configuration config = new Configuration(); config.setHostLanguage(Configuration.XQUERY); StaticQueryContext sqc = new StaticQueryContext(config); XQueryExpression exp; try { exp = store.getXQuery(xqName); final DynamicQueryContext dynamicContext = new DynamicQueryContext(config); dynamicContext.setContextItem(sqc.buildDocument(inXml)); if (params != null && params.size() > 0) { for (String name : params.keySet()) { dynamicContext.setParameter(name, params.get(name)); } } Result r = new StreamResult(result); exp.run(dynamicContext, r, props); } catch (Exception e) { e.printStackTrace(); throw e; } Is there a workaround for this issue ? How can I find the number of processors being used and how can I limit it to 1 ? Thanks again :) SShetty

Legacy ID: #6124498 Legacy Poster: Michael Kay (mhkay)

A compiled query must be run using the same Configuration as was used to create it. When you do this: exp = store.getXQuery(xqName); you appear to be fetching a compiled query that must have been compiled under a different Configuration, which will therefore be using a different NamePool. Instead of creating a new Configuration when you run the query, use the existing one, which can be accessed as XQueryExpression exp; Configuration config = exp.getExecutable().getConfiguration(); I will add a check to give a cleaner error message in this situation.

Legacy ID: #6124554 Legacy Poster: Michael Kay (mhkay)

>I will add a check to give a cleaner error message in this situation. In fact that check has already been added in my development version, but it's not there in 9.1

Legacy ID: #6128382 Legacy Poster: sshetty (sshetty123)

Thank you Michael. That was it. I am using the configuration as you suggested and its working now. Configuration config = exp.getExecutable().getConfiguration(); I just wanted to confirm that the compiled expression exp is thread safe and can be shared across multiple requests/threads ? Thanks again :) SShetty

Legacy ID: #6128473 Legacy Poster: Michael Kay (mhkay)

Yes, an XQueryExpression is thread-safe - once created, it can be evaluated repeatedly in multiple threads. A Configuration is also designed to be used concurrently in multiple threads, though it's probably a good idea to avoid using any setter methods once it's being shared - i.e. it should ideally have a single-thread setting phase and a multi-thread usage phase.