Known Issues for Relay Server and Load Balancer

Learn about known issues and apply workarounds for Relay Server and Load Balancer.

Issue #	Description
SMPONP-15348	A RSOE service using HTTPS cannot start because duplicate certificates are imported into the keystore. Importing duplicate certificates into the keystore prevents the RSOE service from starting. Workaround: Delete the duplicate certificate from the keystore (only leave one item), then restart the RSOE service.
SMPONP-15011	SAP Mobile Platform version 2.3 SP04 does not include the quicksetup_apache folder as did previous releases. Workaround: For Relay Server installation and configuration instructions on Apache, see Landscape Design and Integration > Stage 3: Implement > Adding Relay Servers or Reverse Proxies > Installing Relay Server for Production Environments > Installing a Relay Server, and either: Installing Relay Server on Apache RedHat Enterprise or, Installing Relay Server on Apache SUSE Enterprise
SMPONP-14716	Apache Load balancer is not retaining original request URL from the OData client. The Apache Load Balancer modifies the URL to whichever node to which it is forwarding, if ProxyPreserveHost off , which is the default. Workaround: If you use Apache as a Reverse Proxy or Load Balancer, set ProxyPreserveHost on so the ODP component inside SAP Mobile Server can retrieve the original request URL and add a cookie for it. See ProxyPreserveHost Documentation
RTC-340	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 SAP Mobile Platform to get a proxy connection, the URL rewrite in the response is missing the Relay Server prefix information. Workaround: None.