| Summary: | as5 plugin: "Client JAR [file:/foo.jar] does not exist or is not readable (note, this JAR may not be required for some app server versions)." warnings should not be logged for AS/EAP versions that do not require the corresponding jar | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [JBoss] JBoss Operations Network | Reporter: | Ian Springer <ian.springer> | ||||
| Component: | Plugin -- JBoss EAP 5 | Assignee: | Jay Shaughnessy <jshaughn> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Armine Hovsepyan <ahovsepy> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | JON 3.2, JON 3.2.1 | CC: | ahovsepy, ccrouch, hrupp, jshaughn, loleary, mfoley | ||||
| Target Milestone: | ER02 | ||||||
| Target Release: | JON 3.3.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
If a version of JON did not require a particular JAR, a "Client JAR does not exist or is not readable (note, this JAR may not be required for some app server versions)" warning would be logged whenever a server was discovered, or rediscovered. This caused unnecessary information in the logs, and caused customers to be concerned about the errors due to the severity of the log level. The fix changes the WARN-level message to DEBUG level. While it is not possible to distinguish between non-existent and non-readable JARs, activating the DEBUG log level will identify the originally-reported behavior, and the issue can then be investigated further.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-12-11 14:02:27 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Ian Springer
2012-02-13 16:39:37 UTC
per triage 2/13/2012 (asantos, crouch, foley, loleary)
master commit bed4b9a72f3f6ec19939e82a9fd27e392dc85a9c
Author: Jay Shaughnessy <jshaughn>
Date: Wed Aug 20 10:48:59 2014 -0400
I changed the offensive WARN-level message to DEBUG level. It's not really
possible to distinguish between non-existent and non-readable, or to know
which versions require which JAR. If there is a failure then we can turn
on debug to see the message.
release/jon3.3.x commit 038e60bf5b05101680a5693a18d2f492c287230e
Author: Jay Shaughnessy <jshaughn>
Date: Wed Aug 20 10:57:23 2014 -0400
Cherry-Pick master bed4b9a72f3f6ec19939e82a9fd27e392dc85a9c
Moving to ON_QA as available for test with the following brew build: https://brewweb.devel.redhat.com//buildinfo?buildID=381194 Created attachment 936171 [details]
eap5_debug_log
verified in JON 3.3 ER02 'JAR may not be required for some app server versions' is logged as Debug message. screen-shot attached |