summaryrefslogtreecommitdiff
path: root/TAO/tests/Bug_3647_Regression/README
diff options
context:
space:
mode:
Diffstat (limited to 'TAO/tests/Bug_3647_Regression/README')
-rw-r--r--TAO/tests/Bug_3647_Regression/README32
1 files changed, 32 insertions, 0 deletions
diff --git a/TAO/tests/Bug_3647_Regression/README b/TAO/tests/Bug_3647_Regression/README
new file mode 100644
index 00000000000..13afa51b826
--- /dev/null
+++ b/TAO/tests/Bug_3647_Regression/README
@@ -0,0 +1,32 @@
+/**
+
+@page Bug_3647_Regression Test README File
+
+This test demonstrates the problem described in bugzilla entry #3647.
+
+In this test we have three participants:
+
+A) A back-end server that will inconveniently block in the middle of
+ its work
+B) A middle-tier server that is trying to communicate with the back
+ end server using SYNC_WITH_TRANSPORT oneway calls, with timeouts.
+C) A client application that is sending twoway calls to the
+ middle-tier server.
+
+The expectaton is that when the back-end server completely blocks, the
+middle-tier server will continue to operate normally. That is, the
+oneway calls to the back-end server will block it, the timeouts will
+expire, but the recursive loop will be available to respond to any
+incoming requests from the client application.
+
+What we observe is that the middle-tier application blocks, but not in
+the event loop as it should, but while checking if the socket is ready
+for output.
+
+To run the test use the run_test.pl script:
+
+$ ./run_test.pl
+
+the script returns 0 if the test was successful, non-zero otherwise.
+
+*/