diff options
| author | bala <balanatarajan@users.noreply.github.com> | 2001-08-08 17:27:09 +0000 |
|---|---|---|
| committer | bala <balanatarajan@users.noreply.github.com> | 2001-08-08 17:27:09 +0000 |
| commit | 06057720524ebac554a0553115f1715e70d221fb (patch) | |
| tree | b2ac0c8c8db307a3a855c5c904a62271679f5d7f | |
| parent | e1bb15e8df7e50f8bc11afca2813b3e4b0971658 (diff) | |
| download | ATCD-06057720524ebac554a0553115f1715e70d221fb.tar.gz | |
ChangeLogTag: Wed Aug 8 12:16:22 2001 Balachandran Natarajan <bala@cs.wustl.edu>
| -rw-r--r-- | TAO/ChangeLogs/ChangeLog-02a | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/TAO/ChangeLogs/ChangeLog-02a b/TAO/ChangeLogs/ChangeLog-02a index e3ec3ae29f3..360b2145d08 100644 --- a/TAO/ChangeLogs/ChangeLog-02a +++ b/TAO/ChangeLogs/ChangeLog-02a @@ -2,20 +2,20 @@ Wed Aug 8 12:16:22 2001 Balachandran Natarajan <bala@cs.wustl.edu> * performance-tests/Thread_Per_Connection_Latency/svc.conf: * performance-tests/Thread_Pool_Latency/svc.conf: Made the client - to use Wait On Read Write as we see a big performance drop if we - use the LF. To make the test work without any problems, we now - use the exclusive transport mux strategy. Hopefully this will - get our performance back to normal. + to use Wait_On_Read_Write as we see a big performance drop if we + use the Wait_On_LF. To make the test work without any problems, + we now use the exclusive transport mux strategy. Hopefully this + will get our performance back to normal. * tao/Muxed_TMS.cpp: Fixed a subtle problem in connection_closed (). While iterating through the reply_disptacher table to close the reply dispatchers, a wrong comparision was made in the for loop. This would not allow any of the reply dispatchers to be closed and in turn prevent the transport cleaning up the - resources. This would lead to the client hanging on select () - even after the connection is closed by the server. I am - surprised that this has not been found out so far. God save - people who have been using the Muxed strategy :-). + resources. This lead to the client hanging on select () even + after the connection is closed by the server. I am surprised + that this has not been found out so far. God save people who + have been using the Muxed strategy :-). BTW, the above fix should fix problems seen in the Faults and Crashed_Callback tests in the daily builds. |