Azure Worker Role generating writing unexpected error to Trace log storage -

we have worker role running in cloud polls azure cloudqueue periodically retrieving messages web role has put on there us. worker role , web role housed in same cloud service application , running 1 instance.

as testing have our logging switched on , contents of messages , other useful information appear in our cloud storage view using cerebrata azure diagnostics manager. (great product btw)

diagnosticmonitorconfiguration diagconfig = diagnosticmonitor.getdefaultinitialconfiguration();

diagconfig.logs.scheduledtransferloglevelfilter = loglevel.verbose;

it appears work remarkably actually, see verbose message in trace log has "fail"as message. code appears generated wrapped in try catch odd aren't seeing message through means.

it appear happening out of our code's control, perhaps worker role being restarted, or cloud op system detecting major error can deal restarting our worker role. recovers , carries on of mystery might happening.

what haven't ascertained yet whether losing message.

any gratefully appreciated. cheers kindo malay

without stack trace it's hard much, logging set verbose it's quite you're seeing internal logging 1 of dlls you're using.

for example if run azure table query causes kinds of errors, error logged out 3 times because storage client library catching error, tracing out , retrying.

if error not being caught try catch block, it's nothing need worry about.

if deliverability of queue messages important you, should ensure make use of visibility timeout overload of cloudqueue.getmessage , delete message when you've finished processing it. may end processing messages twice, @ least process of them.