Suppress internal processing output on executing asadmin create-local-instance

[dmiya3]

Internal processing message "Extracted transferred entry ..." [*1] is output on executing asadmin create-local-instance.

# /opt/glassfish7-org/glassfish/bin/asadmin create-local-instance --cluster cluster1 cluster1-1
Rendezvoused with DAS on localhost:4848.
Port Assignments for server instance cluster1-1: 
OSGI_SHELL_TELNET_PORT=26666
JAVA_DEBUGGER_PORT=29009
JMS_PROVIDER_PORT=27676
HTTP_LISTENER_PORT=28080
IIOP_SSL_LISTENER_PORT=23820
ASADMIN_LISTENER_PORT=24848
IIOP_SSL_MUTUALAUTH_PORT=23920
JMX_SYSTEM_CONNECTOR_PORT=28686
HTTP_SSL_LISTENER_PORT=28181
IIOP_LISTENER_PORT=23700
Extracted transferred entry config/keystore.jks of size 6,221 B to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/keystore.jks [*1]
Extracted transferred entry config/cacerts.jks of size 2,495 B to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/cacerts.jks [*1]
Command create-local-instance executed successfully.

FYI, we can still view the internal processing with environment variables (AS_TRACE / AS_DEBUG).

# export AS_TRACE=true
# /opt/glassfish7-org/glassfish/bin/asadmin create-local-instance --cluster cluster1 cluster1-1
...
---- END PAYLOAD ----
Copyied 6,221 bytes to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/keystore.jks
Extracted transferred entry config/keystore.jks of size 6,221 B to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/keystore.jks [*1]
Copyied 2,495 bytes to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/cacerts.jks
Extracted transferred entry config/cacerts.jks of size 2,495 B to /opt/glassfish7-org/glassfish/nodes/localhost-domain1/cluster1-1/config/cacerts.jks [*1]
doHttpCommand succeeds
loadClass(name=com.sun.enterprise.admin.util.CommandModelData$ParamData, resolve=false)
Command create-local-instance executed successfully.

Signed-off-by: dmiya3 [email protected]

[dmatej]

Honestly I was missing these logs when we had issues on production and sometimes we were not sure if something changed or not.

What I do believe is more important - please tell me if this is the real problem for you: asadmin spams user output which is parsed by some script - because the asadmin uses STDOUT both for logging and for user communication. I already created an issue for that: #25169

The GFLauncherLogger class uses STDOUT instead of STDERR, but even worse, it mixes user communication and logs so we cannot simply switch that as it would create other issues.

For now I will approve this (so it would stop breaking scripts), after #25169 these logs should be config/info level, but in STDERR instead of STDOUT.