I'm experiencing some odd behavior while connecting the NetBeans
debugger to an instance of GlassFish. This is the issue I reported
there:
http://www.netbeans.org/issues/show_bug.cgi?id=115033
and this is the response I got from one of the NetBeans developers:
> Aha, I see what's going on now. There are several copies of each class
> loaded by different class loader.
> The GlassFish apparently contains all classes that were ever deployed.
> Therefore when breakpoints are submitted, they
> are naturally trying to be submitted into all these copies. And when
> line number changes, it can easily happen that some
> locations in some copies becomes invalid (there is no executable
> code). This is why you get notification that the
> breakpoint is invalid and subsequently it's successfully submitted
> into a different copy of the same class.
>
> IMHO this is a defect of the GlassFish, since you probably do not care
> about the old copies, which only take up space.
> But I might be wrong. If it is desired to have multiple different
> copies loaded, I will try to find some solution how to
> silently ignore the invalid messages.
Can someone help me to understand what's happening here?
--
____________________________________________________________
Glenn Holmer gholmer_at_weycogroup.com
Software Engineer phone: 414-908-1809
Weyco Group, Inc. fax: 414-908-1601