Sorry for failing to respond to this timely. We see these regularly. Though I believe it is less likely due to your code and more likely we are storing and overly large object, not setting a long enough timeout.
So as long as we can override the timeout or restructure into smaller objects we may be able to solve this. My programmer just did this today so we will see.
