Ken Cavanaugh wrote:
Carla Mott wrote:
Hi,
Those of you who have code added to GlassFish via a binary integration
please send me the names of the loggers that you are using. I noticed
that there are logger such as 'Grizzly', 'org.jvnet.hk2.osgiadapter',
'org.glassfish.web.osgi' and more. I'd like to add these logger names
to the logging.properties file so that the GlassFish tools (cli and
admin gui) can be used to update the log levels.
Please send me a list of logger names that should be added to the
logging.properties file in GlassFish so that users can easily update
the log levels.
Thanks,
Carla
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: dev-help@glassfish.dev.java.net
All of the ORB logger names start with
javax.enterprise.resource.corba.ee.S1AS-ORB.
Actually there are also some ORB loggers that start with
javax.enterprise.resource.corba.ee._CORBA_.
This class corresponds to the RMI-IIOP code and other places where the
is no ORB instance available.
The S1AS-ORB name is used for the single ORB instance that is created
in the app server.
This is probably another good reason to just keep the ORB logging at
the javax.enterprise.resource.corba level.
Ken.
javax.enterprise.resource.corba
is already in logging.properties, and I
don't know if you want to
add a finer level of control than that for the ORB, but mostly I think
people are happy with just
setting the level for all loggers.
The current ORB loggers under the prefix are:
- rpc
- presentation
- encoding
- protocol
- transport
- naming
- orbd (these are not used in GlassFish)
- locator
- activator
- repository
- servertool
- orb
- oa
- rmiiiop
- util
Ken.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@glassfish.dev.java.net
For additional commands, e-mail: dev-help@glassfish.dev.java.net