Decrease number of messages to generate in test case.

- Lowering the NUM_MSG and sleep time.
  Checked with Naoki:
  intent of this test case was to run the scenario when MAX_MESSAGE_SEND is exceeded.
  MAX_MESSAGE_SEND is currently set to 100.

Change-Id: I1e470dee930a38e87f4b884620c34e1477747a41
diff --git a/src/test/java/net/onrc/onos/core/flowprogrammer/FlowPusherTest.java b/src/test/java/net/onrc/onos/core/flowprogrammer/FlowPusherTest.java
index f2cfb59..a8ef220 100644
--- a/src/test/java/net/onrc/onos/core/flowprogrammer/FlowPusherTest.java
+++ b/src/test/java/net/onrc/onos/core/flowprogrammer/FlowPusherTest.java
@@ -98,7 +98,8 @@
      */
     @Test
     public void testMassiveAddMessage() {
-        final int NUM_MSG = 10000;
+        // Some number larger than FlowPusher.MAX_MESSAGE_SEND
+        final int NUM_MSG = FlowPusher.MAX_MESSAGE_SEND * 2;
 
         beginInitMock();
 
@@ -135,7 +136,7 @@
 
         try {
             // wait until message is processed.
-            Thread.sleep(5000);
+            Thread.sleep(1000);
         } catch (InterruptedException e) {
             fail("Failed in Thread.sleep()");
         }