Project

Profile

Help

Bug #4247

closed

java.lang.ExceptionInInitializerError on Saxon 9.9.1.4 .Net where Java version works

Added by Jan Pertermann over 5 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Category:
.NET API
Sprint/Milestone:
-
Start date:
2019-07-08
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.9, trunk
Fix Committed on Branch:
9.9, trunk
Fixed in Maintenance Release:
Platforms:

Description

We have an XSLT script that works with 9.8.0.14 PE .Net and shall work with the recent 9.9.1.4 PE .Net version of Saxon. Instead we get an error message:

Unbehandelte Ausnahme: java.lang.ExceptionInInitializerError
bei net.sf.saxon.Transform.doTransform(String[] args, String command)
bei Saxon.Cmd.DotNetTransform.Main(String[] args)

(Unbehandelte Ausnahme = Unhandled exception; bei = at)

Quite interesting: The script is working with the Java version of 9.9.1.4 PE.

The script is also not working with the prior maintenance release 9.9.1.3 PE .Net.

Other (simpler) scripts work.

With option "-t" set I can see that URIs from various catalog files get resolved and also that the stylesheet gets compiled.

I have no idea how to locate the problem within the XSLT with the help of the message above. And I cannot drop the XSLT /Data here.

Last lines in console before stacktrace are (with -t option):

Stylesheet compilation time: 3.4210791s (3421.0791ms)
Processing  (no source document) initial template = main

Do you have any hints? Any particular infos you need to know? Obviously, this is a Problem of Saxon 9.9 .Net versions ...


Files

StackTrace.txt (17.6 KB) StackTrace.txt Report from Net JIT debugger Jan Pertermann, 2019-07-11 09:14

Please register to edit this issue

Also available in: Atom PDF