diff options
| author | Johnny Willemsen <jwillemsen@remedy.nl> | 2011-10-05 13:10:20 +0000 |
|---|---|---|
| committer | Johnny Willemsen <jwillemsen@remedy.nl> | 2011-10-05 13:10:20 +0000 |
| commit | e379a3b4cdbcebb94e73fd86b9cef36884f34604 (patch) | |
| tree | ca631b50a9d07d40b978d9006ea264db931b6052 /TAO/examples/CSD_Strategy/ThreadPool5 | |
| parent | 86ab3cbf7b5fd1863fcc7dde6e86a9a835e69a55 (diff) | |
| download | ATCD-e379a3b4cdbcebb94e73fd86b9cef36884f34604.tar.gz | |
Fuzz
Diffstat (limited to 'TAO/examples/CSD_Strategy/ThreadPool5')
| -rw-r--r-- | TAO/examples/CSD_Strategy/ThreadPool5/README | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/TAO/examples/CSD_Strategy/ThreadPool5/README b/TAO/examples/CSD_Strategy/ThreadPool5/README index 29b72f8a861..234c4fab331 100644 --- a/TAO/examples/CSD_Strategy/ThreadPool5/README +++ b/TAO/examples/CSD_Strategy/ThreadPool5/README @@ -1,8 +1,8 @@ -# $Id$ +$Id$ Description: -This test is a combination of other tests and has also added some +This test is a combination of other tests and has also added some other test cases such as cancel_servant. It uses the command line options for the number of orb threads, number of servants, collocated test options, etc. @@ -18,15 +18,15 @@ $ ./run_test.pl $ ./run_test.pl collocated - This runs the collocated test. + This runs the collocated test. - The server application creates one servant, runs one orb - thread, runs two custom dispatching threads and one client + The server application creates one servant, runs one orb + thread, runs two custom dispatching threads and one client thread to invoke the operations. - Running two custom dispatching threads instead of one is + Running two custom dispatching threads instead of one is required to avoid deadlock. - + $ ./run_test.pl multiple_servants This test is similar to the "ThreadPool2" test. @@ -41,7 +41,7 @@ $ ./run_test.pl cancel_servant cancelled when a servant is deactivated. The client invokes multiple two-way operations and catches the - OBJECT_NOT_EXIST or NO_IMPLEMENTATION exception after the servant + OBJECT_NOT_EXIST or NO_IMPLEMENTATION exception after the servant is deactivated - this is what it is supposed to do - the exceptions are expected. |