OK, I built V3 and then started the domain fine. I see that
Grizzly comes up fine at port 8080. Then I deploy a war file like:
"asadmin deploy --port 8080 foo.war", which successfully deploys.
So, does it mean that the administrative commands are handled by
the Grizzly listener at 8080, where user applications are deployed?
Is this by design, or we are in process of directing asadmin commands
to a separate Grizzly listener (usually at 4848, like we do for V2)?
Dazed and Confused in Santa Clara :)
- Kedar