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 JANUARY 19, 2018

Applies to:

Oracle WebLogic Server - Version 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'
   at weblogic.wtc.gwt.WTCService$WTCServiceActivateService.run(WTCService.java:660)
   at weblogic.transaction.internal.StartupClass.main(StartupClass.java:33)

the below exception occurs later on when a connection is attempted, for a CORBA service, with a remote Tuxedo domain:

<Mar 19, 2014 1:41:00 PM EDT> <Error> <Kernel> <BEA-000802> <ExecuteRequest failed
   at weblogic.wtc.gwt.OatmialServices.getInboundRdomsAssociatedWithXid(OatmialServices.java:444)
   at weblogic.wtc.gwt.OatmialUnknownXidHandler.execute(WTCService.java:8141)
   at weblogic.wtc.wls.WlsTaskHandler.run(WlsTaskHandler.java:30)
   at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)
   at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)




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.


Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms