× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. April 2002

Re: Word of advice: Dont' close a socket you didn't create.

"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 thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.