Thursday, August 8, 2013

NodeManager : FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT


Recently I extended my BPM domain for OSB , things were good till the time I used Node Manager.

When i tried to start SOA server using node manager , I got below error :

Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath  weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
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]
<Jul 3, 2013 5:11:03 PM> <FINEST> <NodeManager> <Waiting for the process to die: 6264>

The reason is the debug mode is defaulted to "true" when i extended my domain , It was a simple fix though :

In setDomainEnv.sh set debugFlag=false or you can just remove it.

NodeManager is a charm after that.

Cheers !!