
during a reco job, we are seeing many unprotected debug messages each event, which should either be protected or removed, coming from:

emtopo35clustermaker.calorunclustercorrectionstopo35gam35.removebad_gam35topo35/debug
emtopo35clustermaker.calorunclustercorrectionstopo35gam35.layers_gam35topo35/debug
emtopo35clustermaker.calorunclustercorrectionstopo35gam35.time_gam35topo35/debug
emtopo35clustermaker.calorunclustercorrectionstopo35gam35.larupdate_gam35topo35/debug

seen here:

http://atlas-pmb.web.cern.ch/atlas-pmb/arch-mon/?test=msg/dev__x86_64-slc5-gcc43-dbg#plot_totalmsgsvcabusesduringashortjob

this is seen in dev (devval is also available on the page via the same menu). find more information on the link if you are not aware of what it means to protect debug output.

cheers,
thomas

ps. a priori the fix is just needed in dev.

pps. likely related (but i will open separate bug reports and post links here afterwards) are the unprotected debug messages in: 
 toolsvc.egammaswtool.calorunclustercorrectionsegele372.calhits_global_ele37eg2/debug
toolsvc.egammaswtool.calorunclustercorrectionsegele552.calhits_global_ele55eg2/debug
larclustermaker.calorunclustercorrectionsele35.calhits_global_ele35/debug



