DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4912>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=4912 Incremental Processing blocks Summary: Incremental Processing blocks Product: XalanJ2 Version: CurrentCVS Platform: All OS/Version: All Status: NEW Severity: Blocker Priority: Other Component: org.apache.xalan.transformer AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] we are here experiencing problems with Cocoon 2 and latest Xalan 2.2 when we turn on the incremental processing of Xalan. The environment is Windows 2K, JDK 1.3.1, Tomcat 3.3, Xerces 1.4.3. The problem occurs with the latest Cocoon 2 RC2 and the last version of Xalan (D13). When we put our server under some load, some threads seem to hang forever and you never get a response. This is very easy reproducable by using a frameset. If you hit 4 or 5 times the reload button, one frame is blank and Cocoon seems to never return. For each frame a Xalan Transformer Instance is used. If you then hit reload again, Tomcat crashes! There is no exception or anything else logged. The problems seem similar to the threading problem we had with the developer versions of Xalan 2.0 earlier this year. However, turning off incremental processing and everything is running fine again. If you need more information, just let me know - I'll try my best.
