JBoss Fuse: bin/status and scripts do not work if debug is enabled

Solution Verified - Updated -

Issue

Its possible to set

export KARAF_DEBUG=1

on the OS shell to enable JPDA (remote debugging) on the JBoss Fuse container.

When KARAF_DEBUG is enabled, the bin/status script fails with

ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [debugInit.c:750]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Aborted (core dumped)

because the status script starts a new Karaf process which tries to set the same DEBUG parameters that are already used by the JBoss Fuse container.
The issue also occurs with other scripts like a stop script.

Environment

  • JBoss Fuse
    • 6.1, 6.2
    • 7.0, 7.1, 7.2, 7.3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In