On a different, does anyone else view these sequential messages as
conflicting and potentially confusing?
test-listener create failed.
Command create-http-listener executed successfully.
I don't believe the user here is interested in knowing that the act of
sending the command to the server and receiving the failure code back
was successful (at least I think that's what it means -- please correct
me if I'm mistaken). What is the reason for printing the second message
when command submission is successful? Can we not do it, at least in
places such as above where it is both unnecessary and potentially confusing?
-Peter
Amy Roh wrote:
> I can no longer asadmin create-http-listener
>
> ====
> ...glassfish\bin\asadmin create-http-listener
> --listeneraddress=0.0.0.0 --listenerport=9090 --defaultvs=server
> test-listener
>
> test-listener create failed.
>
> Command create-http-listener executed successfully.
> ===
>
> The listener does not get created (note conflicting messages above).
> I don't observe any events getting generated either.
>
> Is this a known issue?
>
> Thanks,
> Amy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>