Revert (inadvertent?) changes to frame-max tests.

Author: Simon MacMullen

test/src/com/rabbitmq/client/test/functional/FrameMax.java

@@ -34,7 +34,6 @@
 import com.rabbitmq.client.impl.FrameHandler;
 import com.rabbitmq.client.impl.LongStringHelper;
 import com.rabbitmq.client.impl.SocketFrameHandler;
-import com.rabbitmq.tools.Host;
 
 public class FrameMax extends BrokerTestCase {
     /* This value for FrameMax is larger than the minimum and less
@@ -74,15 +73,12 @@ public void testFrameSizes()
     public void testRejectLargeFramesDuringConnectionNegotiation()
         throws IOException
     {
-        Host.rabbitmqctl("eval 'application:set_env(rabbit, frame_max, " + Integer.toString(AMQP.FRAME_MIN_SIZE) + ").'");
         ConnectionFactory cf = new ConnectionFactory();
         cf.getClientProperties().put("too_long", LongStringHelper.asLongString(new byte[AMQP.FRAME_MIN_SIZE]));
         try {
             cf.newConnection();
             fail("Expected exception during connection negotiation");
         } catch (IOException e) {
-        } finally {
-            Host.rabbitmqctl("eval 'application:set_env(rabbit, frame_max, 131072).'");
         }
     }
 
@@ -93,7 +89,6 @@ public void testRejectExceedingFrameMax()
     {
         closeChannel();
         closeConnection();
-
         ConnectionFactory cf = new GenerousConnectionFactory();
         connection = cf.newConnection();
         openChannel();