[Progress Communities] [Progress OpenEdge ABL] Forum Post: Calling a webservice method on port in CLOSE_WAIT establishes a new connection

  • Thread starter Thread starter jquerijero
  • Start date Start date
Status
Not open for further replies.
J

jquerijero

Guest
I noticed that when a webservice port switches to CLOSE_WAIT because of inactivity then later on you try to call another webservice method, the act of calling a method establishes a new connection and thus a new port number. This leaves the original port in CLOSE_WAIT status. Is this an expected behavior of port, or is this a Progress implementation? The problem is that the port in CLOSE_WAIT status lingers on and never freed up until the application is closed. Or better yet, is there a way to check for the port status before I make my method call?

Continue reading...
 
Status
Not open for further replies.
Back
Top