Delta V Software Forums

Hi Jarl. Revisiting this issue after quite a while. One possible explanation for the behavior we were seeing is that it's another facet of the inability of RCF to have multiple outstanding requests on a connection. I'm not yet sure if that is the case, but it's a theory. Is there any update on that ...

My company has a product that uses RCF extensively for a client-server application. One oddity about how we use RCF is that there are three distinct RcfClients used for the client/server communication. This was done before my tenure and the justification was that one of the clients could have fairly...

Unfortunately I get the same error with HttpsEndpoint.

Thus far I've been unable to reproduce this in a test application. Still working on that...

I have confirmed that disabling the encryption filter avoids the problem. Not a viable option for production, but a very useful observation for debugging.

We are indeed using an OpenSSL encryption filter on the client connection.

I'll work on getting a standalone test app to send you.

More data. It appears that a single remote call is getting split into three distinct writes, each of which gets an index. The final index is what is included in the response. The next remote call then fails with an index mismatch: 19:31:53.607 - RCF/include/RCF/Future.hpp(245): [Thread: 13468][Time:...

I'm still investigating, but the first suspicious thing I see is simultaneous outstanding requests with an out-of-order response. It's after this that I get the exception. Request(1) Response(1) Request(2) Response(2) Request(3) Response(3) Request(4) Response(4) Request(5) Response(5) Request(6) Re...

Thanks for the reply, Jarl. Ultimately there will be an optional, configurable proxy between client & server (as well as choosing HTTP vs. HTTPS), but for this initial testing I'm limiting things to no proxy and HTTP only to get the simplest case working before adding complexity. I'll let you know w...

I'm attempting to modify an existing application of ours which has used RCF for years to add HTTP tunneling support. I'm presently getting the following exception: [159: HTTP tunnel error. HTTP session index mismatch on request. Expected index: 10 . Actual index: 12 .][0: No sub system.][0: ][What: ...