[QPID-4515] Java Broker: improve logging, especially for diagnosis of transactional messaging performance

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.20
• Fix Version/s: 0.21
• Component/s: Broker-J
• Assignee: Keith Wall
• Reporter: Phil Harvey
• Created: 19/Dec/12 17:52
• Updated: 24/Dec/12 17:06
• Resolved: 24/Dec/12 17:06

Description

I've recently been involved in a number of support issues where we were diagnosing performance problems.

We were trying to find out at which point in the message flow a delay was occurring, and identified a number of areas where debug logging should be added or improved to facilitate this.

We particularly want to track:

1. The points when frames are received and sent by the broker, including in AMQP 0-8/0-9/0-9-1 environments.
2. How long BDB commits are taking.
3. How long post-commit actions are taking