Changeset 735

Timestamp:

07/05/08 14:18:49 (2 months ago)

Author:

francis

Message:

added a test case for a still-unresolved bug

Files:

• trunk/tests/test_basic.rb (modified) (1 diff)

trunk/tests/test_basic.rb

@@ -138 +138 @@
-  end
-
+
+  #------------------------------------
+  #
+  # TODO. This is an unfinished bug fix.
+  # This case was originally reported by Dan Aquino. If you throw a Ruby exception
+  # in a post_init handler, it gets rethrown as a confusing reactor exception.
+  # The problem is in eventmachine.rb, which calls post_init within the private
+  # initialize method of the EM::Connection class. This happens in both the EM::connect
+  # method and in the code that responds to connection-accepted events.
+  # What happens is that we instantiate the new connection object, which calls
+  # initialize, and then after initialize returns, we stick the new connection object
+  # into EM's @conns hashtable.
+  # But the problem is that Connection::initialize calls #post_init before it returns,
+  # and this may be user-written code that may throw an uncaught Ruby exception.
+  # If that happens, the reactor will abort, and it will then try to run down open
+  # connections. Because @conns never got a chance to properly reflect the new connection
+  # (because initialize never returned), we throw a ConnectionNotBound error
+  # (eventmachine.rb line 1080).
+  # When the bug is fixed, activate this test case.
+  #
+
+  class PostInitError < EM::Connection
+          def post_init
+                  aaa bbb # should produce a Ruby exception
+          end
+  end
+  def test_post_init_error
+          assert_raise( NameError ) {
+                  EM.run {
+                        EM::Timer.new(1) {EM.stop}
+                        EM.start_server TestHost, TestPort
+                        EM.connect TestHost, TestPort, PostInitError
+                  }
+          }
+  end
+
+
-end
-
-