Tuxedo 8.1 WSH

Hi
Using Tuxedo 8.1 (64bit) on SUN Solaris UNIX platform.
On booting the Tuxedo WSL, tuxedo starts the WSH.
1. Can someone please explain how Tuxedo assigns a port number when the WSH is started?
2. How can I determine the PORT number assigned to the WSH?
Reason I ask this is, there was a situation whereby it seemsed tuxedo tried to grab hold of a port number already being used by another process (Oracle listener).
3. How can this be avoided in the future?
Thanks in advance.
Sam

Sam,
You can specify the WSL -p minwshport and -P maxwshport options as described
at http://e-docs.bea.com/tuxedo/tux81/rf5/rf5101.htm#1534543 to force the
WSL to choose WSH ports within the specfiied range. If not specified, the
defaults are 2048 for minwshport and 65535 for maxwshport.
Ed
<Sam Dhooper> wrote in message news:[email protected]..
Hi
Using Tuxedo 8.1 (64bit) on SUN Solaris UNIX platform.
On booting the Tuxedo WSL, tuxedo starts the WSH.
1. Can someone please explain how Tuxedo assigns a port number when the
WSH is started?
2. How can I determine the PORT number assigned to the WSH?
Reason I ask this is, there was a situation whereby it seemsed tuxedo tried
to grab hold of a port number already being used by another process (Oracle
listener).
3. How can this be avoided in the future?
Thanks in advance.
Sam

Similar Messages

Problem using Tuxedo from different network

We are using Tuxedo (7.1) with Clarify eFrontOffice.
We are trying to access Tuxedo from a different network. We have a NAT address and opened the port for WSL (48800) and also a range (specified in the ubbconfig and compiled) specified for the WSH. When the Clarify client is started, it is connecting to the WSL on port 48800. When tuxedo returns the WSH port to the Client, it is also returning the IP of the server. Since the IP is not recognized in the 2nd network the communication is failing. Is there a way to retun server name instead of IP or a different IP?
Thanx

Raju,
When using Network Address Translation with /WS you should specify the -H
option to WSL (after the -- option) so that the address of the WSH can be
mapped back to an address that the client will understand. A bug related to
the WSL -- -H option was fixed at Tuxedo 7.1 rolling patch level 165, so you
should obtain the latest 7.1 rolling patch if you are running at an earlier
patch level.
The description of the -H option at
http://e-docs.bea.com/tuxedo/tux71/html/rf537.htm is as follows:
[-H external-netaddr]
Specifies the complete network address to be used as a well known address
template of the WSH process. The address will be combined with a WSH network
address to generate a well known network address used by the Workstation
client to connect to a WSH process. It has the same format as the -n option
except that it substitutes the port number with same length of character M
to indicate the position of the combined network address will be copied from
the WSH network address. For example when address template is
0x0002MMMMdddddddd and WSH network address is 0x00021111ffffffff then the
well known network address will be 0x00021111dddd dddd. When address
template starts with "//" network address type assumes to be IP based and
the TCP/IP port number of WSH network address will be copied into the
address template to form the combined network address. This feature is
useful when Workstation client needs to connect to a WSH through a router
which performs Network Address Translation.
<Raju Vatsavayi> wrote in message news:[email protected]...
We are using Tuxedo (7.1) with Clarify eFrontOffice.
We are trying to access Tuxedo from a different network. We have a NATaddress and opened the port for WSL (48800) and also a range (specified in
the ubbconfig and compiled) specified for the WSH. When the Clarify client
is started, it is connecting to the WSL on port 48800. When tuxedo returns
the WSH port to the Client, it is also returning the IP of the server. Since
the IP is not recognized in the 2nd network the communication is failing. Is
there a way to retun server name instead of IP or a differen
t IP?
Thanx

/WS client & ABORTED transactions

Hello all,
I am bit confused with "Native client" concept.
What is the diffrence between a native client & a remote (/WS ) client?
As far as i know,remote clients are those which are connected to the front end application via workstations.
I have a huge billing application residing over tux(7.1).
what is diffrence between application client & remote tux client? is it the same?
i use following command to check the users connected to tuxedo.
echo 'pclt' | tmadmin -r 2>/dev/null | egrep -v '>|-------|tpsysadm|tmadmin|WSH|^$'|wc -l
sometimes i see around 60 users connected...& i have configured only 50 WS clients in my ubb file.
is there any way i can remove unwanted users ?
also i need to clean up transactions which are in ABORTED state?
Can't we control users & transactions via tux commands?
regards
abhijeet

Workstation client is the client connected to Tuxedo with WSL/WSH. Native
client accesses the IPC queue directly. The pclt of tmadmin is different for
native client and workstation client. The later has a "/W" flag in the
status cloumn.
You can define the MAXACCESSERS in ubbconfig file to limit the users. For
example,
MAXACCESSERS = 100
MAXSERVERS=20
MAXWSCLIENTS=70
Then you leave 10 slots for WSH and tmadmin etc.
Wayne
<Abhijeet K> wrote in message news:[email protected]..
Hello all,
I am bit confused with "Native client" concept.
What is the diffrence between a native client & a remote (/WS ) client?
As far as i know,remote clients are those which are connected to the frontend application via workstations.
>
I have a huge billing application residing over tux(7.1).
what is diffrence between application client & remote tux client? is itthe same?
>
i use following command to check the users connected to tuxedo.
echo 'pclt' | tmadmin -r 2>/dev/null | egrep -v'>|-------|tpsysadm|tmadmin|WSH|^$'|wc -l
>
sometimes i see around 60 users connected...& i have configured only 50 WSclients in my ubb file.
>
is there any way i can remove unwanted users ?
also i need to clean up transactions which are in ABORTED state?
Can't we control users & transactions via tux commands?
regards
abhijeet

Intermittent tpcall() failures in Tuxedo 7.1

Hi,
In our c++ tuxedo clint application (Tuxedo 7.1), tpcall() seems to fail intermittently. It seems that the operation that tpcall is suppossed to perform on the server side and return a result is completed successfully.
But, the server log has the following entry:
095644.machine22!WSH.1924.1.0: WSNAT_CAT:1287: WARN: Forced shutdown of client; user name 'TEST'; client name '*'; workstation address '//10.132.64.66:41370'
Is this a Tuxedo 7.1 issue or a code defect? We didn't seem to have any problem when the same application ran under Tuxedo 6.5.
Does this error have anything to do with a similar issue in Tuxedo 8.1 : CR082895 WTC tpcall fails randomly while Tuxedo service completes successfully.
If yes, is there a patch available for Version 7.1? What is the patch level? We are currently using patch level 307.
How can we trap the exception thrown by tpcall() in c++?
Cheers,
Taran

Unfortunatelly I have already tried the -t flag and it didn't work! This flag is
supposed to provide compatibility with pre-7.1 tuxedos so it wasn't supposed to
help in the first place.
"roopesh" <[email protected]> wrote:
>
I think there is a flag of -t which you can specify
on GWTDOMAIN CLOPT option for the domain on 8.0 to work
with domains on lower versions.
try this
Thanks
"Dimitris Paleocostas" <[email protected]> wrote:
Hello everyone,
I am trying to setup Tuxedo8.0 Domain(Win2000) to call services from
a Tuxedo7.1
Domain(Compact Tru64). I have everything setup correctly (dmConfig files
e.t.c.).
When trying to call a service from Tuxedo8.0 to Tuxedo7.1, I receive
a TPESYSTEM
error 12 - internal system error in the Tuxedo 8.0 ULOG and a LIBGWT1313(:The
gateway received a poorly formatted message from the specified remote
domain and
is unable to recognize it.) in the Tuxedo7.1 server ULOG.
I have enabled the SSL option (without any parameters during the installation
of Tuxedo8.0). Could that be making the diference?
Note: When I reverse the routing settings in the dmConfig /ubbconfig
files I am
ablke to place a call from tuxedo7.1 to tuxedo8.0! The opposite refuses
to work!

Tuxedo Client on Windows Server 2003/2008

I know this is a little unorthodox, and probably not supported, any pointers on possible problems with WSL and WSH would be nice though.
I'm trying to run a .NET application that acts as a Tuxedo client on the Windows Server 2008 operating system. I've tried this with multiple versions of the Tuxedo client software, including 7, 8, 9, and 10. The application works fine on Windows XP.
My client ULOG:
120157.CI2009CORE!?proc.3376.2624.1: LIBWSC_CAT:1055: ERROR: Unable to establish WSL connection
120157.CI2009CORE!?proc.3376.2624.1: LIBWSC_CAT:1027: ERROR: Unable to connect to WSH
120157.CI2009CORE!?proc.3376.2624.1: LIBWSC_CAT:1020: ERROR: Unable to obtain authentication level
Has anyone tried something like this before? Is there a server 2008 setting I'm missing?
EDIT:
Same problem on a server 2003 machine. Using the 10.0 win 2003 installation and tried it with the 10.0 winXP install.
Edited by: user1953107 on Feb 16, 2009 3:23 PM

My original problem with the WSL seems to have been not having enough environment variables and the tux.env file set. This leads me to another problem though. I need to be able to set the WSNADDR at runtime, which I thought I was doing, but the API seems to insist on using the environment settings instead of what is set in the application.
Example:
TypedTPINIT tpinfo = new TypedTPINIT();
tpinfo.flags = TypedTPINIT.TPMULTICONTEXTS;
Utils.tuxputenv("WSNADDR=//NOTVALID");
AppContext ctx1 = AppContext.tpinit(tpinfo);
TypedString requestString = new TypedString(tbInputData.Text);
TypedBuffer replyBuffer = new TypedString(0);
ctx1.tpcall(tbServiceName.Text, requestString, ref replyBuffer, 0);
string result = ((TypedString)replyBuffer).GetString(0, (int)replyBuffer.Size);
ctx1.tpterm();That ought to fail completely because the WSNADDR "//NOTVALID" doesn't point anywhere. I only use an invalid WSNADDR for illustration, because even when I set WSNADDR in the code to a valid location, the API uses what is in the env file instead. Likewise I can set the env file to an invalid location, but use a good one in the code and the system will also fail.
I really need to determine WSNADDR at runtime, how do I do that? I believe I'm following the instructions found at Link: [http://edocs.bea.com/tuxedo/tux100/dotnet/dotnet_chapter.html] and not getting the desired results.

Tuxedo 6.5 Timed out error is locking up the server

Hello all,
I am hoping someone will be able to help me with my problem.
When a client tries some updates using our software, they get the following error
message:
"Timed out waiting for server to acknowledge attention"
Any subsequent processing on this server causes the following messages:
"Attempt to initiate a new SQL Server operation with results pending"
"Unable to Rollback() monitor:'AmsDatabaseConnection'! due to unknown exception!"
"Cannot perform more than one read"
As best as I can tell (which could be wrong), this only occurs to specific clients
that have to go through a firewall. However once those clients encounter the
original problem, everyone is affected.
I don't what is causing the problem. The only way I am able to "fix" the problem
is by restarting the servers. Is there a way for tuxedo to clean up these processes?
Under tmadmin on the server, there is nothing running on the offending servers,
there are no messages in the queue. I do not know what could be the problem.
I have added the -K both flag to the WSL, and I have also added the -N flag to
the WSL, I have also increased the BLOCKTIME to allow the client processes more
time to work. HOwever, none of these changes seem to work.
In the client's ULOG are the following messages:
1065 ERROR: Unable to close WSH connection
1025 ERROR: Unable to send tpterm() request
Any help or suggestions would be greatly appreciated, as I have been pulling my
hair out trying to figure this out.
- Ted

Ted,
The error you posted below is not a Tuxedo error. It is your application error, in
response to some Tuxedo error code, I would imagine.
The WSL has a -K option to turn on Keepalive at the network level. This can keep a
firewall from disconnecting due to lack of traffic.
The SQL errors are from the sequence of operations that your are executing from
your application code. Unless you are using transactions, the database can not
distinguish one service request from the next. The database simply receives a
comtinuing series of requests. It looks like it never cleaned up from the previous
service call.
As Wayne suggested, TMTRACE might show you the sequence of Tuxedo operations
interleaved with your application errors, so that you can better track down what
has happened.
Scott Orshan
Ted Unnikumaran wrote:
Hello all,
I am hoping someone will be able to help me with my problem.
When a client tries some updates using our software, they get the following error
message:
"Timed out waiting for server to acknowledge attention"
Any subsequent processing on this server causes the following messages:
"Attempt to initiate a new SQL Server operation with results pending"
"Unable to Rollback() monitor:'AmsDatabaseConnection'! due to unknown exception!"
"Cannot perform more than one read"
As best as I can tell (which could be wrong), this only occurs to specific clients
that have to go through a firewall. However once those clients encounter the
original problem, everyone is affected.
I don't what is causing the problem. The only way I am able to "fix" the problem
is by restarting the servers. Is there a way for tuxedo to clean up these processes?
Under tmadmin on the server, there is nothing running on the offending servers,
there are no messages in the queue. I do not know what could be the problem.
I have added the -K both flag to the WSL, and I have also added the -N flag to
the WSL, I have also increased the BLOCKTIME to allow the client processes more
time to work. HOwever, none of these changes seem to work.
In the client's ULOG are the following messages:
1065 ERROR: Unable to close WSH connection
1025 ERROR: Unable to send tpterm() request
Any help or suggestions would be greatly appreciated, as I have been pulling my
hair out trying to figure this out.
- Ted

Tuxedo and Network Address Translation(NAT) at Firewall

We made a sucessful connection through the firewall without Network Address Translation
(NAT)on the firewall, from one network to the other and what we found happened
was that the client machine makes a connection on port 8090 and then sets up a
successful connection to the server (WSL).The client then very soon afterward
makes another connection on
another high-port and everything works (WSH connection).
Whats not happening with NAT is that the second connection is not being made to
the firewall. The firewall and the router are not blocking the call. It is just
not being made.
Thanking you in advance!!!
Nathaniel

Nathaniel,
Take a look at the WSL -H option at
http://edocs.bea.com/tuxedo/tux80/atmi/rf540.htm#1534543
Regards,
Peter.
Got a Question? Ask BEA at http://askbea.bea.com
The views expressed in this posting are solely those of the author, and BEA
Systems, Inc. does not endorse any of these views.
BEA Systems, Inc. is not responsible for the accuracy or completeness of
the
information provided
and assumes no duty to correct, expand upon, delete or update any of the
information contained in this posting.
Nathaniel Sebolai wrote:
We made a sucessful connection through the firewall without Network Address Translation
(NAT)on the firewall, from one network to the other and what we found happened
was that the client machine makes a connection on port 8090 and then sets up a
successful connection to the server (WSL).The client then very soon afterward
makes another connection on
another high-port and everything works (WSH connection).
Whats not happening with NAT is that the second connection is not being made to
the firewall. The firewall and the router are not blocking the call. It is just
not being made.
Thanking you in advance!!!
Nathaniel

How to dynamic client limitation in tuxedo ?

I want to limit client concurrent session per tux-user in tuxedo 8.0.
But, I don't want to limit maximum WSH in UBB config file.
How should I do for this case ?

have you tried
binder.getLocal("REMOTE_ADDR");
Let us know how you get on
Tim

How to configure tuxedo to work on server having NAT

I want to my application to the tuxedo . from a remote location , the server on which the tuxedo is installed has a NAT on it . I have updated the WSl port and th IP in the tpinit properties file but still i wam unable to establish a connection to the tuxedo . Pease help me

When you connect to a Tuxedo application from a remote server, you need to take care of 2 things:
1. If there is a firewall between the client and the server, you need to open up the WSL port and ALL the WSH ports in the firewall.
2. If there is a NAT (either in the firewall or otherwise) between the client and the server, you need to use -H option with WSL. To understand this, briefly, this is how the work station connection in Tuxedo works -
- Client connects to WSL
- WSL assigns the client to a WSH, and returns WSH's port/address to the client.
- Client now uses the info received to connect to the WSH.
For this to work under NAT, WSL has to send NAT-ed address to the client. To make it send NATed address, you need to use -H option and give the translation information to WSL. If you dont, the address sent by WSL wont be a valid one for the client to connect to.
Hope this helps.
-Niranjan

TPINIT error Unable to establish WSH connection 0x000221150afea683

Dear All,
we have applications deployed using tuxedo. All the applications are in working condition, but one new application is deployed with same parameters of working applications but on new client application on Windows 2008 server.
This application cannot access the tuxedo server and giving following error.
152035.WEBAPP!?proc.4020.3152.0: 01-30-2013: Tuxedo Version 11.1.1.2.0 with VS2010, 64-bit
152035.WEBAPP!?proc.4020.3152.0: LIBWSC_CAT:1064: ERROR: Unable to establish WSH connection 0x000221150afea683
152035.WEBAPP!?proc.4020.3152.0: LIBWSC_CAT:1055: ERROR: Unable to establish WSL connection
152035.WEBAPP!?proc.4020.3152.0: LIBWSC_CAT:1027: ERROR: Unable to connect to WSH
152035.WEBAPP!?proc.4020.3152.0: LIBWSC_CAT:1020: ERROR: Unable to obtain authentication level
The same application is working on 32 bit 2003 server. and only changed this in 64 bit 2008 server.
My .bat file on the client is as follows. The tuxedo server is already serving all other clients except this one. Server version is tuxedo10gR3. Firewall on this client is also disabled
cls
set APPDIR=C:\bea\prs\
set WSNADDR=//202.25.16.11:7025
set TUXDIR=C:\\bea\\tuxedo11gR1_VS2010
set PATH=%TUXDIR%\\bin;%APPDIR%;%PATH%
set LD_LIBRARY_PATH=%TUXDIR%\\lib
@echo on
echo "Processing online recovery file: " %2
echo %TUXDIR%
echo %WSNADDR%
echo %LD_LIBRARY_PATH%
cd C:\bea\prs
c:
C:\bea\prs\prs.exe %1 %2 %3 %4
Edited by: user6951085 on Jan 30, 2013 2:42 AM

Dear All,
I found out why this is happening(with the Help of Oracle support), so updating it for future use.
Tuxedo uses random ports for clients that have connected to WSL listener. thats why my first error
152035.WEBAPP!?proc.4020.3152.0: LIBWSC_CAT:1064: ERROR: Unable to establish WSH connection 0x000221150afea683
was coming. this means (as per the documentations) that the WSL have accepted the connection but the next step of connecting to WSH is not done. which causes the above error.
The resolution can be 2 things.
1. Allow allow ports of Server or range of ports starting from port of WSL e.g. port WSNADDR port 7777 to 7777+2000 ports , so that clients can access the WSL port + 2000 ports
2. add a parameter on the tuxedo server ubb file to define a range of ports which can handle client requests. (most probably in the WSL CLOPT portion)
if your network has security and it only allows some ports to be accessed , u can get this error.
Thanks.
Edited by: user6951085 on Jan 31, 2013 1:18 AM

How can i change the WSH counts by using ud32

I want to dynamically change the min and max WSH count, but i get the following error:
TA_STATUS LIBTMIB_CAT:147: ERROR: Permissions violation on SET request.
My ubb file:
*SERVERS
WSL SRVGRP=GROUP1 SRVID=20 CLOPT="-A -- -n //192.168.135.211:6666 -m 3 -M 5 -x 5"
My ud32 script file which is named update_wsl.ud :
SRVCNM .TMIB
TA_OPERATION SET
TA_CLASS T_WSL
TA_SRVGRP GROUP1
TA_SRVID 20
TA_MINHANDLERS 5
TA_MAXHANDLERS 10
comand:
[tuxedo@tdy218 simpapp]$ ud32 -C tpsysadm < update_wsl.ud
SENT pkt(1) is :
TA_MAXHANDLERS 10
TA_MINHANDLERS 5
TA_SRVID 20
SRVCNM .TMIB
TA_CLASS T_WSL
TA_OPERATION SET
TA_SRVGRP GROUP1
CMDTUX_CAT:994: ERROR: Reply failure - TPESVCFAIL - application level service failure
TA_BADFLD 33560898
TA_ERROR -5
TA_MAXHANDLERS 10
TA_MINHANDLERS 5
TA_SRVID 20
SRVCNM .TMIB
TA_CLASS T_WSL
TA_OPERATION SET
TA_STATUS LIBTMIB_CAT:147: ERROR: Permissions violation on SET request
TA_SRVGRP GROUP1
Permissions
TA_MINHANDLERS rwxr-xr--
TA_MAXHANDLERS rw-r--r--
[tuxedo@tdy218 simpapp]$ tmadmin -v
INFO: Oracle Tuxedo, Version 10.3.0.0, 32-bit, Patch Level 070
[tuxedo@tdy218 simpapp]$ more /etc/redhat-release
Red Hat Enterprise Linux Server release 5.4 (Tikanga)
[tuxedo@tdy218 simpapp]$ uname -a
Linux tdy218 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:54 EDT 2009 i686 i686 i386 GNU/Linux
Why? Does any on know ?

Hi,
Can you share the solution so if others have need to do something similar they might be able to find the answer here?
Thanks,
Todd Little
Oracle Tuxedo Chief Architect

Call of tuxedo workstation client to tuxedo service

In ubb file:
"WSL" SRVGRP="GRP" SRVID=44
CLOPT="-A -- -p 10002 -n //172.17.1.10:10001 -P 10003 -T 180"
My question is:
1. In workstation client, WSNADDR is //172.17.1.10:10001. If I use "172.17.1.10:10001", it prompts "TPESYSTEM - internal system error", while "//172.17.1.10:10001" is right?
2. 10001 is the port of WSL, 10002-10003 is the port of WSH. But in ubb file, I cannot find WSH configuration, is that right?
3. If "telnet 172.17.1.10 10002(/10003)" doesn't work in workstation client, does it impact the call of tuxedo service from this workstation client?
Thanks a lot.

Bill,
1. Tuxedo syntax for specifying TCP/IP addresses requires that the address start with "//", so it is expected behavior for "172.17.1.10:10001" to result in an error and for "//172.17.1.10:10001" to be correctly parsed.
2. You're correct that the UBBCONFIG file does not include entries for WSH processes. WSH processes are started by the WSL as appropriate.
3. The Tuxedo WSH communicates with workstation clients and with the WSL using a proprietary Tuxedo workstation protocol. The WSH does not understand telnet protocol, so any attempt to telnet to the WSH port will not succeed.
Regards,
Ed

Tuxedo behind firewall

Hello. I need to know what ports I need to open on my firewall to allow users to gain access to our CRM application behind our firewall. I'm sending them through a secure tunnel with http access and can't get to a login page. Thanks for the help.

You would get more Tuxedo attention in the tuxedo.general group. However, if you are using
/ws clients and a WSL on the server side, you specify the ports in the CLOPT with '-p' and
'-P'. The WSH processes will use ports in that range. Those are the ones to open on the
firewall.
hope that helps,
Wayne Scott
Jon Calisi wrote:
Hello. I need to know what ports I need to open on my firewall to allow users to gain access to our CRM application behind our firewall. I'm sending them through a secure tunnel with http access and can't get to a login page. Thanks for the help.

There are errors on the Tuxedo-client (ULOG) while trying to work with Serv

Hello,
What we have:
1. Tuxedo-server 8.1. (HP-UX)
2. Tuxedo-client 9.1 (AIX 6.1)
3. Java-program
4. C-library which is supposed to work with tuxedo service (server side)
and what we want:
1.Java-program loads C-library using JNI and tries to communicate with Tuxedo service on server side.
2. We get ULOG file on tuxedo-client side with errors which are after tpsend function. Program finishes after time out.
3. We do not have JOLT system installed.
Here are the errors from ULOG-file:
114055.puma!AIX2C2TUX_stain.860250.515.0: 01-19-2011: Tuxedo Version 9.1, 64-bit
114055.puma!AIX2C2TUX_stain.860250.515.0: LIBWSC_CAT:1332: ERROR: Unable to set mode to NONBLOCK
114055.puma!AIX2C2TUX_stain.860250.515.0: LIBWSC_CAT:1085: ERROR: Unable to get reply to unsolicited message request
114055.puma!AIX2C2TUX_stain.860250.258.0: LIBWSC_CAT:1332: ERROR: Unable to set mode to NONBLOCK
114055.puma!AIX2C2TUX_stain.860250.258.0: LIBWSC_CAT:1085: ERROR: Unable to get reply to unsolicited message request
114055.puma!AIX2C2TUX_stain.860250.1029.0: GP_CAT:1241: ERROR: An error occurred in the encryption subsystem code(60)
114055.puma!AIX2C2TUX_stain.860250.1029.0: LIBWSC_CAT:1512: ERROR: Unable to generate first diffie-hellman packet
114055.puma!AIX2C2TUX_stain.860250.1029.0: LIBWSC_CAT:1055: ERROR: Unable to establish WSL connection
114055.puma!AIX2C2TUX_stain.860250.1029.0: LIBWSC_CAT:1027: ERROR: Unable to connect to WSH
114055.puma!AIX2C2TUX_stain.860250.1029.0: LIBWSC_CAT:1020: ERROR: Unable to obtain authentication level
114055.puma!AIX2C2TUX_stain.860250.772.0: GP_CAT:1241: ERROR: An error occurred in the encryption subsystem code(60)
114055.puma!AIX2C2TUX_stain.860250.772.0: LIBWSC_CAT:1512: ERROR: Unable to generate first diffie-hellman packet
114055.puma!AIX2C2TUX_stain.860250.772.0: LIBWSC_CAT:1055: ERROR: Unable to establish WSL connection
114055.puma!AIX2C2TUX_stain.860250.772.0: LIBWSC_CAT:1027: ERROR: Unable to connect to WSH
114055.puma!AIX2C2TUX_stain.860250.772.0: LIBWSC_CAT:1020: ERROR: Unable to obtain authentication level
I googling for a while but could not get a clue to solve this.
Any help appreciated.
Thanks.
Andrei

Hi Andrei,
First, JNI loading the Tuxedo client libraries is not supported by Oracle. That isn't to say it won't work, it's just that Oracle won't support you. What you are trying to do, access Tuxedo services from Java, is exactly what Jolt is designed to provide and is the Oracle supported way to do this.
That being said, my guess is that the JVM process environment is somehow restricting what the workstation libraries can do with the network as you are getting fundamental networking errors. How you work around this I can't really say.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Access log generated in tuxedo 10R3

Ed or Todd,
One of our customers complained about the access.MMDDYY files generated in APPDIR in this version of tuxedo. Can we disable it? Thanks!
messages in the files:
163100.jfkdappsys01!WSH.3572.4156495552.0: total client (9), logon: /WS IP (//10.5.2.53:2273), cltname (user) success
163100.jfkdappsys01!WSH.3572.4156495552.0: total client (9), logoff: /WS IP (//10.5.2.53:2273), cltname (user) success
163105.jfkdappsys01!WSH.3573.4156516032.0: total client (9), logon: /WS IP (//10.5.2.53:2281), cltname () success
163110.jfkdappsys01!WSH.3573.4156516032.0: total client (9), logoff: /WS IP (//10.5.2.53:2281), cltname () success
163110.jfkdappsys01!WSH.3574.4156647104.0: total client (9), logon: /WS IP (//10.5.2.53:2288), cltname (user) success
172113.jfkdappsys01!WSH.3574.4156647104.0: total client (9), logoff: /WS IP (//10.5.2.53:2288), cltname (user) success
Wanglai Li

Hi Wanglai,
Yes, it is an enhancement in that release and intentionally it can't be disabled. I thought there was a previous post here about how you might be able to redirect it, but I can't find that post. I'll see if I can get an engineer to chime in here and tell you what if anything is possible.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

Tuxedo 8.1 WSH

Similar Messages

Maybe you are looking for