IdentifyTask stops returning results until map service is restarted

[RichardBetts]

Hi everyone,

I have an Identify task running against a map service (server version 10) which happily returns results for a few hours and then stops doing so and returns an empty result each time.
Re-start the map service and everything is fine again for a couple of hours. 

No changes have been to the IdentifyParameters in the meantime. 

I've checked the results with Firebug etc and the results are definately empty for a request that would have previously returned some features.

Any ideas? Have I missed something?

Thanks very much

[RichardBetts]

Oh hang on....I've partly answered my own question. Shouldn't have been so quick to post!

I am editing the data in this service from within the same application. As soon as an edit is made, the IdentifyTask stops working until the map service is re-started.

Anyone know how best to deal with this?

(There is a reason I am using IdentifyTask to go back to the server for an answer rather than just accessing the data from the graphics in the featurelayer itself)

Cheers

[RichardBetts]

Another update in case anyone can help? I am now more clear about what the problem is.  

Identify against any of the layers this map service stops working after any edits are made to one of the (feature) layers in the service. The only way I can find to get identify returning results again is to restart the map service.

The data is in sde and non versioned. The edits are being successfully saved to the database.

I am using the Java version of server 10.

Thanks