RE: Simultaneous Channel access

[<matthew.taylor@diamond.ac.uk>]

Hi Marty,

 

I tried that and the TestSimultaneous test does pass, but only because it waits until the RPC call has finished, before doing the GET. I had implemented PvaClientRPCRequesterImpl to ensure that the GET was called whilst the RPC was still being processed by the Server.

 

I’ve done some debugging in the Epics jars today, and have maybe seen what’s happening:

 

The server seems to be processing requests using the ‘BlockingTCPAcceptor.java’ class, and several other class with ‘Blocking’ in the name. In one of them, it has the comment:

 

// NOTE: supports 2 threads per connection (receive and send)

 

I’ve put some debugging in the client and the server, and as far as I can see, the client is sending the request to connect, but the server doesn’t respond/get it.

 

It also seems that the client is reusing an existing ‘Transport’ object, and so isn’t creating a new connecting to the server, but reusing an existing one. I’m assuming now that the server can’t receive any new connections on this existing connection as it is Blocking, and is currently dealing with a request.

 

My question then is, (given that I don’t have much control over the server), how can I force the client to create a new Transport and connection each time, regardless of whether there is an existing connection or not in the Context?

 

Basically, my key requirement is to be able to connect to the same server from the same client (to perform an RPC call or a GET), whilst the server is already processing an RPC call from the client.

 

Thanks again,

 

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.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom