[ http://issues.apache.org/jira/browse/XALANJ-2322?page=comments#action_12434570 ] Toadie Darsten commented on XALANJ-2322: ----------------------------------------
The original bug (2083) still exists if the XSLT calls an Extension Function. We are still seeing corruption when data is passed from XSLT into Extension Function. I have updated the ZIP to include samples XML , XSLT and a run.cmd to illustrate the problem. The ZIP file built on the samples in bug 2083. Environment Information: - JDK: java version "1.5.0_07" - Xalan version 2.70 (latest version as of this writing) - WinXP SP2 (32 bit) - Dual Core CPU System Manufacturer Dell Inc. System Model Latitude D620 System Type X86-based PC Processor x86 Family 6 Model 14 Stepping 8 GenuineIntel ~1994 Mhz Processor x86 Family 6 Model 14 Stepping 8 GenuineIntel ~1994 Mhz BIOS Version/Date Dell Inc. A02, 4/11/2006 SMBIOS Version 2.4 Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume2 Locale United States Hardware Abstraction Layer Version = "5.1.2600.2180 (xpsp_sp2_rtm.040803-2158)" > CLONE -Data corrupted in Parallel XSL execution (when calling Extension > Function) (https://issues.apache.org/jira/browse/XALANJ-2083) > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: XALANJ-2322 > URL: http://issues.apache.org/jira/browse/XALANJ-2322 > Project: XalanJ2 > Issue Type: Bug > Affects 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: Toadie Darsten > Assigned To: Yash Talwar > Priority: Critical > Fix For: 2.7 > > Attachments: XalanXercesTest.zip > > > 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
