|
"Walden H. Leverich" <WaldenL@TechSoftInc.com> wrote in message FAD7A1A61D7EBF49B994F1A4BBDCD3044EEC6B@neptune.techsoftwareinc.com">news:FAD7A1A61D7EBF49B994F1A4BBDCD3044EEC6B@neptune.techsoftwareinc.com... > So do I understand this correctly? Your job that had absolutely nothing to > do with the remote command job caused the remote command job to fail by > closing a socket number that belonged to the remote command job? Is that > correct? No ... my job was being RUN inside the remote command job, using the remote command API (from a client side java program). Socket zero belonged to the remote command job ... my program closed it. My program ran to completion fine, but the remote command job couldn't send the necessary status updates to the remote system because the socket was closed. david
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.
midrange.com
