Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!feeder.erje.net!newsfeed.xs4all.nl!newsfeed5.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail Return-Path: X-Original-To: python-list@python.org Delivered-To: python-list@mail.python.org X-Spam-Status: OK 0.000 X-Spam-Evidence: '*H*': 1.00; '*S*': 0.00; 'parser': 0.05; 'subject:when': 0.07; 'python': 0.08; 'args,': 0.09; 'none)': 0.09; 'api': 0.09; 'configure': 0.10; 'error:': 0.10; 'server,': 0.12; 'converting': 0.15; 'method.': 0.15; 'skip:" 40': 0.15; 'to:name:python-list@python.org': 0.15; '(),': 0.16; '1.5.2': 0.16; '240,': 0.16; '__init__': 0.16; 'addr': 0.16; 'exe': 0.16; 'func(*args)': 0.16; 'hangs': 0.16; 'invoking': 0.16; 'received:216.32.181.186': 0.16; 'timeout': 0.16; 'windows?': 0.16; '{})': 0.16; 'subject:Windows': 0.18; 'occurred': 0.18; 'trace': 0.18; 'seems': 0.20; 'written': 0.20; '(most': 0.21; 'seconds': 0.21; 'dec': 0.22; 'header:In-Reply-To:1': 0.22; 'runs': 0.23; '(my': 0.24; 'traceback': 0.24; 'code': 0.25; 'architecture': 0.26; 'windows': 0.26; 'server.': 0.28; 'raise': 0.28; 'skip:" 30': 0.28; 'error': 0.29; 'server': 0.30; '-1,': 0.30; 'args)': 0.30; 'none,': 0.30; 'collecting': 0.31; 'skip:( 20': 0.31; 'there': 0.33; 'to:addr:python-list': 0.34; 'received:169': 0.34; 'received:169.254': 0.34; 'setting': 0.34; 'calling': 0.34; 'last):': 0.34; 'purely': 0.34; 'issue': 0.35; 'running': 0.35; 'something': 0.35; 'however,': 0.36; 'file': 0.36; 'header:Received:8': 0.36; 'charset:us-ascii': 0.37; 'run': 0.37; 'skip:_ 10': 0.37; 'using': 0.38; 'some': 0.38; 'called': 0.40; 'to:addr:python.org': 0.40; 'back': 0.62; 'order': 0.62; 'reply': 0.65; 'making': 0.67; 'encountered': 0.73; '__call__': 0.84; 'activex': 0.93 X-SpamScore: 6 X-BigFish: VS6(zzzz1202hzzz2dh2a8h668h839h8e2h8e3h944hbe9n) X-Forefront-Antispam-Report: CIP:70.37.183.190; KIP:(null); UIP:(null); IPV:NLI; H:mail.freescale.net; RD:none; EFVD:NLI X-FB-SS: 13, From: Wong Wah Meng-R32813 To: "python-list@python.org" Subject: Timeout when calling COM objects on Windows Thread-Topic: Timeout when calling COM objects on Windows Thread-Index: AQHMwWTkn1gFDccrmkWPlOp96Aom5w== Date: Fri, 23 Dec 2011 11:20:36 +0000 References: <18f78d0d-1e70-4c7b-9033-1422e6edb6db@t13g2000yqg.googlegroups.com> <10c62dac-2750-4f08-8962-21952c1c0a0b@v31g2000prg.googlegroups.com> <5a7a7aab-a320-4429-a130-ffcfcf0ac174@v24g2000prn.googlegroups.com> <4EF440A9.7030101@stoneleaf.us> <77861e74-c4fa-4f3f-8f28-853a1a319b1d@l16g2000prg.googlegroups.com> In-Reply-To: <77861e74-c4fa-4f3f-8f28-853a1a319b1d@l16g2000prg.googlegroups.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.228.70.137] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: freescale.com X-BeenThere: python-list@python.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: General discussion list for the Python programming language List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Newsgroups: comp.lang.python Message-ID: Lines: 66 NNTP-Posting-Host: 2001:888:2000:d::a6 X-Trace: 1324643782 news.xs4all.nl 6987 [2001:888:2000:d::a6]:58548 X-Complaints-To: abuse@xs4all.nl Xref: x330-a1.tempe.blueboxinc.net comp.lang.python:17798 Hello there, I am converting my VB ActiveX application written sometime back in year 200= 0 with python 1.5.2 to run in python 2.7.1.=20 My application is using RMI architecture and I am using a pythonOleRmi.py p= arser to exchange data/objects between the python and the VB exe.=20 I have no issue when my VB EXE is not running as a COM server while making = python API calls where my application server is written purely in python an= d runs on UNIX. However, when my VB EXE is running as a COM server, this co= de seems hangs when I make the python API same call to the application serv= er. Is there something that I need to change or configure in order to run t= his successfully? Or to make some security setting on my Windows? (My VB EX= E is run on Windows 7 now, will try out if the same issue is encountered on= XP next week).=20 Is the issue resided in the calling to the local daemon process (10.228.70.= 137:26000), or it is some security setting depicted in the policy.py file? Collecting Python Trace Output... Proxy called with: MatlMgr, getCompatibleFTCSVersions(), (), {} Dec 23 18:41:21 OleRmiClient Timeout of 300 seconds occurred on the inv= ocati on of ('getAppAddress', (u'MatlMgr',), {}) to ('10.228.70.137', 26000) pythoncom error: Python error invoking COM method. Traceback (most recent call last): File "C:\genesis\Enablers\Python\lib\site-packages\win32com\server\policy= .py", line 277, in _Invoke_ return self._invoke_(dispid, lcid, wFlags, args) File "C:\genesis\Enablers\Python\lib\site-packages\win32com\server\policy= .py", line 282, in _invoke_ return S_OK, -1, self._invokeex_(dispid, lcid, wFlags, args, None, None= ) File "C:\genesis\Enablers\Python\lib\site-packages\win32com\server\policy= .py", line 585, in _invokeex_ return func(*args) File "C:\genesis\Product\Lib\PythonOleRmi.py", line 240, in Proxy proxy =3D self._getProxyObj(pyserverString) File "C:\genesis\Product\Lib\PythonOleRmi.py", line 223, in _getProxyObj None, self._logWriter, rem_admin_addr =3D remAddr ) File "C:\genesis\Product\Lib\EComponent.py", line 710, in __init__ addr =3D self._getAppProxyAddress() File "C:\genesis\Product\Lib\EComponent.py", line 742, in _getAppProxyAdd= ress addr =3D remAdmin.getAppAddress(self.server_name) File "C:\genesis\Product\Lib\EComponent.py", line 611, in __call__ self._method, args, kw ) File "C:\genesis\Product\Lib\RMI.py", line 1779, in _genericInvocation reply =3D self._requestReply( replyBit, (method_name, args, kw) ) File "C:\genesis\Product\Lib\RMI.py", line 1585, in _requestReply reply =3D self._receive() File "C:\genesis\Product\Lib\RMI.py", line 1677, in _receive raise ServerReplyTimeout( self.reply_timeout) ServerReplyTimeout: 300 Regards, Wah Meng=20