Bug 1296454 - info log "Skipping message id in translation" to be debug with more details
Summary: info log "Skipping message id in translation" to be debug with more details
Keywords:
Status: NEW
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-cpp
Version: 3.2
Hardware: x86_64
OS: Linux
medium
low
Target Milestone: ---
: ---
Assignee: messaging-bugs
QA Contact: Messaging QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-07 10:01 UTC by Pavel Moravec
Modified: 2020-11-04 22:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Pavel Moravec 2016-01-07 10:01:31 UTC
Description of problem:
When sending an AMQP1.0 message with message ID in non-UUID format and when consuming the message via AMQP 0-10 client, qpid broker logs info statement:

2016-01-07 10:48:54 [Broker] info Skipping message id in translation from 1.0 to 0-10 as it is not a UUID

The message as is is useless, since it is without any identification details (i.e. what message ID it was, what queue it is stored in, or so). Also it is makes sense to have the log statement of lower verbosity (i.e. debug) since the message id conversion is known.


Version-Release number of selected component (if applicable):
qpid-cpp-server-0.30-5


How reproducible:
100%


Steps to Reproduce:
1. qpidd --log-enable=info | grep Skipping &
2. qpid-send -a "test; {create:always}" -m1 -i "pokus" --connection-options "{protocol:'amqp1.0'}"
3. qpid-receive -a test --print-content=no --print-headers=yes


Actual results:
running qpidd logs:

2016-01-07 10:48:54 [Broker] info Skipping message id in translation from 1.0 to 0-10 as it is not a UUID


Expected results:

The log statement to be ideally debug level.

The statement itself to contain some identification of the message (i.e. message subject, ID to be lost or so).


Additional info:


Note You need to log in before you can comment on or make changes to this bug.