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

List:       xalan-dev
Subject:    [jira] [Commented] (XALANJ-2564) variable value calculated incorrectly within for-each in xsl transf
From:       "Nash (JIRA)" <jira () apache ! org>
Date:       2012-12-07 21:11:25
Message-ID: JIRA.12618946.1354742096287.5533.1354914685480 () arcas
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/XALANJ-2564?page=com.atlassian.jira.plugin \
.system.issuetabpanels:comment-tabpanel&focusedCommentId=13526774#comment-13526774 ] 

Nash commented on XALANJ-2564:
------------------------------

Hi Gary,

Sorry about that typo. To answer your answer original query, the application does \
create "Template" object for each of the xsl which is then shared between threads. \
The templates are created in ejbCreate() method of the session beans. 

The classpath is not the endorsed path but is a system classpath provided by weblogic \
app server.I ran a environment check and this is what it threw up.

<checkEnvironmentExtension>
     <EnvironmentCheck version="$Revision: 1.29 $">
          <environment>
               <item key="version.DOM.draftlevel">2.0fd</item>
               <item \
key="java.class.path">:/home/weblogic/bea/patch_weblogic923/profiles/default/sys_manif \
est_classpath/weblogic_patch.jar:/opt/java1.5/lib/tools.jar:/home/weblogic/bea/weblogi \
c92/server/lib/Bug8841241_920mp1.jar:/home/weblogic/bea/weblogic92/server/lib/weblogic \
_sp.jar:/home/weblogic/bea/weblogic92/server/lib/weblogic.jar:/home/weblogic/bea/weblo \
gic92/server/lib/webservices.jar::/home/weblogic/bea/weblogic92/common/eval/pointbase/ \
lib/pbclient51.jar:/home/weblogic/bea/weblogic92/server/lib/xqrl.jar:/home/weblogic/AQ \
JMSHOME/AQJMS/StartupClass/lib/WLS9.0/AQJMSStartupClass.jar:/home/weblogic/AQJMSHOME/jar_files/aqapi13.jar:</item>
  <item key="version.JAXP">1.1 or higher</item>
               <item key="java.ext.dirs">/opt/java1.5/jre/lib/ext</item>
               <item key="version.xerces2">Xerces-J 2.8.1</item>
               <item key="version.xerces1">Xerces 1.4.4</item>
               <item key="version.xalan2_2">Xalan Java 2.7.0</item>
               <item key="version.xalan1">not-present</item>
               <item key="version.ant">Apache Ant version 1.6.2 compiled on August 5 \
2004</item>  <item key="java.version">1.5.0.17</item>
               <item key="version.DOM">2.0</item>
               <item key="version.crimson">not-present</item>
               <item \
key="sun.boot.class.path">/opt/java1.5/jre/lib/rt.jar:/opt/java1.5/jre/lib/i18n.jar:/o \
pt/java1.5/jre/lib/sunrsasign.jar:/opt/java1.5/jre/lib/jsse.jar:/opt/java1.5/jre/lib/jce.jar:/opt/java1.5/jre/lib/charsets.jar:/opt/java1.5/jre/classes</item>
  <item key="version.SAX">2.0</item>
               <item key="version.xalan2x">Xalan Java 2.7.0</item>
          </environment>
          <status result="OK"/>
     </EnvironmentCheck>
</checkEnvironmentExtension>

Nash
                
> 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
> Attachments: Incorrect Transformation.zip, Xalan_Test.zip
> 
> 
> 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]