One problem in diagnosing this is we don't currently know why the file fails to open -- I agree that from your description it sounds like something that shouldn't happen -- it looks like Xalan/Xerces are swallowing the actual error information between them. You could try filemon from sysinternals (www.sysinternals.com), which would allow you to get at this information.
Mark > -----Original Message----- > From: Swaminathan A [mailto:[EMAIL PROTECTED] > Sent: 03 September 2003 06:19 > To: '[EMAIL PROTECTED]' > Subject: RE: XalanTransformer::transform fails in Xalan 1.5 > > > Thanx for the response Mr.Mark. > > It is not multithreaded.At one time i am having only one XalanTransformer > object. > All the transformations are to the same target but at one time only one > XalanTransformer object writes into the target. > > I don't see any reason for the target file getting locked as it > is a single > threaded application. > > In an single threaded application the XSLT transformation is done > by getting > the input xml file and its xsl file. > > This application is executed in a loop for 80000 times so there is not > chance of a target file getting locked. > > -----Original Message----- > From: Mark Weaver [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 02, 2003 11:29 PM > To: [EMAIL PROTECTED] > Subject: RE: XalanTransformer::transform fails in Xalan 1.5 > > > > > > I tried the same call with Xalan 1.5 built with SP3 ( DownLoaded > > from Site). > > In that case fails sporadically in the ratio of 80 Failures / 80000 > > Attempts. > > > > The function call returns -1 and getlasterror returns > > "XalanFileOutputStreamOpenException: Error opening file: > > c:\temp\ValidationError.xml. The C++ run-time error code > (errno) is 0. (, > > line -1, column -1)" > > > > c:\temp\ValidationError.xml is the output XSLT tranformed file. > > > Is this multi-threaded? Are you using separate XalanTransformer > objects per > thread? Are all the transformations to the same target? You need to > provide more details -- there are a number of reasons that you > might not be > able to open the output file, e.g. too many open files for the process, or > something else has it locked. > > Mark > >
