summaryrefslogtreecommitdiff
path: root/java/client/src
diff options
context:
space:
mode:
authorRajith Muditha Attapattu <rajith@apache.org>2007-11-12 18:08:15 +0000
committerRajith Muditha Attapattu <rajith@apache.org>2007-11-12 18:08:15 +0000
commit0823169a6eedf63763099ef5a175593c6d340dd2 (patch)
tree41e80084d6b05ebff58917478cef777cd2d623be /java/client/src
parent82362e02efb289ef0c964b7034ccaa10ca4923a6 (diff)
downloadqpid-python-0823169a6eedf63763099ef5a175593c6d340dd2.tar.gz
Added a new set of performance tests which is more focused on getting the throughput.
The producers and consumers can be run from separate machines. There is no pass/fail, it merely records message count, memory etc at periodic intervals and prints a summary at the the end of the test. Since there are periodic entries, you could identify the rough time time it crashed and memory consumption etc. git-svn-id: https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid@594239 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/client/src')
-rw-r--r--java/client/src/main/java/client.log4j7
1 files changed, 3 insertions, 4 deletions
diff --git a/java/client/src/main/java/client.log4j b/java/client/src/main/java/client.log4j
index c7b6630987..7cab6895dc 100644
--- a/java/client/src/main/java/client.log4j
+++ b/java/client/src/main/java/client.log4j
@@ -23,11 +23,10 @@ log4j.rootLogger=${root.logging.level}
#log4j.additivity.org.apache.qpid=false
#log4j.logger.org.apache.qpidity.transport=TRACE, console
-log4j.logger.org.apache.qpid=MAJOR, console
+log4j.logger.org.apache.qpid=ERROR, console
log4j.additivity.org.apache.qpid=false
-log4j.logger.org.apache.qpidity.transport=MAJOR, console
-log4j.logger.org.apache.qpid.testutil.QpidTestCase=MAJOR, console
-
+#log4j.logger.org.apache.qpidity.transport=DEBUG, console
+#log4j.logger.org.apache.qpid.client.message.AbstractBytesTypedMessage=DEBUG, console
log4j.appender.console=org.apache.log4j.ConsoleAppender
log4j.appender.console.Threshold=all