1. Home
  2. Support
Article - CS163539

"Method Server" starts up successfully, but the "Background MethodServer" doesn't even intialize, no logs are generated on Windchill PDMLink

Modified: 25-Apr-2024   


Applies To

  • Windchill PDMLink 9.0 to 13.0

Description

  • Windchill Method Server or Background MethodServer could not start
    • Method Server(MS) starts up successfully, but the Background MethodServer(BGMS) doesn't even initialize
    • Or Background Method Server starts successfully, but Method Server doesn't even initialize
    • On a system configured with multiple MS's, the first MS starts up successfully. But subsequent Method Servers and the BGMS don't start
  • System is configured to connect to a remote java debugger, like the Eclipse debugger
    • The property wt.manager.cmd.MethodServer.debug.args of wt.properties is set to something like the below in wt.properties:
wt.manager.cmd.MethodServer.debug.args=-agentlib\:jdwp\=transport\=dt_socket,address\=8000,server\=y,suspend\=n
  • ​The following error is thrown when attempting to run the MS/BGMS start command from a Windchill shell:
    • Refers to CS26192 for how to run MS/BGMS start command from a Windchill shell
      • 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 intialized [../../../src/share/back/debugInit.c:690]
        FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)​
  • Server Manager shows below error.
    • ERROR : wt.manager.ServerManagerImpl - Start of BackgroundMethodServer timed out.
This is a printer-friendly version of Article 163539 and may be out of date. For the latest version click CS163539