From df99d3f87a61157f685396a14aad55ece1e7a134 Mon Sep 17 00:00:00 2001
From: lutoff <lutoff@localhost>
Date: Tue, 10 Jul 2007 14:51:33 +0000
Subject: [PATCH] fix for issue #1881 : Jmx Unit Test doesn't handled correctly JMX connection exception We now catch expected exception in the test
---
opends/tests/unit-tests-testng/src/server/org/opends/server/protocols/jmx/postConnectedDisconnectTest.java | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/opends/tests/unit-tests-testng/src/server/org/opends/server/protocols/jmx/postConnectedDisconnectTest.java b/opends/tests/unit-tests-testng/src/server/org/opends/server/protocols/jmx/postConnectedDisconnectTest.java
index 65a75c4..04363eb 100644
--- a/opends/tests/unit-tests-testng/src/server/org/opends/server/protocols/jmx/postConnectedDisconnectTest.java
+++ b/opends/tests/unit-tests-testng/src/server/org/opends/server/protocols/jmx/postConnectedDisconnectTest.java
@@ -26,6 +26,7 @@
*/
package org.opends.server.protocols.jmx;
+import java.io.IOException;
import java.util.HashMap;
import org.opends.server.TestCaseUtils;
@@ -58,8 +59,15 @@
env.put("jmx.remote.x.client.connection.check.period",0);
OpendsJmxConnector opendsConnector = new OpendsJmxConnector("localhost",
TestCaseUtils.getServerJmxPort(), env);
- opendsConnector.connect();
assertNotNull(opendsConnector);
+ try
+ {
+ opendsConnector.connect();
+ }
+ catch (IOException e)
+ {
+ assertTrue(false, "JMX connection error: " + e.getMessage());
+ }
// Check that number of postconnect has been incremented.
// Don't wait more than 5 seconds
--
Gitblit v1.10.0