Loading...

XML

Word

Printable

Release Note Text:

Hide
Cause: No timestamps in default broker log configuration
Consequence: Difficult to decipher logs
Fix: Added a script that configures the broker log configuration file to include timestamps before every log message in the format: yyyy-mm-dd hh:mm:ss
Result: Logs are easier to interpret

Show
Cause: No timestamps in default broker log configuration Consequence: Difficult to decipher logs Fix: Added a script that configures the broker log configuration file to include timestamps before every log message in the format: yyyy-mm-dd hh:mm:ss Result: Logs are easier to interpret
Target Release:

AMQ63 1.4.0.GA
Workaround Description:

Hide

Using S2I one can probably configure a custom broker logging config

Show
Using S2I one can probably configure a custom broker logging config
Git Pull Request:
https://github.com/jboss-openshift/cct_module/pull/212

The broker log of a broker running on OpenShift does not contain and date and time stamp information.
For production environments this is a must!

The default broker images should use a broker logging config that also logs date and time stamp.

is incorporated by

CLOUD-2734 Upgrade AMQ6.3 image to 1.4