# Further logging configuration
# Excalibur logging provides the facility to configure logging using
# configuration files written in XML. This allows for such features as
# log file rotation which are not supported directly by JMeter.
#
# If such a file specified, it will be applied to the current logging
# hierarchy when that has been created.
#
#log_config=logkit.xml
in jmeter.properties so tried adding the line
to a jmeter.properties in /src/test/jmeter and I got an error:
FATAL - jmeter.JMeter: An error occurred: java.lang.NoClassDefFoundError: org/apache/avalon/excalibur/i18n/ResourceManager
at org.apache.avalon.excalibur.logger.DefaultLogTargetFactoryManager.<clinit>(DefaultLogTargetFactoryManager.java:44)
at org.apache.avalon.excalibur.logger.LogKitLoggerManager.setupTargetFactoryManager(LogKitLoggerManager.java:423)
at org.apache.avalon.excalibur.logger.LogKitLoggerManager.configure(LogKitLoggerManager.java:400)
at org.apache.jorphan.logging.LoggingManager.setConfig(LoggingManager.java:139)
at org.apache.jorphan.logging.LoggingManager.initializeLogging(LoggingManager.java:104)
at org.apache.jmeter.util.JMeterUtils.initLogging(JMeterUtils.java:149)
at org.apache.jmeter.JMeter.initializeProperties(JMeter.java:527)
at org.apache.jmeter.JMeter.start(JMeter.java:292)
this class seems to exist in the jar with pom plugin dependency:
<dependency>
<groupId>excalibur-i18n</groupId>
<artifactId>excalibur-i18n</artifactId>
<version>1.0</version>
</dependency>
which goes against the versions of excalibur jars that gets put in target/jmeter/libs from running a build:
excalibur-datasource-1.1.1.jar
excalibur-instrument-1.0.jar
excalibur-logger-1.1.jar
excalibur-pool-1.2.jar
Adding the dependency allows the build to complete but my logkit.xml or even the default one that gets into target/jmeter/bin (?) don't seem to be working even though I have no errors.
Has anyone tried using this advanced logging either with jmeter or with the plugin?
Cheers
Nomit