GenericJMSRA would benefit from separately configurable loggers

[arinban]

The present GenericJMSRA implementation uses a single java.util.logging.Logger, identified by its name "com.sun.genericjmsra", for all logging purposes.

(NB This is true even when the resource adapter is deployed multiple times within a single application server, which apparently was never intended but which otherwise works just fine on GlassFish 2 and 3.)

It would be desirable to create multiple (child) loggers so that each Admin Object (for outbound queues/topics) or ActivationSpec (for inbound ones) could have its own log level setting and so that log entries originating with different queues/topics could be correlated with separate logger names. The current situation results in confusing and less-than-truly-helpful server logs in real-world situations when multiple inbound and outbound queues are involved and the (global) log level is cranked up for troubleshooting.

Environment

GlassFish (2.1.1 or 3.1.2), Linux (SLES10SP2, SLES11SP2), x86_64

Affected Versions

[0.9, 1.0a, 1.0, v1.5, 1.5, v1.6, 1.6, 2.1a, 2.1b, current, 2.2a]

[arinban]

• Issue Imported From: https://github.com/ari-ban/test1/issues/59
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented

• Issue Imported From: https://github.com/ari-ban/glassfish-genericjmsra/issues/59
• Original Issue Raised By:@arinban
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented

• Issue Imported From: https://github.com/javaee/glassfish-genericjmsra/issues/59
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @glassfishrobot

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented Reported by gerhard_niklasch

[arinban]

@arinban Commented @arinban Commented @glassfishrobot Commented This issue was imported from java.net JIRA GENERICJMSRA-59

[arinban]

Closing this as this issue is migrated to https://github.com/ari-ban/test1/issues/59