We have a custom-built JRA application connecting to our repository that has recently been leaving invalid sessions connected to the repository intermittently. I was hoping someone may be able to help clarify a few of the odd aspects of this problem (and perhaps help track down where the problem may be in our code).

1. Our system is a classic license, with both full and retrieval users. The program connects using a dedicated username/password retrieval user license. When the errors have stacked up enough that all of the retrieval licenses are used up by these invalid sessions, the program begins to consume the full licenses as well. Is there a way to prevent a retrieval login from using a full license?
2. Our repository has a login timeout for 1hr of inactivity. The JRA application login seems to be exempt from that, as the invalid sessions show inactivity times of days. Is that normal behavior?
3. At times it is possible that there have been 2 instances of the application running on the same workstation. Would these problems be caused by an interaction between the two instances trying to login to the same user account?

I realize there may be a problem in the code somewhere, and I can't really publish that here. Any insight into the way connections work with the JRA toolkit that may be helpful would be very much appreciated.

Thank You!