Roger,
I don't see an error parsing the pbd. Here are the lines from the AutoProbe logs that I believe show that the pbd is being processed( Please correct me if I am wrong)
Using directives specified in /app/WAS8/IBM/WebSphere/AppServer/wily/core/config/TestCustomPBD.pbd
Starting file dump for /app/WAS8/IBM/WebSphere/AppServer/wily/core/config/TestCustomPBD.pbd
> TurnOn: Tools
> SetFlag: Tools
>
> IdentifyMatchingClassesAs: com.ibm.defaultapplication.* Tools
> #TraceComplexMethodsIfFlagged: Tools BlamePointTracer "ToolsTest|{classname}|{method}"
>
> #TraceOneMethodOfClass: com.ibm.defaultapplication._Increment_Stub getTheValue BlamedMethodTimer "ToolsEngg|Increment_Stub|getTheValue:Average Method Invocation Time (ms)"
> TraceOneMethodOfClass: com.ibm.defaultapplication.IncrementBean getTheValue BlamedMethodTimerHC "ToolsEngg|Increment_Stub|getTheValue:Average Method Invocation Time (ms)"
Finished file dump for /app/IBM/AppServer/wily/core/config/TestCustomPBD.pbd
and then further down in the logs I see the lines like the ones below at various points in the logs. The only one that I don't know how to interpret is the one marked with *** below.
Processing class com/ibm/defaultapplication/ConcreteIncrement_501bb55e
Processing class com/ibm/defaultapplication/IncrementBean
Processing class com/ibm/defaultapplication/_EJSRemoteCMPIncrementHome_501bb55e_Tie
Processing class com/ibm/defaultapplication/_EJSRemoteCMPIncrementHome_501bb55e_Stub
Processing class com/ibm/defaultapplication/websphere_deploy/DERBY_V100_1/IncrementBeanFunctionSet_501bb55e
Processing class com/ibm/defaultapplication/_EJSRemoteCMPIncrement_501bb55e_Tie
Processing class com/ibm/defaultapplication/_Increment_Stub---> How do I interpret these results******** it looks like the below is collected under a different tracer, is that right?
_ids:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
_ids:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
_ids:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
getEJBHome:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
getEJBHome:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
getEJBHome:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
getHandle:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
getHandle:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
getHandle:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
getPrimaryKey:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
getPrimaryKey:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
getPrimaryKey:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
getTheValue:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
getTheValue:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
getTheValue:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
increment:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
increment:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
increment:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
isIdentical:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
isIdentical:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
isIdentical:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
remove:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/CrossProcessCorrelationEjbTracer
remove:0 inserted method tracer object allocation: com/wily/introscope/appmap/agent/trace/hc2/AppMapMarkerTracer
remove:0 inserted method tracer object allocation: com/wily/introscope/agent/trace/hc2/BackendTracer
To answer your 2nd question- There is no clamping on the agent or in the EM ( e.g. historical metrics etc).