HF RL Explorer

Issue: Incorrect remote address reported for STOMP/MQTT over WebSocket

Issue: Incorrect remote address reported for STOMP/MQTT over WebSocket: a task in LegoFlow-SWE (Harbor dataset). When a client connects to ActiveMQ via STOMP or MQTT over WebSocket, calling getRemoteAddress() on the socket transport returns an internal identifier (e.g., "StompSocket <hashCode " )…

The task

When a client connects to ActiveMQ via STOMP or MQTT over WebSocket, calling `getRemoteAddress()` on the socket transport returns an internal identifier (e.g., `"StompSocket_<hashCode>"`) instead of the actual client WebSocket URL. This makes logging, monitoring, and connection tracking unreliable.

Part of Lego-X/LegoFlow-SWE.