[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_62271 ] Rony Zoghby commented on XALANJ-2083: -------------------------------------
Hi, Good news! We can reproduce now with a standalone multi-threaded single/multiple cpus example using the xalan version i've mentionned (so not the latest version!). The XSL is quite complex: transformation from an XML to another. We then simplified our use of the xalan library (we're using pools and caches), and we can still reproduce. We'll try now to use the very basic api, and see what happens. If after this, we still don't discover the problem, we'll send you an example of the standalone example. Thank you very much for your help. > Data corrupted in Parallel XSL execution > ---------------------------------------- > > Key: XALANJ-2083 > URL: http://issues.apache.org/jira/browse/XALANJ-2083 > Project: XalanJ2 > Type: Bug > Versions: 2.5 > Environment: Solaris 8, JDK1.4.2_05 - Xalan with Xerces 2.5.0 and xercesImpl > Xerces-J_2_0_1_01 > Reporter: Rony Zoghby > Priority: Critical > > Hi, > We're executing the same stylesheet on different XML documents at the same > time (multiple concurrent threads). Randomly, the result of the execution of > one thread is the result of the execution of another: > Example: > XML INPUT1: <Date>17/01/1976</Date> > XML INPUT2: <Date>20/04/2004</Date> > The results of the XSL that extracts the date are: > RESULT 1: 20/04/2004 (the result of the second execution) > RESULT 2: 20/04/2004 > Is this issue related to Bug ID 19434? It seems like if it is the same. > If not, is there a fix for this? > Regards, > Rony. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
