Article View: borland.public.cppbuilder.webservices.soap
Article #103Re: Problem with using MSSOAP
From: Dean Mitchell
Date: Mon, 19 Jul 2004 01:29
Date: Mon, 19 Jul 2004 01:29
64 lines
3199 bytes
3199 bytes
Thanks for the idea of switching to raw interfaces, It was the reference counting as it worked when I went to raw interfaces, and it was the line that made you uncomfortable. What the problem was it wasn't actually returning an IStream but ISequentialStream instead, so when I changed IStreamPtr to be ISequentialStreamPtr it worked. Thanks again Dean "Jean-Marie Babet" <bbabet@borland.com> wrote in message news:40f562f4$1@newsgroups.borland.com... > Hello Dean, > > I have not used MSSOAP for a very long time (it was actually not known as > MSSOAP yet when I last I used it). > > If you suspect a COM issue, I would suggest dropping the InterfacePtr > wrappers and going directly for the interface with explicit Release calls - > there are just 4 of them in the sample posted. Also, along the same COM > issue suspicion, do the interfaces have to be initialized/destroyed > LIFO-wise? Currently the order of destruction will go in reverse order of > declaration, not reverse order of initialization. I suspect this does not > matter but....? Explicit 'Release' calls will also allow better control in > this issue. > > I doubt this matters but the following line makes me a little uncomfortable > since the underlying interface wrapper exposes a conversion operator to the > its interface type but not to IUnknown*: > > > OleCheck(Serializer->Init(TVariant((IUnknown*)Stream))); > > So I would prefer > > > OleCheck(Serializer->Init(TVariant((IUnknown*)(IStream*)Stream))); > > > > I believe that this is caused by the fact that after the request has been > > sent and the reponse recieved the control is still connected to the HTTP > > server. So I end up with an ever growing number of connections until the > > program is shutdown. so this is the real problem. > > You're assessment is probably correct but in case you're interested, if you > have something like proxyTrace (http://www.pocketsoap.com/tcptrace/pt.aspx), > it might be useful as it will allow you to confirm that indeed the HTTP > connections are still open. > > Regards, > > > Bruneau. > >
Technical Details
Message-ID:
<40fb23e1@newsgroups.borland.com>Path:
arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!news-out.ntli.net!newsrout1.ntli.net!news-in.ntli.net!ntli.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mailReferences:
<40f4bebd$1@newsgroups.borland.com> <40f562f4$1@newsgroups.borland.com>Show Full Headers
Complete Article Headers
X-Google-Thread: 11096a,3cec10b879f4b20d X-Google-Attributes: gid11096a,public X-Google-Language: ENGLISH,ASCII-7-bit From: "Dean Mitchell" <not@this.address> Newsgroups: borland.public.cppbuilder.webservices.soap References: <40f4bebd$1@newsgroups.borland.com> <40f562f4$1@newsgroups.borland.com> Subject: Re: Problem with using MSSOAP Date: Mon, 19 Jul 2004 13:29:34 +1200 Lines: 66 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1409 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 NNTP-Posting-Host: 210.54.152.164 Message-ID: <40fb23e1@newsgroups.borland.com> X-Trace: newsgroups.borland.com 1090200545 210.54.152.164 (18 Jul 2004 18:29:05 -0700) Path: arc1-ca.pugleaf.net!g2news1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.freenet.de!216.196.110.149.MISMATCH!border2.nntp.ams.giganews.com!nntp.giganews.com!news-out.ntli.net!newsrout1.ntli.net!news-in.ntli.net!ntli.net!newsfeed01.sul.t-online.de!t-online.de!newsgroups.borland.com!not-for-mail