summaryrefslogtreecommitdiff
path: root/java/test-profiles/default.testprofile
diff options
context:
space:
mode:
authorMartin Ritchie <ritchiem@apache.org>2009-09-21 15:41:33 +0000
committerMartin Ritchie <ritchiem@apache.org>2009-09-21 15:41:33 +0000
commita5283e144f9107e3e735379ddd68d8d29e9fdb53 (patch)
tree0e1240f794a59d7a2647503b18151c8f76e44c11 /java/test-profiles/default.testprofile
parent9e349f53ccbb1f41156df7ff32f99c1030aa4f68 (diff)
downloadqpid-python-a5283e144f9107e3e735379ddd68d8d29e9fdb53.tar.gz
FailoverBaseCase has not been using the testprofile defined test.port.alt for the failover server. As a result the connection has been failing. Updated to use correct system property and added text to both default.testprofile and test-provider.properties to ensure that the changes are made in both locations, Ideally JNDI connection would use the same system property that is used by QTC for starting the broker. However I don't believe that it is currently doing that.
git-svn-id: https://svn.apache.org/repos/asf/qpid/trunk/qpid@817295 13f79535-47bb-0310-9956-ffa450edef68
Diffstat (limited to 'java/test-profiles/default.testprofile')
-rw-r--r--java/test-profiles/default.testprofile2
1 files changed, 2 insertions, 0 deletions
diff --git a/java/test-profiles/default.testprofile b/java/test-profiles/default.testprofile
index 86a5b2efb3..63ad03f08b 100644
--- a/java/test-profiles/default.testprofile
+++ b/java/test-profiles/default.testprofile
@@ -16,6 +16,8 @@ root.logging.level=warn
log4j.configuration=file:///${test.profiles}/log4j-test.xml
log4j.debug=false
+# Note test-provider.properties also has variables of same name.
+# Keep in sync
test.port=15672
test.mport=18999
#Note : Management will start open second port on: mport + 100 : 19099