[FDS-21] After having configured jvm.config for debugging my server does not start any more!

Description

I’ve added the debugging settings required by FusionDebug to my servers configuration file /opt/jrun4/bin/jvm.config and now my server does not start any more.

When I start the server with

/opt/jrun4/bin/jrun start

I get the following error message:

Error [98] in bind() call!
<<<<<<< support.html
FATAL ERROR in native method: No transports initialized
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.

This is caused by the attempt to start all servers sharing the same configuration (which is the default). The port number you have defined in the debug settings can only be used by one server at a time. Therefor either start only the server you want to debug, e.g.

/opt/jrun4/bin/jrun start cfusion

or use separate JVM configuration files for each server. Read the Adobe technote to get the details on how to do that.

Issue Details

Type: Technote
Issue Number: FDS-21
Components: Configuration
Environment:
Resolution: Fixed
Added: 18/05/2007 13:54:33
Affects Version: 2.0
Fixed Version: 2.0
Server:
Platform: Solaris, MacOS, Linux, Windows 2003, Windows 2000, Windows XP
Related Issues:
  • FDS-17 – FusionDebug fails to launch, with the error “Transport dt_socket failed to initialize”.
  • FDS-20 – How do I modify my jvm.config file for debugging?
  • FDS-24 – Can I use FusionDebug with a MultiServer configuration?
  • FDS-71 – How do I debug on a remote computer?
  • FDS-80 – FusionDebug could not connect to the target system (Localhost:8000). Please ensure the debug agent is listening on the system, check you configuration file – Mac OS X
  • FDS-85 – Windows could not start the CF MX7 Server on Local Computer…refer to service-specific error code 2
  • FDS-93 – How do I configure FusionDebug to work with multiple servers or multiple instances?

Comments are closed.