Monday, April 21, 2008

Mule Error: Application does not seem to be starting or is hanging

Launching a JVM...
Error [125] in bind() call!
err:: Address already in use
Socket transport failed to init.
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
JVM exited while loading the application.
The JVM is being launched with a debugger enabled and could possibly be
suspended. To avoid unwanted shutdowns, timeouts will be disabled,
removing the ability to detect and restart frozen JVMs.

The logs display the above error.

This indicates that the port for debugging is already in use, and not the actual mule application's port.

Change the debug port in the wrapper.conf.,address=5295,server=y,suspend=y

No comments: