Problem Note 33535: Invalid cast exceptions and heap memory leaks might occur when running IOM servers in a multithreaded .NET environment
Applications that launch IOM servers in separate threads might see invalid cast exceptions during program execution. Incremental heap memory growth could also occur over the life of the application, even after thread termination.
The cast exception is seen when the client issues a workSpace.FileService.DeassignFileref(..) method call. An indication of this condition is the lack of ::Close() events in the related IOM server logs.
As threads and their associated IOM servers are terminated, some of their heap memory is not released. For short-lived applications this might not be apparent. For longer running applications such as services, the heap will grow incrementally and will not recover, even after garbage collection cycles.
Select the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| SAS System | SAS Integration Technologies | Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
| Windows Vista | 9.1 TS1M3 SP4 | 9.1 TS1M3 SP4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
| Type: | Problem Note |
| Priority: | medium |
| Date Modified: | 2009-01-28 10:33:05 |
| Date Created: | 2008-10-07 10:42:03 |
