"I was running 1.6.0_18 yesterday and today 1.6.0_19 and I hit it both
times."
Hi Richard, You mean running the same apps in JDK 1.6.0_18 did not hit
this issue, it only happened using JDK 1.6.0_19 ?
Thanks to Paul, Kristian jump in to help!
Judy :-)
Richard Kolb wrote:
> Hi Kristian
>
> On 7 April 2010 14:55, Kristian Rink <rink_at_planconnect.de
> <mailto:rink_at_planconnect.de>> wrote:
>
> Am 07.04.2010 14:49, schrieb Richard Kolb:
>
>
> Is anyone else hitting this issue on a regular basis ?
> It really frustrates me as I seem to hit this almost every day
> while
> doing web development in NetBeans 6.8.
> And these are test projects, nothing big at all.
>
>
> Well, I am not running into this on a regular basis but it seems
> reproducible as soon as the webapps to be deployed get a little
> larger and I do deploy frequently. Never managed to track down why
> it _actually_ happens, though - usually restarting the server
> resolved things, and so far I never ran into this in production
> environment... :)
>
>
> Thanks very much for this. There was an issue with JDK 1.6.0_16 I
> think. Something to do with AWT keeping a reference to an object
> believe it or not.
> Which JDK are you running ?
>
> I was running 1.6.0_18 yesterday and today 1.6.0_19 and I hit it both
> times.
>
>
> regards
> Richard.
>