Known and Resolved Issues

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Known and Resolved Issues

The following sections describe known issues with the Oracle Tuxedo software and include recommended workarounds. The problems are listed by the Change Request (CR) number. The CR number is provided to facilitate the tracking of these problems.

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 CR number.

 


Known Limitations

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

Table 1 Known Limitations
  1.  
Best performance is obtained when buffer size is smaller than 100KB.
 
Description
When buffer size is greater than 100KB, Direct Cross Node Communication Leveraging RDMA feature lowers performance.
 
Platforms
All
 
Workaround
Disable Direct Cross Node Communication Leveraging RDMA feature when buffer size is greater than 100KB.
  1.  
Jolt SSL does not work with Oracle JDK 1.6 u32 and JDK 7
 
Description
Jolt SSL in Tuxedo 12cR1 does not work with Oracle JDK 1.6 u32 and JDK 7.
 
Platforms
All
 
Workaround
Use Oracle JDK 1.6 u37 or Oracle JDK 1.6 u26
with Jolt SSL.
  1.  
XmlHelper::save() loses content of XML document of mixed type
 
Description
In a schema where a type is defined as follows:
<xsd:complexType name="myType" mixed="true"> ...
A document cannot be loaded by SDO XmlHelper, then saved as its original content. For example:
...
       Dear Mr.<name>John Smith</name>.
       Your order <orderid>1032</orderid>
       will be shipped on <shipdate>2001-07-13</shipdate>.
...
can only be saved as:
...
       <name>John Smith</name>
       <orderid>1032</orderid>
       <shipdate>2001-07-13</shipdate>
...
 
Platforms
All
 
Workaround
These types of documents should be handled directly by the application code.
  1.  
Error data sent is ignored when Web service binding is used to connect two Tuxedo domains
 
Description
The current implementation of Web services binding only returns the fault string when a SOAP fault occurs. For those services where fault detail may contain additional information or data (as handled by the GWWS SALT gateway), ServiceInvocationException has no place or mechanism to store this data.
This may happen:
  • when attempting to invoke an existing Tuxedo service exposed as a Web service from an SCA component or SCA client.
  • only between two Tuxedo domains.
 
Platforms
All
 
Workaround
Use ATMI binding and /Domain feature to connect two Tuxedo domains.
  1.  
JATMI binding does not support transaction.
 
Description
The JATMI binding crashed when running with transaction because the JATMI container does not have sufficient transaction support for TSESSION.
 
Platforms
All
 
Workaround
The services accessed may be configured as AUTOTRAN.
  1.  
JATMI reference binding does not check the presence of two different serviceType
 
Description
JATMI reference binding does not check the presence of two different serviceType, inputBufferType, outputBufferType and errorBufferType elements without specifying a target attribute.
 
Platforms
All
 
Workaround
To avoid this problem, you should not configure duplicated XML elements for ATMI binding without specifying target in the composite file.
  1.  
Sometimes invoking tpabort in an Oracle Tuxedo client fails
 
Description
This issue only occurs when a Java server is involved in a transaction. Sometimes the transaction is committed automatically before tpabort is invoked in an Oracle Tuxedo client.
 
Platforms
Linux x86 32-bit
 
Workaround
None
  1.  
"Command.run( ): process completed before monitors could start" appears during installation
 
Description
During Oracle Tuxedo installation, the following error message sometimes appears: "Command.run( ): process completed before monitors could start."
 
Platforms
OEL5 x86 64-bit
 
Workaround
You can safely ignore this message.

 


Product Constraints

Table 2 describes product constraints for Oracle Tuxedo and provides recommended workarounds.

Table 2 Product Constraints 
  1.  
Have to rebuild TMS servers when upgrading tuxedo to 12.1.1
 
Description
TMS server binaries have to be re-compiled and re-linked after upgrading Tuxedo to 12.1.1.
 
Platforms
All
 
Workaround
None.

 


Resolved Issues

Any software or documentation fixes that are made to Oracle Tuxedo 12c Release 1 (12.1.1) are reported in updates to this section.

Table 3 lists the software and documentation problems that have been fixed in Release 12c Release 1 (12.1.1). Problems are listed by bug number.

Table 3 Problems Fixed in Oracle Tuxedo 12c Release 1 (12.1.1)
  1. 10087453
GWTDOMAIN connections not reported to event broker
  1. 11075862
Request to improve tmqueue/tmqforward restart after they died
  1. 11769303
Exception not always thrown by corba client timeout occurs within commit
  1. 12706766
TPNOTIY with a new flag to return immediatly after checking that client exist
  1. 12895294
Need faddr/frange for gwtdomain
  1. 13109309
tmadmin pq queue count too high for app servers on as5 multicore
  1. 13350779
Dynamic change to min=0 for servers fails
  1. 13354862
Enhancement request: new api to get the username (principal name) from security
  1. 13358022
QMADMIN leaves orphan process
  1. 13385815
Can not compil simpappssl corba sample provided by tuxedo product
  1. 13449208
Possible gwtdomain hanging on message
  1. 13458820
Enhancement request: shift-jis message catalog garbled on aix
  1. 13476066
iiop request indefinitely waits for response
  1. 13478819
gwtdomain core dump on _dom_freend
  1. 13535072
Event notification thread goes into tight loop
  1. 13594998
gwtdomain sometimes don't process any reqeust for some seconds
  1. 13630313
Message leak when tm_mqi has multiple instances
  1. 13649274
libfml_cat:3: error: no space in fielded buffer
  1. 13724874
tmboot catalog error, nls:4: cannot open message catalog, libtux_cat,.lang=c
  1. 13741289
Context leaks when using tpmulticontexts and tpu_thread with /ws client
  1. 13895423
Building tuxedo mq adapter with only mq tx client installed
  1. 13930115
[ER] tuxedo mq adapter fail recover mechanism
  1. 13930116
[ER] allow mutli threading in tm mq adapter server
  1. 13965614
gwws can not handle crlf
  1. 13965770
[er] add patchlevel attribute winthin release xml element of registry.xml
  1. 13994890
TM_KILL_WITH_BBLOCK does not work under high load
  1. 14041741
MULTIPLE RDOMS ON ON_DEMAND mode cause other normal services not used
  1. 14116565
gwtdomain send dmkeepalive msg every second when remote domain no response
  1. 14135406
CONVERSATIONAL SERVER SPAWN/DECAY FUNCTION doesn't work correctly
  1. 14144929
gwws makes outbound call got tpesystem occasionally
  1. 14214734
Outbound attribute failed with error type and/or subtype do not match
  1. 14231888
/DOMAIN doesn't support fml32 buffer bigger then 70000 bytes
  1. 14308647
rp installer outputs error message
  1. 14323552
Q_CAT:1353 occurs when tpdequeue() rolled back
  1. 14339774
wsl backlog can config in windows
  1. 14348578
LIBTUX_CAT:681 occurs when long running on windows
  1. 14354417
Service name not displayed when reporting libtux_cat:1401


  Back to Top       Previous  Next