You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by "Rony Zoghby (JIRA)" <xa...@xml.apache.org> on 2005/03/17 12:50:20 UTC
[jira] Created: (XALANJ-2083) Data corrupted in Parallel XSL execution
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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Henry Zongaro (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_62266 ]
Henry Zongaro commented on XALANJ-2083:
---------------------------------------
Rony, you asked whether you're using the latest version of Xalan-J. No - the latest version is Xalan-J 2.6, and you've reported this problem against Xalan-J 2.5.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Joachim (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_12330688 ]
Joachim commented on XALANJ-2083:
---------------------------------
Hi,
I found the same error in Xalan J 2.70 on AIX platforms (4 and 5) using multiple CPU.
Problem could not be reproduced on Windows, Linux on single CPU computers even if more than one threads were used.
Switching configuration on AIX to 1 thread helps to avoid bug, but slows down execution performance.
Joachim
> 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
> Assignee: 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Rony Zoghby (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_61752 ]
Rony Zoghby commented on XALANJ-2083:
-------------------------------------
Hi,
Thank you for your answer.
We're trying to have an example that reproduces
the problem. We'll let you know when we have something.
P.S.: Are the xalan-xerces versions we're using the latest ones?
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_12313001 ]
Brian Minchau commented on XALANJ-2083:
---------------------------------------
Yash has tried, but was unable to reproduce the problem. He will have another look at it in the next week.
> 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
> Assignee: Yash Talwar
> Priority: Critical
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=history ]
Brian Minchau updated XALANJ-2083:
----------------------------------
fix-priority: (was: fp1)
What is Bug ID 19434? I looked it up on the old bugzilla system and that didn't seem to be the bug you are pointing to.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Resolved: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Yash Talwar (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=all ]
Yash Talwar resolved XALANJ-2083:
---------------------------------
Fix Version: CurrentCVS
Resolution: Fixed
I looked into this defect. I used an AIX machine with multiple CPU.
The problem is reproducable with Xalan 2.6.0 Version (almost always, i.e. 9 out of 10 times)
The problem is not reproducable with currentCVS version. So, it appears that the defect has been fixed in currentCVS version.
Yash Talwar.
> 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
> Assignee: Yash Talwar
> Priority: Critical
> Fix For: CurrentCVS
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Rony Zoghby (JIRA)" <xa...@xml.apache.org>.
[ 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Assigned: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=all ]
Brian Minchau reassigned XALANJ-2083:
-------------------------------------
Assign To: Yash Talwar
> 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
> Assignee: Yash Talwar
> Priority: Critical
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_62216 ]
Brian Minchau commented on XALANJ-2083:
---------------------------------------
We are still waiting for a testcase. Of course we recognize the difficulty of producing a stand-alone testcase, and such bugs probably depend critically on there being a multi-processor CPU.
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Rony Zoghby (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_12314752 ]
Rony Zoghby commented on XALANJ-2083:
-------------------------------------
Ok thank you.
On our side, we were able to reproduce easily with different versions of xalan/xerces.
Do you have a debug version of xalan (with logs, ... ) that we can use so to have more info on the error?
Or maybe we can send you two XMLs: one which is the expected result and the other which is the obtained result.
This might help in identifying the xsl part that is causing the problem or a pattern for the error!?
> 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
> Assignee: Yash Talwar
> Priority: Critical
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Rony Zoghby (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=history ]
Rony Zoghby updated XALANJ-2083:
--------------------------------
Attachment: XalanXercesTest.zip
Hi,
Please find attached the standalone test case that reproduces the problem. The attached XalanXercesTest.zip contains the following files for the test:
test.jar: contains the test code which is also attached in the zip.(ExecuteParallelFormulaeTest.java) We have simplified our executions down to the bare minimum of javax functions.
com.jar: to build the unique input xml files so that each thread is executing on an xml with unique PCDATA at every node.
input.xml: the base xml file that is the reference for building the unique input xml files
conv.xsl: the xsl formula being executed
We have tested with Xerces 2.6.2 and Xalan 2.6.0 as well as the previous version we mentioned(2.5) and also an earlier 2.0 version and all have reproduced the problem.
To run test case where number of xsl transformations per thread is 50 and number of threads is 50 execute the following command (all execution results are dumped to disk):
/usr/local/j2sdk1.4.2_04/bin/java -Xms256M -Xmx512M -Xbootclasspath/p:xerces.jar:xalan.jar -cp test.jar:xerces.jar:xalan.jar:com.jar test/ExecuteParallelFormulaeTest /MXJ_NUMBER_OF_TRIES:50 /MXJ_NUMBER_OF_THREADS:50 /MXJ_FORMULA:conv.xsl /MXJ_INPUT_FILE:input.xml /MXJ_OUTPUT_FILE:New_Xml
To run test verification:
/usr/local/j2sdk1.4.2_04/bin/java -Xms256M -Xmx512M -cp test.jar test/ParallelTestVerification /MXJ_NUMBER_OF_TRIES:50 /MXJ_NUMBER_OF_THREADS:50 /MXJ_OUTPUT_FILE:New_Xml
Example of result of screen printout from verification:
*********************************
NOT EQUAL: File1:New_Xml_28_42.xml File2:New_Xml_28_43.xml
*********************************
*********************************
NOT EQUAL: File1:New_Xml_28_43.xml File2:New_Xml_28_44.xml
*********************************
- meaning that execution number 43 in thread number 28 is not equal to the other executions in this thread. When you diff the files you see that the node action has a value 182405 in 'New_Xml_28_43.xml' whereas, in all the other executions it has a value 164753. When you search in the other results from other executions you find that the value 182405 belongs to the results from thread 31. If you check the printout from the test execution you see that 28_43 executed at the same time as 31_44 so the result came from thread 31 meaning that we are obtaining random results from parallel executions of seperate xsl executions on different xml files.
Transforming Node: ThreadNumber:28 TryNumber:43 OutputFile:New_Xml_28_43.xml
Transforming Node: ThreadNumber:31 TryNumber:44 OutputFile:New_Xml_31_44.xml
Hope this is clear,
Rony
P.S: Can you please remove the zip attachment after downloading it as it has some proprietary aspects?
(Visible to jira-users)
> 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
> 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
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=all ]
Brian Minchau updated XALANJ-2083:
----------------------------------
fix-priority: fp1
Setting fix priority fp1, assign to Yash T., per the Xalan-J issue meeting on May 3, 2005.
> 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
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL
execution
Posted by "Toadie Darsten (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_12436549 ]
Toadie Darsten commented on XALANJ-2083:
----------------------------------------
Joachim
We have found and repro similar issues on Windows using Dual Core Processors. Have a look at 2322 as well as the suggested patch in 2321 which seems to fix the problem for us.
Regards,
Toadie
> Data corrupted in Parallel XSL execution
> ----------------------------------------
>
> Key: XALANJ-2083
> URL: http://issues.apache.org/jira/browse/XALANJ-2083
> 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: Rony Zoghby
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=all ]
Brian Minchau updated XALANJ-2083:
----------------------------------
Attachment: XalanXercesTest.zip
Re-attaching Rony's attachment, but viewable only by xalanj developers.
Rony did not grant license to Apache, so this attachement is only for the use of fixing the bug.
(Visible to xalanj-developers)
> 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
> Assignee: Yash Talwar
> Priority: Critical
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Updated: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Brian Minchau (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=all ]
Brian Minchau updated XALANJ-2083:
----------------------------------
Fix Version: 2.7
(was: CurrentCVS)
> 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
> Assignee: 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Yash Talwar (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_12315623 ]
Yash Talwar commented on XALANJ-2083:
-------------------------------------
Hi Rony
Can you please verify that the problem is fixed in currentCVS version?
Thanks!
Yash Talwar
> 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
> Assignee: Yash Talwar
> Priority: Critical
> Fix For: CurrentCVS
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Henry Zongaro (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_61373 ]
Henry Zongaro commented on XALANJ-2083:
---------------------------------------
There have been a few multithreading bugs in the Xalan-J processors discovered over the years. The one you refer to is one such. It's really impossible to tell whether a fix is available for the problem without a complete test case.
May I ask you to attach a stylesheet, input XML document(s) and a sample Java driver program that uses multiple threads that we can use to reproduce the problem?
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org
[jira] Commented: (XALANJ-2083) Data corrupted in Parallel XSL execution
Posted by "Rony Zoghby (JIRA)" <xa...@xml.apache.org>.
[ http://issues.apache.org/jira/browse/XALANJ-2083?page=comments#action_61210 ]
Rony Zoghby commented on XALANJ-2083:
-------------------------------------
This is the link to the ID:
http://issues.apache.org/jira/browse/XALANJ-49?page=all
> 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: xalan-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xalan-dev-help@xml.apache.org