[jboss-cvs] JBossRemoting/src/tests/org/jboss/test/remoting/timeout ...

[Ron Sigal]

  User: rsigal  
  Date: 07/02/22 16:32:08

  Modified:    src/tests/org/jboss/test/remoting/timeout  Tag: remoting_2_x
                        QuickDisconnectClientParent.java
  Log:
  JBREM-657, JBREM-701:  Disabled testSlowDisconnect() and testSlowRemoveListener().
  
  Revision  Changes    Path
  No                   revision
  
  
  No                   revision
  
  
  1.1.2.3   +24 -8     JBossRemoting/src/tests/org/jboss/test/remoting/timeout/Attic/QuickDisconnectClientParent.java
  
  (In the diff below, changes in quantity of whitespace are not shown.)
  
  Index: QuickDisconnectClientParent.java
  ===================================================================
  RCS file: /cvsroot/jboss/JBossRemoting/src/tests/org/jboss/test/remoting/timeout/Attic/QuickDisconnectClientParent.java,v
  retrieving revision 1.1.2.2
  retrieving revision 1.1.2.3
  diff -u -b -r1.1.2.2 -r1.1.2.3
  --- QuickDisconnectClientParent.java	22 Feb 2007 09:41:50 -0000	1.1.2.2
  +++ QuickDisconnectClientParent.java	22 Feb 2007 21:32:08 -0000	1.1.2.3
  @@ -53,7 +53,7 @@
    * removeListener().
    * 
    * @author <a href="ron.sigal at jboss.com">Ron Sigal</a>
  - * @version $Revision: 1.1.2.2 $
  + * @version $Revision: 1.1.2.3 $
    * <p>
    * Copyright Jan 24, 2007
    * </p>
  @@ -181,8 +181,16 @@
       * disconnectTimeout value is not set on the client.  Therefore, the client
       * will not be able to disconnect as quickly as it does in
       * testQuickDisconnectTimeout().
  +    * 
  +    * This test fails in linux - apparently the connection gets feedback from a
  +    * failed i/o operation more quickly, and the call to Client.disconnect() is
  +    * able to conclude.
  +    * 
  +    * Therefore, the test has been disabled.  That's OK, since it doesn't verify
  +    * any functionality.  It was intended only to verify the design of
  +    * testQuickDisconnect(), and it passes in Windows.
       */
  -   public void testSlowDisconnect() throws Throwable
  +   public void xtestSlowDisconnect() throws Throwable
      {
         log.info("entering " + getName());
         String host = InetAddress.getLocalHost().getHostAddress();
  @@ -259,7 +267,7 @@
      /**
       * This test starts a server, connects a client to it, disables the server,
       * and sets the client's disconnectTimeout to 1 second.  The client should be
  -    * able to terminate the lease and disconnect quickly even though it cannot
  +    * able to remove the callback handler quickly even though it cannot
       * complete an invocation on the server.
       */
      public void testQuickRemoveListener() throws Throwable
  @@ -350,12 +358,20 @@
   
      
      /**
  -    * This test starts a server, connects a client to it, disables the server,
  -    * and sets the client's disconnectTimeout to 1 second.  The client should be
  -    * able to terminate the lease and disconnect quickly even though it cannot
  -    * complete an invocation on the server.
  +    * This test is identical to testQuickRemoveListener() except that the
  +    * disconnectTimeout value is not set on the client.  Therefore, the client
  +    * will not be able to remove the callback handler as quickly as it does in
  +    * testQuickRemoveListener().
  +    * 
  +    * This test fails in linux - apparently the connection gets feedback from a
  +    * failed i/o operation more quickly, and the call to Client.removeListener()
  +    * is able to conclude.
  +    * 
  +    * Therefore, the test has been disabled.  That's OK, since it doesn't verify
  +    * any functionality.  It was intended only to verify the design of
  +    * testQuickRemoveListener(), and it passes in Windows.
       */
  -   public void testSlowRemoveListener() throws Throwable
  +   public void xtestSlowRemoveListener() throws Throwable
      {
         log.info("entering " + getName());
         String host = InetAddress.getLocalHost().getHostAddress();