FYI, exception chaining in the JDK was introduced in 1.4. Though that
is ancient :), the JDO code was intentionally kept to run with 1.3 for a
while, then in somewhat of a maintenance mode, which is probably why it
didn't call the correct superclass constructor.
Rochelle
Scott Oaks wrote:
>
> Well, the JDOFatalInternalException in this case doesn't chain properly,
> which I didn't realize until just now when I went to look at it: it is
> constructed with the other exception as an argument, but its
> implementation doesn't call the correct superclass constructor for that
> to work. So I was incorrectly blaming the fact that I don't see any
> information on the root cause on the JDK giving up printing stack traces
> after it had dumped a few hundred lines of output. [A few hundred
> lines...bad enough!]
>