Article - CS19254
Tomcat and/or method server does not start with the error "javax.naming.CommunicationException: ***.com:389" in Windchill
Modified: 07-Mar-2025
Applies To
- Windchill PDMLink 9.0 to 12.1
Description
- MethodServer failed to start with error in MethodServer.log :
java.io.IOException: com.infoengine.exception.adapter.IEAdapterException; nested exception is:
javax.naming.CommunicationException: <hostname>:389 [Root exception is java.net.ConnectException: Connection refused: connect]
at com.infoengine.au.IEProperties.resetProperties(IEProperties.java:1212)
at com.infoengine.au.IEProperties.resetProperties(IEProperties.java:1149)
at com.infoengine.au.IEProperties.resetProperties(IEProperties.java:1095)
at com.infoengine.au.IEProperties.resetProperties(IEProperties.java:1073)
at com.infoengine.au.NamingService.setProperties(NamingService.java:1329)
at com.infoengine.au.NamingService.newInstance(NamingService.java:278)
at com.infoengine.au.NamingService.newInstance(NamingService.java:210)
- During Windchill startup, the Method Server exits prematurely with the following error in the Method Server log:
javax.naming.CommunicationException: ***.com:389" [Root exception is java.net.ConnectException: Connection refused: connect]
- In Windchill 9.1 or older, Tomcat may also fail to start with the same error in localhost.###.log or windchill.log under <Tomcat>/logs/
- After restart server, method server can not start up
This is a printer-friendly version of Article 19254 and may be out of date. For the latest version click CS19254