If you had a static inbound agent configured in 2.426.x, there is a special compatibility mode for the config screen which allows a GUI round-trip (Configure + Save) to preserve fields which are now deprecated such as webSocket. In the case of tunnel this failed to call fixEmptyAndTrim, so that if no tunnel was specified (blank text field) the config.xml of the agent would nonetheless contain , causing the proposed launch instructions to include -tunnel (with no argument) which is incorrect.
Originally reported by 
jglick, imported from: Deprecated JNLPLauncher.tunnel round-trips null to empty string
- assignee: jglick
- status: Closed
- priority: Major
- component(s): core
- label(s): 2.452.1-fixed
- resolution: Fixed
- resolved: 2024-04-15T12:54:43+00:00
- votes: 0
- watchers: 1
- imported: 2025-11-24
Raw content of original issue
If you had a static inbound agent configured in 2.426.x, there is a special compatibility mode for the config screen which allows a GUI round-trip (Configure + Save) to preserve fields which are now deprecated such as webSocket. In the case of tunnel this failed to call fixEmptyAndTrim, so that if no tunnel was specified (blank text field) the config.xml of the agent would nonetheless contain <tunnel></tunnel>, causing the proposed launch instructions to include -tunnel (with no argument) which is incorrect.
If you had a static inbound agent configured in 2.426.x, there is a special compatibility mode for the config screen which allows a GUI round-trip (Configure + Save) to preserve fields which are now deprecated such as webSocket. In the case of tunnel this failed to call fixEmptyAndTrim, so that if no tunnel was specified (blank text field) the config.xml of the agent would nonetheless contain , causing the proposed launch instructions to include -tunnel (with no argument) which is incorrect.
Originally reported by
jglick, imported from: Deprecated JNLPLauncher.tunnel round-trips null to empty string
Raw content of original issue