Hi, Intended to do the $subject.
We have a lot of debug logs. Some are per message. When troubleshooting an issue this is almost the only way to identify the problems (race conditions - threading issues etc). We intend to separate out the debug logs in our control (cannot help qpid internals) as below 1. Non per-message logs : subscription information logs/how many messages were read/how many messages were moved etc etc 2. Per message logs: add as "Trace" level logs with a separate appender like in ESB. >>Message with id x came to the sever >>Message x metadata were written >>Message x content chunk y is written >>Message x was cut from Global Queue a to node queue b >>Message x was read from Node queue b >>Message with id x was sent to the subscriber s1 >>Message with id x was sent to the subscriber s2 >>Message with id x was acked sy subscriber s1 >>Message with id x waas acked by subscriber s2 >>Message with id x is considered delivered and removed from store. >>Content belonging to message x was removed from store Is this the correct approach? WDYT? Thanks. -- *Hasitha Abeykoon* Software Engineer; WSO2, Inc.; http://wso2.com *cell:* *+94 719363063* *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
