Welcome Guest Search | Active Topics | Sign In | Register

Essential Objects Product Support Forum » All Products » Support » ThreadRunners must be destroyed before exit

ThreadRunners must be destroyed before exit Options
Previous Topic · Next Topic
ns
Posted: Monday, October 5, 2015 5:12:05 AM
Rank: Member
Groups: Member

Joined: 8/11/2015
Posts: 17
"Sometimes" we are getting the exception "ThreadRunner object must be explicitly destroyed before exiting the application or shutting down the AppDomain" after unloading an AppDomain that we have created.

We are not creating the ThreadRunner object(s) and we are calling EO.Base.Runtime.Shutdown() just before unloading the AppDomain.

Is there a way to wait for the runtime to shutdown to ensure that we would not get the aforementioned exception?

Note: We are unable to repro it in a consistent manner, nonetheless, it is customer visible.
Back to top
 
eo_support
Posted: Monday, October 5, 2015 8:36:16 AM
Rank: Administration
Groups: Administration

Joined: 5/27/2007
Posts: 24,082
Hi,

We can't think of any case where this can occur without creating ThreadRunner object. The exception is thrown from an instance method of the ThreadRunner object, so somewhere in your code you must have created one. You must destroy it before calling Runtime.Shutdown.

Thanks!
Back to top
 
ns
Posted: Monday, October 5, 2015 9:08:01 AM
Rank: Member
Groups: Member

Joined: 8/11/2015
Posts: 17
Thank you for the quick reply, we will try to reproduce this problem.
Back to top
 


You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.