1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 <2016> 2017 2018 2019 2020 2021 2022 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Issue with PvaClientRPC |
From: | <[email protected]> |
To: | <[email protected]> |
Date: | Fri, 25 Nov 2016 11:23:15 +0000 |
Hello, I have an issue with PvaClientRPC in Java. It may be that I’m not using it correctly, or it may be a bug/desired behaviour. I send an RPC request in the following way: PvaClientChannel pvaChannel = pvaClient.createChannel(“mydevice”,"pva"); pvaChannel.issueConnect(); status = pvaChannel.waitConnect(3); [ …check status is ok… ] PvaClientRPC rpc = pvaChannel.createRPC(myMethodStructure); rpc.issueConnect(); status = rpc.waitConnect(); [ …check status is ok… ] pvResult = rpc.request(myParametersStructure); The timeout is set to 0 (wait until completes). This all works fine is normal operations. The problem occurs if the rpc ‘server’ that I am connecting to crashes while dealing with that request. If it does, the call to PvaClientRPC.request() continues blocking. There is some output in
the console: [MainThread]error mydevice mydevice connection state DISCONNECTED So it ‘knows’ that the device has been disconnected, but it doesn’t throw any exception up to the caller or return, so it continues to wait forever. Is this expected? Is there a way I can work around it? Thanks for your assistance, Matt
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |