Known Issues for Relay Server

Read about updates, corrections, and clarifications to the documentation released with Sybase Unwired Platform Runtime.

Issue # Description

Issue #	Description
SMPONP-3934	Requests fail with error `400 bad request with session error reported by RSOE` This error typically happens after Relay Server has been restarted. Relay server maintains client socket and back-end server socket affinity using a section named `ias-rs-sessionid`, which is provided by the client application. With this mechanism, a stateful request can be transferred to the original back-end server, even from a different relay server in the relay server farm. After restarting the relay server, the socket and session affinity that originated from this relay server are both cleared, and the back-end server socket connection is dropped. The Outbound Enabler responds with a 400 error when it receives a request that is still using the previous `ias-rs-sessionid` value. Moreover, for a stateless request that does not provide `the ias-rs-sessionid`, relay server transfers the request to any back-end server in the targeted farm according to the load balancing algorithm. Workaround: In the relay server configuration file, create a property named `renew_overlapped_cookie` in the `backend_farm` configuration section. Set the `renew_overlapped_cookie` default value to yes. In the future, Outbound Enabler will create new connections instead of responding with a 400 error.
RTC-46	When an HTTP client connects through Relay Server to Unwired Platform to get a proxy connection, the URL rewrite in the response is missing the Relay Server prefix information. Workaround: None.

SMPONP-3934

Requests fail with error 400 bad request with session error reported by RSOE

This error typically happens after Relay Server has been restarted. Relay server maintains client socket and back-end server socket affinity using a section named ias-rs-sessionid, which is provided by the client application. With this mechanism, a stateful request can be transferred to the original back-end server, even from a different relay server in the relay server farm. After restarting the relay server, the socket and session affinity that originated from this relay server are both cleared, and the back-end server socket connection is dropped. The Outbound Enabler responds with a 400 error when it receives a request that is still using the previous ias-rs-sessionid value. Moreover, for a stateless request that does not provide the ias-rs-sessionid, relay server transfers the request to any back-end server in the targeted farm according to the load balancing algorithm.

Workaround:

In the relay server configuration file, create a property named renew_overlapped_cookie in the backend_farm configuration section.
Set the renew_overlapped_cookie default value to yes. In the future, Outbound Enabler will create new connections instead of responding with a 400 error.

RTC-46

When an HTTP client connects through Relay Server to Unwired Platform to get a proxy connection, the URL rewrite in the response is missing the Relay Server prefix information.

Workaround: None.