WebLogic Tuxedo Connector Administration Guide
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
The following sections provide WebLogic Tuxedo Connector troubleshooting information.
The WebLogic Tuxedo Connector uses the WebLogic Server log file to record log information. To record log information you must:
Note: For more information about setting WebLogic Server properties, see How to Set WebLogic Tuxedo Connector Properties.
To enable tracing, update the JAVA_OPTIONS
variable in your server start script to the to the desired level.
Example:
JAVA_OPTIONS=-Dweblogic.wtc.TraceLevel=100000
Use the following values to set the TraceLevel:
Use the following procedure to specify that trace information is written to the log file:
To enable dumping of user data, add the following line to the java.weblogic.Server
command.
JAVA_OPTIONS=-Dweblogic.debug.DebugWTCUData
=true
Enabling this causes user data to be dumped after the connection is connected. If no other debugging properties are enabled, then this will be the only WTC information dumped, except normal WTC error/informational messages. The dump is available in the WLS server log file.
The dump has the following format.
Outbound UDATA: buffer type (<type>, <subtype>)
+++++ User Data(size) +++++
......
Inbound UDATA: buffer type (<type>, <subtype>)
+++++ User Data(size) +++++
......
This section provides solutions to common user questions.
When I build the simpserv
example, I get the following error:
<date> <Error> <EJB> <EJB Deployment: Tolower has a class weblogic.wtc.jatmi.tpserviceHome which is in the classpath. This class should only be located in the ejb-jar file.>
This error message can be ignored for this release of the WebLogic Tuxedo Connector. The EJB wants all of the interfaces for an EJB call in the EJB jar file. However, some interfaces for the WebLogic Tuxedo Connector are implemented through the CLASSPATH, and the compiler throws an exception. When the EJB is deployed, the compiler complains that the EJB cannot be redeployed because some of its classes are found in the CLASSPATH.
Releases prior to WebLogic Server 7.0 used a WebLogic Server Startup class to start a WebLogic Tuxedo Connector session and a WebLogic Server Shutdown class to end a session. In WebLogic Server 8.1, WebLogic Tuxedo Connector sessions are managed using a WTC Service.
The Tuxedo Queuing Bridge is started if the Tuxedo Queuing Bridge and Redirections configurations exist in your WTC Service and the WTC Service is assigned to a selected server
The console displays an exception when I try to assign my WTC Service to a server. What should I do?
Make sure you have a valid WTC Service configured. Each WTC Service must have 1 or more Local Tuxedo Access Points configured before it can be assigned to a server. Your server log will display the following:
<Apr 22, 2002 4:21:35 PM EDT> <Error> <WTC> <180101> <At least one local domain has to be defined.>
I'm having trouble getting a connection established between WebLogic Tuxedo Connector and Tuxedo. What should I do?
TraceLevel
and enable Debug mode. Repeat the connectivity test and check the WebLogic Tuxedo Connector and Tuxedo log files for error messages.AclPolicy
and CredentialPolicy
attributes. If your AclPolicy
is LOCAL
, you must register the remote domain DOMAINID
as a WebLogic Server user. For more information, see User Authentication.PasswordKey
as a WebLogic Server property. For more information, see How to Set WebLogic Tuxedo Connector Properties.
You must make some changes in your WebLogic Tuxedo Connector 6.x applications (including WebLogic Tuxedo Connector 1.0) to use them with WebLogic Server 9.0. For more information, see Upgrading WebLogic Application Environments.
![]() |
![]() |
![]() |