Package com.adaptris.profiler
Using the profiler will require aspectjweaver
to be
listed as a javaagent when starting the JVM. The recommendation is to
not use the bundled wrapper executables, and to roll your own script
that provides the correct startup parameters to your JVM. The aspects
themselves are stored in META-INF/profiler-aop.xml
which means
that you need to set the appropriate aspectj system property to enable
the aspects
By default, the profiler does ot do anything other than inject aspects
at the appropriate places for Workflow/Service/Producer. In order to
get meaningful information you will need a concrete implementation of
PluginFactory
which needs to be
specified in the file interlok-profiler.properties
(this should be
available on the classpath).
com.adaptris.profiler.plugin.factory=my.implementation.of.com.adaptris.profiler.client.PluginFactory
You should switch to using SimpleBootstrap to start the adapter and build the classpath
manually in your script.
COREJARS=`ls -1 lib/*.jar`
for jar in $COREJARS
do
CLASSPATH=$CLASSPATH:$jar
done
LOCALCLASSPATH=$CLASSPATH
export JAVA_HOME=/opt/java/jdk1.7
JAVA_ARGS="-server -XX:+UseConcMarkSweepGC -XX:+UseParNewGC"
$JAVA_HOME/bin/java -javaagent:./lib/aspectjweaver.jar \
-Dorg.aspectj.weaver.loadtime.configuration=META-INF/profiler-aop.xml -cp "$LOCALCLASSPATH" $JAVA_ARGS \
com.adaptris.core.management.SimpleBootstrap bootstap.properties
-
Interface Summary Interface Description InterlokProfilerPlugin Interface defining additional lifecycle steps for profiler implementations that require it.ProcessStep -
Class Summary Class Description MessageProcessStep ProfilerSettings ReflectionHelper -
Enum Summary Enum Description StepType