Menu

#1 End of port range causes error

closed-fixed
None
5
2005-05-03
2005-05-02
Dan Nathan
No

When you get to the end port in the range the software
doesn't wrap back around, but instead just throws an
error. The code currently checks to see if a process ID
is still running, but uses the TCP port number instead.

Discussion

  • Gregory Warnes

    Gregory Warnes - 2005-05-03
    • assigned_to: nobody --> warnes
    • status: open --> closed-fixed
     
  • Gregory Warnes

    Gregory Warnes - 2005-05-03

    Logged In: YES
    user_id=9316

    Fixed using patch provided by Dan Nathan, in cvs as

    RSOAPManager.py
    revision 1.8
    date: 2005/04/30

     

Log in to post a comment.