[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xalan-dev
Subject:    [jira] [Created] (XALANJ-2564) variable value calculated incorrectly within for-each in xsl transfor
From:       "Nash (JIRA)" <jira () apache ! org>
Date:       2012-12-05 21:15:59
Message-ID: 2017969852.64947.1354742159697.JavaMail.jiratomcat () arcas
[Download RAW message or body]

Nash created XALANJ-2564:
----------------------------

             Summary: variable value calculated incorrectly within for-each in xsl \
transformation output  Key: XALANJ-2564
                 URL: https://issues.apache.org/jira/browse/XALANJ-2564
             Project: XalanJ2
          Issue Type: Bug
      Security Level: No security risk; visible to anyone (Ordinary problems in Xalan \
projects.  Anybody can view the issue.)  Affects Versions: 2.7
         Environment: Weblogic 9.2 MP3 on HP-UX Itanium(B.11.31). Multi-threaded \
environment.  Xalan 7.0. 
Hardware: 
Processors: 4
architecture: IA64N
Java: 1.5
Physical Memory: 32G
            Reporter: Nash
            Assignee: Steven J. Hathaway


We are encountering a strange issue in Production environment which we are not able \
to replicate in any environments. The Order Process & Management application which \
generates this error processes thousands of orders in a day avg. 4000 order. The \
order xmls are transformed using various xslt to update order data. There is no XLS \
transformation exception thrown but the xml output is not what is expected which \
leads to an "OrderUpdateException" being thrown by the application API. 

When this exception occurs, there are always 2 orders involved i.e. 2 different order \
xmls being transformed at the same time(same timestamp) using same xslt. The \
resulting XML transformation output for both the orders are also well-formed but due \
to incorrect value evaluated by a variable declared inside <xsl:for-each, wrong path \
information is being supplied to <Add instruction for updating the order. Morever, \
the issue seems to go away on retry of order task from the application web client. As \
a result, the orders get updated and processing continues. Here retry means applying \
the same transformation again on order xml. The input order xmls were not modified \
whatsoever during retry.



--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xalan.apache.org
For additional commands, e-mail: dev-help@xalan.apache.org


[prev in list] [next in list] [prev in thread] [next in thread]