Known Issues

The following sections describe known issues with the Oracle Tuxedo software and include recommended workarounds. The problems are listed by the BugDB Request (BugDB) number.

Contact your Oracle Customer Support Center for assistance in the tracking of any unresolved problems. When contacting the Oracle Customer Support Center, please refer to the BugDB number.

•	Known Issues

Known Issues

Table 1 describes the known issues for Oracle Tuxedo and provides recommended workarounds.

 

Table 1 Known Issues

1.	Bug 22955140 - Service call fails after changing a service name and reloading the module.
	Description	After changing a service name and reloading the corresponding module, a service call fails with the error TPESVCFAIL - application-level service failure.
	Platforms	All
	Workaround	Reload the entire configuration file.
2.	Bug 22986073 - Java Server could not log detailed error messages in Tuxedo ULOG
	Description	If an exception is thrown to a Java server from a user java application in Tuxedo Java Server, the detailed error message could not be logged in ULOG by Java Server. Only ERROR: Caught exception [null] is logged.
	Platforms	AIX only
	Workaround	Catch all exceptions in your Java classes and invoke userlog(<MyEx>.toString()) to log the detailed error messages.
3.	Bug 24397397 - Java Server could not update a jar file using dynamic reloading on Windows.
	Description	When you perform the reloading operation on Windows platforms, the jar file is locked and cannot be replaced with new jar file.
	Platforms	Windows only
	Workaround	There are two ways to solve it: • Place the new jar file into a different directory, and then perform the reloading operation. • Separate the reloading operation into two steps. – 1. Perform deletion operation to the server module depending on the jar file. – 2. Perform adding operation to add the server module depending on the new jar file.