nchristy wrote:
Why is this occuring? Is it because I have multiple threads accessing the same session?
I would guess so. Do you really need multiple threads accessing the _same_ session? I can't think of a use case for it. What is the requirement?
Usually you get the data, and return, perhaps display or modify, and then flush and close. Each command goes to the database on its own, then closes the connection.
Please show us some more of your code, where the command is actually occurring. And how your session handling code wraps the command.