directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] [Commented] (DIRSERVER-1855) java.lang.IllegalStateException: Can't overwrite cause at
Date Wed, 12 Jun 2013 14:11:20 GMT


Emmanuel Lecharny commented on DIRSERVER-1855:

Absolutely right : we swallow the exception, which is damn wrong.I just committed a fix for
that (

Now, the pb is that I don't see why you get an error at startup...

However, a big issue has been fixed since 2.0.0-M9 in the way we handle groups : we weren't
able to fetech them back on startup, and my bet is that you get a NPE somewhere in the loop.

I strongly suggest to load all the data in a more recent version (be aware that important
the data will be problematic, as the full export of all your data won't be ordered, so importing
them in the new server will require many imports or a reordering of the data. This is an issue
we are working on.
> java.lang.IllegalStateException: Can't overwrite cause at
> -------------------------------------------------------------------------------------------------------------------------------------------
>                 Key: DIRSERVER-1855
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 2.0.0-M12
>            Reporter: Konrad Windszus
>            Priority: Critical
> We got the following exception stack trace after trying to start ApacheDS from a backup:
> {code}
> 14:37:15] ERROR [] - Failed
to start the service.
> java.lang.IllegalStateException: Can't overwrite cause
>         at java.lang.Throwable.initCause(
>         at
>         at<init>(
>         at
>         at
>         at
>         at
>         at
>         at
>         at
>         at org.tanukisoftware.wrapper.WrapperManager$
> {code}
> The problem here really is, that this exception hides the real problem here. I see that
even in the trunk you try to set the cause in
in the initializeMethod. That is not allowed and leads to that exception if the original exception
already has a cause set (
Rather just wrap the original exception and leave out the initCause or at least check first,
if the initCause is allowed at that point. Also please remove the e.printStackTrace as it
will land in the standard error stream rather than in the log.

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:

View raw message