[AXISCPP-181] Entry/exit trace performance bad with trace off

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3 Final
• Component/s: Basic Architecture
• Assignee: Mark Whitlock
• Reporter: Mark Whitlock
• Created: 01/Oct/04 10:03
• Updated: 12/Oct/04 15:38
• Resolved: 12/Oct/04 15:38

Description

When Axis C++ is built with trace entry/exit and run with trace off,
performance is impacted because the trace tool generates...
if (g_pAT) {
... Do trace stuff ...
}
g_pAT is null before trace is initialised, but is not null when trace
is initialised but off. So the the string manipulation and invoking
the trace class happens before we realise trace is actually off. This
works, except that it hits performance. The trace tool should generate
if (g_pAT && g_AT->traceOn())
or something similar.