What can one do about the following message that appears when running an
application from within the Visual Studio development environment (rather
than the build executable)? Is there a setting that would diminish the
likelihood of getting this message? In this case it occurs during the fetch
of 100,000 rows of data from an iSeries database table.
Thanks in advance,
Dean S
Message: The CLR has been unable to transition from COM context 0x18f340 to
COM context 0x18f490 for 60 seconds. The thread that owns the destination
context/apartment is most likely either doing a non pumping wait or
processing a very long running operation without pumping Windows messages.
This situation generally has a negative performance impact and may even lead
to the application becoming non responsive or memory usage accumulating
continually over time. To avoid this problem, all single threaded apartment
(STA) threads should use pumping wait primitives (such as
CoWaitForMultip leHandles) and routinely pump messages during long running
operations.
application from within the Visual Studio development environment (rather
than the build executable)? Is there a setting that would diminish the
likelihood of getting this message? In this case it occurs during the fetch
of 100,000 rows of data from an iSeries database table.
Thanks in advance,
Dean S
Message: The CLR has been unable to transition from COM context 0x18f340 to
COM context 0x18f490 for 60 seconds. The thread that owns the destination
context/apartment is most likely either doing a non pumping wait or
processing a very long running operation without pumping Windows messages.
This situation generally has a negative performance impact and may even lead
to the application becoming non responsive or memory usage accumulating
continually over time. To avoid this problem, all single threaded apartment
(STA) threads should use pumping wait primitives (such as
CoWaitForMultip leHandles) and routinely pump messages during long running
operations.