Web service causing Stack overflow exception - bug?

[Guest]

Hi

I'm running CF SP2 on Pocket PC 2003

I have written an app which passes various values via a webservice. For some reason after 6 calls to the webservice the next call to the service, causes the app to abort with a stack overflow.

During the previous 5 times (when it is working perfectly) the stack trace shows 19 calls (including CF calls). This is consistant everytime. When the exception occurs, the stack trace is empty. I assume that this is because the stack has overflowed

If I create the web service to run async, it aborts immediately. In fact it doesn't even give an error, it just terminates the app and completely locks up the Ipaq it is running on. The problem is 100% repeatable everytime

I notice that for the SoapHttpClientProtocol class, there isn't a dispose function on the compact framework; although there is one for the full .NET framework. Is this an omission by design or accident

Is anyone else experiencing similar problems, when trying to connect to something via a soap client

Many thank
Ia

 

[Lloyd Dupont]

I haven't used WebService
However I have encoutered StackOverflow a few times.

It's a very nasty bug.
Your app might died without providing any information or even false
information on where the bug hapened.

I strongly advice you to do a step by step excecution to see exactly where
the application throw this exception.
Don't believe VS.NET for this exception and you might be surprised by the
result ....

Hi,

I'm running CF SP2 on Pocket PC 2003.

I have written an app which passes various values via a webservice. For

some reason after 6 calls to the webservice the next call to the service,
causes the app to abort with a stack overflow.

During the previous 5 times (when it is working perfectly) the stack trace

shows 19 calls (including CF calls). This is consistant everytime. When
the exception occurs, the stack trace is empty. I assume that this is
because the stack has overflowed

If I create the web service to run async, it aborts immediately. In fact

it doesn't even give an error, it just terminates the app and completely
locks up the Ipaq it is running on. The problem is 100% repeatable
everytime.

I notice that for the SoapHttpClientProtocol class, there isn't a dispose

function on the compact framework; although there is one for the full .NET
framework. Is this an omission by design or accident?

 

[Valentin Iliescu]

Hi,

Do you recreate the webservice object every time you call
the webservice methods? Or do you create it once and call
only its methods afterward?

-----Original Message-----
Hi,

I'm running CF SP2 on Pocket PC 2003.

I have written an app which passes various values via a

webservice. For some reason after 6 calls to the
webservice the next call to the service, causes the app to
abort with a stack overflow.

During the previous 5 times (when it is working

perfectly) the stack trace shows 19 calls (including CF
calls). This is consistant everytime. When the
exception occurs, the stack trace is empty. I assume that
this is because the stack has overflowed

If I create the web service to run async, it aborts

immediately. In fact it doesn't even give an error, it
just terminates the app and completely locks up the Ipaq
it is running on. The problem is 100% repeatable
everytime.

I notice that for the SoapHttpClientProtocol class, there

isn't a dispose function on the compact framework;
although there is one for the full .NET framework. Is
this an omission by design or accident?

Is anyone else experiencing similar problems, when

trying to connect to something via a soap client?

 

[Guest]

Hi

I've have tried it both ways, and the result is identical. I'm kind of wondering if the CF is not cleaning up after itself. Which is why I was wondering about the absence of a dispose method

I have run it through the debugger, line by line. And every time on the 6th call to the webservice, the app just crashes, and locks up the Ipaq. Hey I thought that that kind of behaviour isn't possible with the CF :-

 

[Lloyd Dupont]

could you provide a sample reproducing the bug ?

Hi,

I've have tried it both ways, and the result is identical. I'm kind of

wondering if the CF is not cleaning up after itself. Which is why I was
wondering about the absence of a dispose method.

I have run it through the debugger, line by line. And every time on the

6th call to the webservice, the app just crashes, and locks up the Ipaq.
Hey I thought that that kind of behaviour isn't possible with the CF