We are facing a TPEPERM (bad permissions) error when our Tuxedo server attempts to call a WebLogic service. The failure occurs when invoking the CALLEJB service.
We recently modified our Tuxedo environment to support a multi‑tenant architecture, where each tenant connects to the same WebLogic server and the same WTC port. After this change, the TPEPERM error started appearing.
The error in the Tuxedo ULOG shows that the call is being rejected with TPEPERM, even though the domain link is active
Error errorless = TPEPERM - bad permissions
Can't send request to service CALLEJB.
ULOG trace:
ULOG.us03.030226:214504.seidevd09qtz32!quartzntSABT.1283539.4015394432.0: TRACE:at: { tpcall("SSACAQtzEjbBean", 0x0x10a25508, 0, 0x0x7ffd6eff8fe0, 0x0x7ffd6eff8fd8, 0x0)
ULOG.us03.030226:214504.seidevd09qtz32!quartzntSABT.1283539.4015394432.0: TRACE:at: } tpcall = -1 [tperrno TPEPERM]
Our domain connectivity appears normal. For example:
> printdomain -d QTZ2_D09BCK_TUX_MS1
Local domain : QTZ2_D09BCK_TUX_MS1
Connected domains:
Domainid: QTZ_D09BCK_WLS_MS1
The WTC link is established, but the service call still fails with TPEPERM and there are no corresponding logs on the WebLogic Server side to check.
We are trying to understand why this permission failure occurs only after enabling multi‑tenant Tuxedo domains that all connect to the same WebLogic endpoint.
Does WebLogic WTC require explicit configuration for each Tuxedo tenant domain even if all tenants connect to the same WLS port?