C
chris-s
Hi folks,
Whilst working on a 'background comms' option for our application which
runs in a separate thread, I am having a small problem with a
webservice that it uses. The actual data is transferred using RDA, but
part of the process uses a simple web service, the instance of which is
created, used and then set to null which is meant to destroy it.
When the comms process has completed it drops the connection, however,
a few moments later the GPRS connection is re-established by something.
After a process of elimination I have traced this down to the web
service, removing its inclusion resolves the issue. After some more
experimenting, if the web service object is created and then set to
null without making the actual call to the method, the problem also
never occurs.
I have checked and double-checked that no other obvious references are
being maintained which might prevent the object being disposed off,
even then, why would it re-make the connection without the method being
called?
So, what causes a webservice to re-establish a connection? Is there a
better way to 'kill-off' or dispose of a web service instance other
than setting it's instance to null? Bear in mind that the webservice is
being created and used within a separate thread, which other than this
issue appears to work 100% with no other problems.....yet!
Any tips welcome!
Chris
Whilst working on a 'background comms' option for our application which
runs in a separate thread, I am having a small problem with a
webservice that it uses. The actual data is transferred using RDA, but
part of the process uses a simple web service, the instance of which is
created, used and then set to null which is meant to destroy it.
When the comms process has completed it drops the connection, however,
a few moments later the GPRS connection is re-established by something.
After a process of elimination I have traced this down to the web
service, removing its inclusion resolves the issue. After some more
experimenting, if the web service object is created and then set to
null without making the actual call to the method, the problem also
never occurs.
I have checked and double-checked that no other obvious references are
being maintained which might prevent the object being disposed off,
even then, why would it re-make the connection without the method being
called?
So, what causes a webservice to re-establish a connection? Is there a
better way to 'kill-off' or dispose of a web service instance other
than setting it's instance to null? Bear in mind that the webservice is
being created and used within a separate thread, which other than this
issue appears to work 100% with no other problems.....yet!
Any tips welcome!
Chris