VJM crashes on xslt Error

[Erwin Burgstaller <bu...@knapp.co.at>]

Hello!

I'm still new to xml/xslt and the last 2 days I was looking for an error in
my documents. Unfortunately I wrote a Java class so I first thought the
error is in that Java-Code. Then I began to up- and downgrade
everything except the apache server. And it naturally went worse.

After I got Cocoon running again, I found the error in my xsl-stylesheet:

Instead of 

      <xsl:value-of select=".">, 

I wrote 

      <xsl-apply-templates select=".">

which is very bad. It crashes the Java VM (IBMJava2 1.3-2.0). 

In the browser you see alternatively a (very long) stack trace for a stack
overvlow or simply the message "Internal Server Error".

In apaches error_log you see:


SIGILL 4 (*) illegal instruction (not reset when caught)
        stackpointer=0xbedc1b10

SIGABRT 6 (*) abort process
        stackpointer=0xbedbffb0


Is Sun's Java VM be more stable? I still have the problem with
org.w3c.dom.Element does not compile with jdk1.3.0_01.

How can I avoid such fatal effects for something like a typo in
xsl-stylesheets?

Erwin

Re: VJM crashes on xslt Error

[Donald Ball <ba...@webslingerZ.com>]

On Tue, 23 Jan 2001, Erwin Burgstaller wrote:

> Instead of
>
>       <xsl:value-of select=".">,
>
> I wrote
>
>       <xsl-apply-templates select=".">
>
> which is very bad. It crashes the Java VM (IBMJava2 1.3-2.0).
>
> In the browser you see alternatively a (very long) stack trace for a stack
> overvlow or simply the message "Internal Server Error".
>
> In apaches error_log you see:
>
> SIGILL 4 (*) illegal instruction (not reset when caught)
>         stackpointer=0xbedc1b10
>
> SIGABRT 6 (*) abort process
>         stackpointer=0xbedbffb0
>
>
> Is Sun's Java VM be more stable? I still have the problem with
> org.w3c.dom.Element does not compile with jdk1.3.0_01.

this is a bug in your JVM - we can't do anything about it. report the
error to your JVM manufacturer, and maybe try another JVM.

- donald