|
I have a series of jobs that run in batch and spawn a bunch of socket jobs. Basically, I used Scott Klement's sample socket programs and modified them to do what I needed. Everything works really well, except that after the second or third (I think) rendition of the socket listener spawning a new job the whole thing just kind of hangs as if the sockets are all used up. Now...using Scott's design, I spawn about 10 socket instances from the single socket listener and from there as each spawned job finishes, I terminate the program and the main socket listener spawns another socket, reusing that now closed socket port. And, as I say, it works fine for awhile, but at some point it all just hangs. To "fix" this, I end the socket jobs and restart them. Then everything works fine again for awhile, until, once again it hangs. I'm wondering if the sockets ports are really being freed up like I think they are or if something else is going on. Suggestions? Shannon O'Donnell
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.