Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #29670

Re: bug shows up depending on whether Java console is there or not.

From Andreas Leitgeb <avl@auth.logic.tuwien.ac.at>
Newsgroups comp.lang.java.programmer
Subject Re: bug shows up depending on whether Java console is there or not.
Date 2014-08-15 01:22 +0000
Organization A noiseless patient Spider
Message-ID <slrnluqo7d.fp3.avl@login.logic.tuwien.ac.at> (permalink)
References <slrnlukl58.fp3.avl@login.logic.tuwien.ac.at> <lsdu57$d6m$1@news.albasani.net>

Show all headers | View raw


Marcel Mueller <news.5.maazl@spamgourmet.org> wrote:
> On 12.08.14 19.53, Andreas Leitgeb wrote:
>> Now comes the strange part:  with 1.6.0_u51, that code block throws
>> an JAXBException, but only if the java console is hidden.  As soon
>> as the console is activated, code runs through perfectly normal (as
>> it did up to 1.6.0_u45 regardless of console).
>>
>> Is this "proof" that something is wrong with _u51, or could anyone
>> think of a programming error that would show up only with a specific
>> version and depend on console visibility and cause a JAXBException
>> to be thrown?
>
> Almost anything could happen in case of a race condition.
> Console access could serialize things that otherwise run in parallel.
> Of course, I'm just guessing.

Thanks for the guess, but that likely isn't the case here.

The code within the try-block doesn't really attempt to write to
the console. All logging activities are governed by a debugging flag,
and even when that flag is false, the presence or absence of console
still made a reliably *reproducible* difference.

I still keep it in backhead, though.

>> On top of that, the getLocalizedMessage() method on the
>> thrown exception returns null, and thus we don't really get much
>> information about the problem itself.
>
> What about the call stack? Try to find the corresponding throw in the 
> Java source.

That will be subject to check in the next days. 
My hopes are not very high (based on the null from getLocalizedMessage())
to find any other sensible information, but it is definitely worth a try.
(I need to add some code for that and have the user check again, as the
stack-trace of the JAXBException isn't currently visible to the user. So,
it'll take some time.)

Thanks!

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

bug shows up depending on whether Java console is there or not. Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-08-12 17:53 +0000
  Re: bug shows up depending on whether Java console is there or not. Marcel Mueller <news.5.maazl@spamgourmet.org> - 2014-08-12 22:41 +0200
    Re: bug shows up depending on whether Java console is there or not. Andreas Leitgeb <avl@auth.logic.tuwien.ac.at> - 2014-08-15 01:22 +0000
      Re: bug shows up depending on whether Java console is there or not. Marcel Mueller <news.5.maazl@spamgourmet.org> - 2014-08-15 11:07 +0200

csiph-web