dev@glassfish.java.net

serviceability

From: Carla Mott <Carla.Mott_at_Sun.COM>
Date: Wed, 22 Jul 2009 16:31:19 -0700

Hi all,

We need to update the resource bundles to contain diagnostic information
for all SEVERE and WARNING messages.

In evaluating the serviceability requirements for GlassFish we found
that there is missing information from the resource bundles. The
requirement states:

The product shall include the following information in every log entry:
  Timestamp- preferably in a standard format; Module - Acronym of the
module generating the message: LogLevel - Indicates relative
severity(following an applicable standard if any); MessageId - Unique
withing the product: Message Text - brief text message explaining the
message; ContextInfo - key values that go with the message (context),
include stack trace if program error is suspected; Recommendation -
recommended actions to take to further determine the cause of a problem
(not the actual solution).

We have most of this but in many cases we are missing the recommendation
  or what we call the diagnostic part. We agreed that all SEVERE,
WARNING and INFO messages must have a message id. For the most part
that seems to be true but I could not easily determine if all SEVERE
messages have a message id. The message id is important for this task.
  I have created a wiki page which lists the
resource bundles that have diagnostic messages and which resource
bundles don't. We would like to get to a point where all SEVERE, and
WARNING messages have diagnostic information. The first pass is
targeting all SEVERE messages for code that is in the GlassFish source
repository and we're targeting this to be complete by August 3rd.

http://wiki.glassfish.java.net/Wiki.jsp?page=GlassFishV3LoggingServiceability


Please go through the resource bundles listed and verify that all SEVERE
and WARNING messages have a message id. If any diagnostic information is
missing please provide that in the resource bundle and update the table
on the wiki when complete. We'd like to cover all WARNING messages by
August 17.

I can produce a list of message ids which have diagnostic messages but
not sure how useful that is at this point. I can provide that info if
needed.


Thanks for your help

Carla