Hi Anuja,

Some of the information i could think of,

1) JMS levels header information i.e arrival time stamps
2) Message content itself ? (in this case we might need to think about the
message sizes as well tracing large messages etc might lead into several
issues, format i.e whether its binary/plain text)
3) Also for AMQP the frame information (frame number)
4) For MQTT we could include (QoS level, retain status, whether this
message is a retry (duplication flag))

Also, for each message we might need a way to distinguish the trace message
? maybe from the id ? so that we could track the state of it at different
layers (i.e Message inbound handlers, slot delivery worker, message
flusher, delivery handlers)

Thanks,
Pamod

On Fri, Jun 5, 2015 at 10:52 AM, Anuja Herath <an...@wso2.com> wrote:

> Hi,
>
> Related to Jira [1], we need to add a trace level log when every time a
> message is received. What information of the received message can be useful
> to include in the log message?
>
> [1] https://wso2.org/jira/browse/MB-803
>
> --
> Anuja Herath
> *Software Engineer*
> *WSO2, Inc.*
> Mobile : +94 (0)71 429 8861
>
> _______________________________________________
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
*Pamod Sylvester *

*WSO2 Inc.; http://wso2.com <http://wso2.com>*
cell: +94 77 7779495
_______________________________________________
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to