×
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.
Ending the job would cause the operating system to automatically close
the connection (i.e. the equivalent of calling the close() API). Unless
the job is ended abnormally... or the Java client times out, but
doesn't actually close the connection (which means it'll eventually run
out of descriptor handles).
But I would expect the JVM to be smart enough to know when a socket can
never be used again, and automatically close it as part of it's garbage
collection routine.
Regardless of whether it's the Java program's fault or not, though, you
should ALWAYS code timeouts on the RPG side. Otherwise, anyone can
perform a denial-of-service attack on you simply by writing code that's
designed to make your program "get hung up".
Lim Hock-Chai wrote:
Could it also be cause by the java client ends the job, due to timeout,
without execute the close() api?
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.
midrange.com
