Re: [Exist-development] Java exceptions crash the server

[Dannes W. <da...@ex...>]

Hi,

On Tue, Feb 22, 2011 at 8:35 AM, Lauri Hyttinen
<lau...@ho...>wrote:

>  My code causes an org.w3c.dom.DOMException with a HIERACHY REQUEST ERROR
> being the cause and this causes eXist to shut down.
> Earlier I had a null pointer exception which also caused the same effect.
> The null pointer exception is fixed and I am in the process of addressing
> the DOMException.
> But regardless of the exception is eXist supposed to shut down when a java
> module does these things?
>
> I know I have to write better java code :) but still it would be easier on
> the mind when I did not crash the server with my faulty java module.
>

it is unlikely that such an exception crashes the database. To understand
your issue better I'd need to see the stacktraces.

In general: if the databases stops to respond, in many cases  the 'broker'
is never returned to the 'brokerpool'. This is fatal since there is just a
limited number of brokers available.

regards

Dannes

-- 
eXist-db Native XML Database - http://exist-db.org
Join us on linked-in: http://www.linkedin.com/groups?gid=35624