Hi, I don't recommmend handling the timeout on the Perl side. If the webservice you call from Java is not returning, it's best to handle the timeout on the Java side.
A timeout on the Perl side will just leave that Java thread blocked indefinitely ancd will cause the protocol between Perl and Java to become messed up and possibly unstable. Patrick On Mon, Apr 14, 2014 at 8:19 PM, Bill Moseley <mose...@hank.org> wrote: > > > > On Thu, Apr 10, 2014 at 9:07 PM, Bill Moseley <mose...@hank.org> wrote: > >> >> >> >> On Thu, Apr 10, 2014 at 8:52 PM, <sisyph...@optusnet.com.au> wrote: >> >>> >>> Looks like there's no-one currently around here to help you out. >>> Maybe try somewhere like perlmonks (http://www.perlmonks.org) if you're >>> still trying to find a solution. >>> >> >> Well, if there isn't a specific solution for Inline then I'll go the ALRM >> approach. >> > > I'm wondering how risky this is. Since it appears to be sitting on > read() I would need to use "unsafe" signal handling: > > http://search.cpan.org/~rgarcia/Perl-Unsafe-Signals-0.02/Signals.pm > > Years back I remember fighting segfaults in mod_perl when using ALRM to > interrupt external calls. > > Sure would be much cleaner if could use a select() timeout, but I'd need > help knowing where that would need to be implemented. > > > -- > Bill Moseley > mose...@hank.org > -- ===================== Patrick LeBoutillier Rosemère, Québec, Canada
