What are the proper steps to take when destroying a class that derives from SocketPort and Thread and is attached to a SocketService pool? I think that I have an issue where an existing session object is being reused by subsequent requests that occur immediately afterward. The behavior is that the pending() method of my derived class is never called, similar to the problems seen when you attach a derived SocketPort to the SocketService pool in the derived constructor and pending() is called before the constructor finishes. This results in the base-class pending() being called. By introducing a miniscule delay between making the two socket requests from the client, the problem goes away. Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What are the proper steps to take when destroying a class that derives from SocketPort and Thread and is attached to a SocketService pool? I think that I have an issue where an existing session object is being reused by subsequent requests that occur immediately afterward. The behavior is that the pending() method of my derived class is never called, similar to the problems seen when you attach a derived SocketPort to the SocketService pool in the derived constructor and pending() is called before the constructor finishes. This results in the base-class pending() being called. By introducing a miniscule delay between making the two socket requests from the client, the problem goes away. Any ideas?