05294: | OpenJMSServer creates immense logfile upon each instantiation |
Category: Connector
Status: ClosedSeverity: MEDIUM
Reported against release: 0.9
Fixed in release: 0.9.1
PROBLEM:Each time the OpenJMSServer is started, it creates a 280K log file
(before any publishers or subscribers run). This could potentially be
serious, filling up disk space quickly. ANALYSIS:In the 0.9 release, the OpenJMS server component was modified to have a
wrapper that published attributes about the server as an Openwings
service. This wrapper therefore uses Component Services, which loads
policies. For some reason, when running in the OpenJMS server, the
Openwings Policy Services is unable to locate the schema (*.xsd) files
for the policies loaded by Component Services. The XML parsing error
handler utilized by Policy Services prints out errors withoug checking
the "policy" log level, resulting in voluminous output.
Note that these error messages are recoverable errors - the policy XML
documents are not validating correctly since the schema is not found.
The OpenJMS server component needs to have it's policy path configured
correctly, and Policy Services should be updated so that error logging
is controlled by the "policy" log level. |
