MetaSolv (MSS) Application Servers Start Up Failure With 'ERROR: JDWP Transport dt_socket failed to initialize'
(Doc ID 1386509.1)
Last updated on AUGUST 28, 2023
Applies to:
Oracle Communications MetaSolv Solution - Version 6.2.0 and laterInformation in this document applies to any platform.
Symptoms
MetaSolv Solution (MSS) Application server fails to start with following errors reported in MSS log:
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 [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197) : No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
Solution 1 |
Solution 2 |