[vwnc] "Interrupted" error invoking COM methods

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[vwnc] "Interrupted" error invoking COM methods

Boris Popov, DeepCove Labs (SNN)

I’ve run into a case today where invoking a method on a COMDispatchDriver caused “Exception occurred. ( HRESULT 16r80020009 ) Interrupted.”. After a bit of poking and prodding adding a small delay (anything over 10 microseconds) after calls to #setProperty:value and just prior to  #invokeMethod: seems to have solved this specific issue, which brings me here in case someone has a rational explanation for what might be happening and what to do to _properly_ address this?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

[hidden email]

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] "Interrupted" error invoking COM methods

Boris Popov, DeepCove Labs (SNN)

I’d raised this issue a while back and would like to follow up in case someone might have an idea about this one…

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Popov
Sent: Wednesday, August 26, 2009 12:22 PM
To: [hidden email]
Subject: [vwnc] "Interrupted" error invoking COM methods

 

I’ve run into a case today where invoking a method on a COMDispatchDriver caused “Exception occurred. ( HRESULT 16r80020009 ) Interrupted.”. After a bit of poking and prodding adding a small delay (anything over 10 microseconds) after calls to #setProperty:value and just prior to  #invokeMethod: seems to have solved this specific issue, which brings me here in case someone has a rational explanation for what might be happening and what to do to _properly_ address this?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

[hidden email]

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] "Interrupted" error invoking COM methods

Boris Popov, DeepCove Labs (SNN)

Hmm… A little more digging on MSDN and through the COM session manager suggests that disabling free threading might do the trick,

 

COMSessionManager

 isCOMAvailable: nil;

 isDCOMEnabled: nil;

 isFreeThreadingAvailable: false

 

Quick tests appear to support this theory, but I’m wondering if I should be expecting some other negative side effects from this? Any way to set this per-COMDispatchDriver instead of on the session manager?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Popov
Sent: Tuesday, September 29, 2009 2:53 PM
To: [hidden email]
Subject: Re: [vwnc] "Interrupted" error invoking COM methods

 

I’d raised this issue a while back and would like to follow up in case someone might have an idea about this one…

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Popov
Sent: Wednesday, August 26, 2009 12:22 PM
To: [hidden email]
Subject: [vwnc] "Interrupted" error invoking COM methods

 

I’ve run into a case today where invoking a method on a COMDispatchDriver caused “Exception occurred. ( HRESULT 16r80020009 ) Interrupted.”. After a bit of poking and prodding adding a small delay (anything over 10 microseconds) after calls to #setProperty:value and just prior to  #invokeMethod: seems to have solved this specific issue, which brings me here in case someone has a rational explanation for what might be happening and what to do to _properly_ address this?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

[hidden email]

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: [vwnc] "Interrupted" error invoking COM methods

Alexander Augustin

Hello,

 

I had a look into WINERROR.H and found that DISP_E_EXCEPTION is defined as 0x80020009L,
a general exception error. In your case the server component seems to provided the information
that some kind of interrupt has appeared. It is probably not possible to say more without knowing
the server software you use.

 

I also had a look into the settings you described in VisualWorks.  
IsCOMAvailable only modifies VisualWorks Server behaviour.

 

The other two flags may influence the context in which an object is created.
Normally COMDispatchDrivers pass CLSCTX_SERVER as context parameter to the instance creation method.

Normally in this case CLSCTX_REMOTE_SERVER flag will added automatically. If one of the settings is set to false
this will not happen (please see COMExternalInterface class>>asClassContextParameter:)

 

If the problem is caused by the the added CLSCTX_REMOTE_SERVER flag
there currently is no way to bypass this except by setting isDCOMEnabled
or isFreeThreadingAvailable to false.

 

You may nevertheless try to experiment with classcontext seetings by using

COMDispatchDriver class>createObject:context: instead of #createObject:.

But please be aware that the previously mentioned settings will still influence the
context parameter.

 

I hope this will help a little.

 

Best regards,

Alexander Augustin

Alexander Augustin (Dipl.-Informatiker),
Email:
[hidden email] ,
Tel: +49-3496-214329, Fax: +49-3496-214712
Georg Heeg eK, Köthen
Handelsregister: Amtsgericht Dortmund A 12812


Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Boris Popov
Gesendet: Mittwoch, 30. September 2009 00:11
An: [hidden email]
Betreff: Re: [vwnc] "Interrupted" error invoking COM methods

 

Hmm… A little more digging on MSDN and through the COM session manager suggests that disabling free threading might do the trick,

 

COMSessionManager

 isCOMAvailable: nil;

 isDCOMEnabled: nil;

 isFreeThreadingAvailable: false

 

Quick tests appear to support this theory, but I’m wondering if I should be expecting some other negative side effects from this? Any way to set this per-COMDispatchDriver instead of on the session manager?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Popov
Sent: Tuesday, September 29, 2009 2:53 PM
To: [hidden email]
Subject: Re: [vwnc] "Interrupted" error invoking COM methods

 

I’d raised this issue a while back and would like to follow up in case someone might have an idea about this one…

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Boris Popov
Sent: Wednesday, August 26, 2009 12:22 PM
To: [hidden email]
Subject: [vwnc] "Interrupted" error invoking COM methods

 

I’ve run into a case today where invoking a method on a COMDispatchDriver caused “Exception occurred. ( HRESULT 16r80020009 ) Interrupted.”. After a bit of poking and prodding adding a small delay (anything over 10 microseconds) after calls to #setProperty:value and just prior to  #invokeMethod: seems to have solved this specific issue, which brings me here in case someone has a rational explanation for what might be happening and what to do to _properly_ address this?

 

Regards,

 

-Boris

 

--

+1.604.689.0322

DeepCove Labs Ltd.

4th floor 595 Howe Street

Vancouver, Canada V6C 2T5

http://tinyurl.com/r7uw4

 

[hidden email]

 

CONFIDENTIALITY NOTICE

 

This email is intended only for the persons named in the message header. Unless otherwise indicated, it contains information that is private and confidential. If you have received it in error, please notify the sender and delete the entire message including any attachments.

 

Thank you.

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc