omniORB 4.0.5 bugs

The following bugs in omniORB 4.0.5 have been fixed. Update from CVS to get the fixes.


Summary:	Race conditions in connection disconnection (bug number 1)
Date:	Mon Dec 20 18:06:02 GMT 2004

Summary:	Segfault in omniCurrent::get (bug number 2)
Date:	Tue Jan 4 14:47:42 GMT 2005
Description:	omniCurrent::get would segfault if called before the ORB is initialised.

Summary:	Requests missed after skipping one. (bug number 3)
Date:	Tue Jan 4 18:05:35 GMT 2005
Description:	If multiple requests were received in a single buffer, and one of them was skipped (because the object did not exist, for example), subsequence requests would be ignored.

Summary:	Memory leaks with CloseConnection messages (bug number 4)
Date:	Wed Feb 2 00:20:01 GMT 2005
Description:	Some CloseConnection messages and other connection closures could result in memory leaks.

Summary:	Fixed point bugs (bug number 5)
Date:	Thu Mar 3 12:44:46 GMT 2005
Reported by:	Simone Viani
Description:	A number of bugs in multiplication and truncation of fixed point values.

Summary:	Server side connection shutdown (bug number 6)
Date:	Wed Mar 16 09:15:35 GMT 2005
Reported by:	Dirk Siebnich
Description:	A problem introduced by a previous bug-fix meant that servers would never close idle connections.

Summary:	Connection management problems (bug number 7)
Date:	Sun Apr 10 23:16:04 BST 2005
Reported by:	Jon Biggar
Description:	A number of connection management situations were not handled well.
Link for this bug:	http://www.omniorb-support.com/pipermail/omniorb-dev/2005-April/000177.html

Summary:	Could not create an alias TypeCode to an incomplete type (bug number 8)
Date:	Sun Apr 10 23:36:27 BST 2005
Reported by:	Renzo Tomaselli