Victor St Clair wrote:
Hello Jason
For us, this usually happens when you close a session that's not open.
Typically this happens because an I/O step fails in a way that causes
the session to close. I think, but I'm not sure, that in some cases
UniObjects does not throw an error. Or, it could be that we're catching
the error and not re-throwing it if it's an unexpected condition.
I think there is a property on the session you can test, I believe it's
.IsActive.
(I'm answering this from home, so I'm going from memory.)
But in any case, find the code where this error is being thrown, and
check to see if the session object is still valid when it tries to close
Hope this helps
Victor St. Clair
Victor,
Thanks for the suggestion.
As mentioned by Brian in a separate message, my problem was the lack of
a explicit session close call.
I probably do a "close all sessions" call just to be safe.
Jason
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
