Last updated on DECEMBER 05, 2016
Applies to:Oracle Tuxedo - Version 10.3.0 and later
Information in this document applies to any platform.
The problem happened on the production system which was working properly for some time.
The system uses both WebLogic server (10.3.3) and Tuxedo (126.96.36.199) and WTC to communicate between the two.
The WTC stopped working, the WLS was not able to enqueue messages to Tuxedo queues and many instances of following error were found in the Weblogic Server log.
Caused by: TPETIME(13):0:0:TPED_MINVAL(0):QMNONE(0):0
at weblogic.wtc.jatmi.dsession.tpenqueue(Unknown Source)
It was also reported that the GWTDOMAIN Tuxedo process was using unusually high amount of the CPU.
We believe the problem was on Tuxedo side since the WLS restart alone didn't resolve the issue.
The problem was resolved when the whole server was restarted.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms