Hi all, Our sys. admin. pointed out to me that the Websale demo code repeatedly looks for files which are not present. This of course create additional work at the fs level. The JVM is constantly calling stat() for the missing files. So the sys. admin. is not very happy with this... You can see this below (where ENOENT means that the entry/file do not exist): | stat64("/tmp/jBPMtest/conf/process.examples/META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration", | 0xFFBFB828) Err#2 ENOENT | /1: | stat64("/tmp/jBPMtest/conf/config.files/META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration", | 0xFFBFB828) Err#2 ENOENT | /1: | stat64("/tmp/jBPMtest/conf/resources/META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration", | 0xFFBFB828) Err#2 ENOENT | /1: stat64("/usr/j2se/jre/lib/jaxp.properties", 0xFFBFD318) Err#2 ENOENT | /1: stat64("/tmp/jBPMtest/classes/META-INF/services/javax.xml.parsers.SAXParserFactory", | 0xFFBFCB00) Err#2 ENOENT | /1: | stat64("/tmp/jBPMtest/conf/process.examples/META-INF/services/javax.xml.parsers.SAXParserFactory", | 0xFFBFCB00) Err#2 ENOENT | /1: | stat64("/tmp/jBPMtest/conf/config.files/META-INF/services/javax.xml.parsers.SAXParserFactory", | 0xFFBFCB00) Err#2 ENOENT | /1: stat64("/tmp/jBPMtest/conf/resources/META-INF/services/javax.xml.parsers.SAXParserFactory", | 0xFFBFCB00) Err#2 ENOENT | /1: stat64("/usr/j2se/jre/lib/xerces.properties", 0xFFBFCA58) Err#2 ENOENT | /1: | stat64("/tmp/jBPMtest/classes/META-INF/services/org.apache.xerces.xni.parser.XMLParserConfiguration", | 0xFFBFC170) Err#2 ENOENT | ... | I've copied some of the dirs from the starters kit in order to centralize the files a bit. But except for the new location the files and dir. structure correspond to that of the starters kit. Is my classpath wrong or are these files (or maybe just one) missing? Best regards, Johan View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4018906#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...