Prev: How to use JSESSIONID on follow-on request without basic auth?
Next: Runtime Devirtualization
From: segalsegal on 22 Jan 2010 15:46
On Jan 20, 12:47 pm, RedGrittyBrick <RedGrittyBr...(a)SpamWeary.invalid>
wrote:
> Have you considered catching more specific exceptions?
>
> >    {
> >            System.out.println("Couldn't show in browser: " + e);
> >    }
> > }
>
> Is that useful?
>
> I'd log the exception (and preferably a stack trace) to a file that can
> be attached by the end-user to an email.

Good point. I should see if this is throwing an exception, since if
an exception is thrown, at the minimum I could then try some of the
approaches that Roedy Green details at http://mindprod.com/jgloss/browserlaunching.html.
I am a bit limited by not having been able to reproduce this problem
on any computer I've tried, and the fact that our users are medical
experts, not computer experts. But now that I have suggestions of
what to try that is different it seems worthwhile to get the doctors
to help debug this problem, assuming that it is still present (it was
gone for one of the two doctors today, as detailed elsewhere in this
thread).

I'll report back if I get more information.

Thanks for the help. It is great to know that Roedy and the others
are still as helpful as in the old days when we were all new to Java.
First  |  Prev  | 
Pages: 1 2 3
Prev: How to use JSESSIONID on follow-on request without basic auth?
Next: Runtime Devirtualization