On Oct 7, 2005, at 9:33 AM, Michael Peters wrote:
Michael Peters wrote:
So I'm looking for ideas for recovery from this (or ideas to fix it in
the first place). Should I wrapp all Java calls from perl in an eval
and
then try and reconnect if I get these kind of errors?
Since the list is silent I decided to try my approach and wrap every
Java call in an eval that checks for "Broken Pipe" messages and then
tries to reconnect if that occurs.
Is there a reason why you don't want to use JNI? Too much memory in
the process, perhaps? Otherwise that would be a good way to go, no
connection to worry about losing in the long-running process.
-Ken
