Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No free ports available #123

Open
rsandhu1 opened this issue Feb 6, 2014 · 1 comment
Open

No free ports available #123

rsandhu1 opened this issue Feb 6, 2014 · 1 comment

Comments

@rsandhu1
Copy link

rsandhu1 commented Feb 6, 2014

I am giving a port range in cog.properties like following. Looks like the code is never doing a reset of org.globus.net.PortRange.ports[]. Ports are actually available but this array is never reset and get "No free ports available".
tcp.port.range=4001,4005 #small range for testing

I can make the change to reset this and again call the getFreePort to restart the values. WDYT?
@rsandhu1
Copy link
Author

rsandhu1 commented Feb 6, 2014

ServerSocket close is not called. PrServerSocket and other socket has close functions have close and ports are set to UNUSED. I will take a look how to call this and close ServerSocket.

rsandhu1 added a commit to rsandhu1/JGlobus that referenced this issue Feb 10, 2014
@rsandhu1
To fix jglobus#123.
00ba022 
Socket was not getting closed in case of gram job and ports were not
reset for both gram and gridftp use.
rsandhu1 added a commit to rsandhu1/JGlobus that referenced this issue Feb 10, 2014
@rsandhu1
To fix jglobus#123 in v 2.0.6
2d1ee0e 
Socket was not getting closed in case of gram job and ports were not
reset for both gram and gridftp use.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rsandhu1