V2 and V3 have the same default port structure (HTTP = 8080, admin = 4848, etc.)

If two similarly configured V2 and V3 server instances are added to the Servers node in the IDE, and the V3 instance is
running, then, sometimes in response to user activity and sometimes spontaneously, the V2 plugin will attempt to
synchronize the V2 instance node with the V3 server process.  When this fails (sometimes after a timeout), an incorrect
modal message box is displayed (image attached) with the following (incorrect) text:

    Authentication for GlassFish V2 failed with message 
    http://localhost:4848/web1/remotejmx.
    
    If the username or password is incorrect, you can change them via Tools | Servers.

There are some circumstances where the box is displayed repeatedly and is rather annoying, but I can't recall the
circumstance.

This happens because the server signatures are similar as well as the recognition algorithm in the respective plugins
and the V2 plugin is trying to talk to the V3 instance, not realizing it is a different server entirely.

What should happen here is V2 should realize at some reasonable point that the server process is not V2 at all and
ignore it.  Exactly what "some reasonable point" means and to what certainty we can differentiate between "bad password
for V2" and "not V2 at all" is left as an exercise for the person who gets to resolve this :)