WebLogic Tuxedo Connector(a.k.a. WTC) Service On A Managed Server, In A Cluster, Does Not Start When The Administration Port Is Enabled
(Doc ID 1637659.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle WebLogic Server - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
When the administration-port is disabled (by WLS configuration) managed servers in a cluster, and their WTC service, are able to run.
When the administration-port is enabled the WTC service is not able to start, in the managed servers, with the following startWTC runtime exception:
<Mar 19, 2014 1:23:45 PM EDT> <Info> <WTC> <BEA-180001> <WTC finished parsing the configuration MBean information.>
Caused by: java.lang.RuntimeException: startWTC failure: Unable to resolve 'weblogic.management.adminhome'. Resolved 'weblogic.management'
the below exception occurs later on when a connection is attempted, for a CORBA service, with a remote Tuxedo domain:
Upgraded from Weblogic 11g to Weblogic 12c.
Weblogic configuration moved to separate Virtual Linux servers. The WebLogic servers previously ran co-located with the Tuxedo servers.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document