When I have a test webapp installed, the web container makes sure it
does not load the test webapp on __asadmin virtual server (4848) because
we treat asadmin virtual server as special and do not load webapps on it.
However, after starting the server, the first access to
http://localhost:4848/testwebapp always returns 200 immediately and
shows the GlassFish Administration Console page (loading the admin
console).
"GlassFish Administration Console
GlassFish Administration Console - Installation in Progress...
The browser will refresh automatically, or you may press reload on your
browser.
Loading of the GlassFish Admin Console is in progress..."
After a few seconds later, it then goes to 404 as the testwebapp isn't
available on asadmin virtual server - 404 is expected. If you access
the page for the 2nd time, you get 404 as expected.
It seems that access to 4848 port triggers admin console loading
immediately regardless if the resource is available or not. Where is
this handled?
Thanks,
Amy