Proc.17086.1.-2: LIBTUX_CAT:6274: ERROR: TMNOTHREADS set to yes but multipl

Hi
I am seeing above errors in my ULOG and i have made sure TMNOTHREADS=yes , is set in the environment. We are not using threads and thread functions in my client and server.
we are using tux80 on hp11i
we get ocassional failures and below is the snippet
proc.17086.1.0: LIBTUX_CAT:6242: ERROR: Invalid user password
17086.1.0: LIBWSC_CAT:2005: ERROR: gssapi function returned failure -3003
proc.17086.1.-2: LIBTUX_CAT:6274: ERROR: TMNOTHREADS set to yes but multiple threads detected: 1/0
why does buildclient add -lpthread default ?
Vasu

Ronan,
This error message tells us your application password stored in
TPINIT.passwd does not match the one which was input when creating
TUXCONFIG.
I would like suggest following checking,
1. If compiling the same workstation client to native client, can you get
the same error message ? If the native client works correctly and this
problem came up after a particular Tuxedo rolling patch, please contact BEA
support.
2. If possible, recreate your TUXCONFIG from UBBCONFIG and input the
application password again.
Hope some help.
Wayne
<Ronan Shee> wrote in message news:[email protected]..
Good day and thanks in advance for one's advice in this column. 
Background and Error 
- "LIBTUX_CAT:6251: ERROR: A workstation client does not have a properapplication password" 
- Recently, our system was logged with this error message in TuxedoULOG. 
>
Findings 
- The version of Tuxedo (8.0, Patch Level 331) that we are using isbelieved to have addressed the issue faced in previous version of
Tuxedo. 
- We are able to simulate that error message with a bad batchapi call(i.e. setting an invalid "tux.user" value in a batch program's
"tpinit.properties" file). 
- Tried changing the different logging parameters but was still not ableto trace / identify the source (program, IP) of this fault. 
>
Questions 
1.a) May I know, is there a logging parameter that can be turned on inorder for the system to log more information (program name, transaction
call, IP address) about the calling program / machine? 
1.b) If yes, where will it be written to (ULOG)? 
2) Are there any other causes for this error?
 
 
One's advice / feedback shall be much appreciated. Thank you.
 
 
Best Regards

Similar Messages

LIBTUX_CAT:1278 errors and access log entires

Hi,
On our development database, we're observing the LIBTUX_CAT 1278 warnings quite often. Each of these entries are accompanied by an lines in the access log of the same day.
Question is:
What do the access log entries mean? How are the two entries in the two files (the ULOG and access.ddmmyy files) related?
125419.usplsoplhdimf03!?proc.13754.1.-2: 09-03-2010: Tuxedo Version 10.3.0.0, 64-bit
125419.usplsoplhdimf03!?proc.13754.1.-2: LIBTUX_CAT:1278: ERROR: Cannot join application - permission denied
$ grep 13754 *
access.090310:125408.usplsoplhdimf03!?proc.13754.1.0: total client (17), logon with AUTH: NATIVE cltname (tpsysadm) usrname (OB4D2_SVR) success
access.090310:125419.usplsoplhdimf03!?proc.13754.1.0: total client (17), logoff with AUTH: NATIVE cltname (tpsysadm) usrname (OB4D2_SVR) success
Thanks.

I can't say for sure what is happening here, but my guess is that process 13754 may be calling tpterm() on some and then continuing to call other ATMI APIs.
Most Tuxedo client APIs perform an implicit tpinit((TPINIT *)NULL) if called by an application which has not previously called tpinit(). Since this implicit tpinit does not include any authorization information, it can only succeed in an application with no authorization.
The evidence is that your application performed a successful tpinit() (logon) at 12:54:08. The access log indicates that authorization was used. At 12:54:19 the application performed tpterm() (logoff). During the same second another tpinit() was unsuccessful. Most likely this was an implicit tpinit((TPINIT *)NULL) done by some other call such as tpcall(), tpconnect(), tpacall(), or another ATMI function.
In order to further debug the problem, you may want to
export TMTRACE=*:ulog:dye
in the client which is failing. This will cause a record of all ATMI calls to be written to the userlog.
Regards,
Ed

LIBTUX_CAT 594 error

WHat is the solution for overcoming the LIBTUX_CAT 594 error..

This usually happens when the machine name in your Tuxconfig does not match the
actual machine name.
artram wrote:
Hi.
Please solution follow message...
Windows2000 server, ws client ....
110738.ARTRAM!?proc.2188.2644.0: LIBTUX_CAT:594: ERROR: Unable to locate PE entry in the Bulletin Board
594 ERROR: Unable to locate PE entry in the Bulletin Board
DESCRIPTION
The TUXEDO System was unable to locate information for a PE in the Bulletin Board.
ACTION
Contact your TUXEDO System Technical Support.
mail: [email protected]

Office Web App error - unable to open PDF after multiple trials

Hi, we are using Office Web App server 2013 on win server 2012 (NO Sharepoint installed) to preview files (doc, docx, pdf, xls, xlsx, ppt, pptx), OWA is set as http, wopihost
is http as well under different from HTTP80, HTTP809 application pool
File conversion if fine for small files and large files to some point - we can process same large pdf (100MB) 30-50 times, but after that there is a message
"Sorry, Word Web App ran into
a problem opening this document. To view this document please open it in Microsoft Word."
Server has plenty of free space, PerfMon
does not show spikes, no memory spikes in Process Manager. ULS logs do not provide any good info either...
No errors in event log under Applications,
System, or Microsoft Office Web Apps sections.
That error will be shown if we process
the same file. if try to process different file it works fine (again - few dozen times), but if after that I try to process first file - it shows error again.
Documents
are located on the same server as OWA installed, same machine has wopi site in non owa application pool (from Microsoft demo
- C#)
The only resolution i found is to reset
WAC server from PowerShell or restart IIS - after that it starts to process original file...
If I just recycle OWA application pools
- HTTP80, HTTP809 it does not help. (tried to change Recycling condition in IIS for those pools - it slightly improves situation but does not resolve).
I can reproduce such pattern with different file types, it just matter of number of hits.
Same error present if we use OWA and wopi on machine as https with certificate.
We use VerboseEx option for logging - no errors in ULS log files, but multiple Sync exiting
early records similar to
Sync exiting early: LastSyncTime = 09/16/2014 14:52:07
at Microsoft.Office.Web.Apps.Environment.WacServer.ACacheableFarmStateObject.Sync(Boolean force)
at Microsoft.Office.Web.Apps.Environment.WacServer.AFarmSettings.TryGetSettingValue[T](String settingName,
T& value, Boolean shouldProcessValue)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSConfigAdapter.TryGetValue[T](String settingName,
T& value)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.GetAgentUri(WebAgentProperties
agentProperties, String machineName, String fqdn)
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.UpdateServiceList()
at Microsoft.Office.Web.Apps.Environment.WacServer.WSServiceInstanceFinderAdapter.FindAllServiceInstances()
at Microsoft.Office.Web.Common.ServiceInstanceFinder.RefreshList(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback
callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback,
Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
---------------------------------There are some paired records
Cached service list has 39 service instances before the update
Cached service lists has 39 service instances after the update
So it goes as follows: OWA processing all formats fine, after trying same 100mb pdf file 50 times (it is possible to get same error with docx, just bigger number of trials) it does not process that pdf file, but processes others.
After IIS reset it works as usual again. After trying another 100mb pdf file 50-60 times OWA stops to process that another file... We are expecting large number of hits and resetting IIS every 30min is not a good solution...
Any help will be appreciated.
Thank you

Hi ,
Thank you for your post.
Whether the issue occurs with different file types or only the PDF.
Based on your description, when you reset WAC server from PowerShell or restart IIS, the issue is solved temporarily.
I recommend that you check the application account, re-enter the account, then reset the IIS.
whether the issue occurs with different file types or only the PDF.
In addition, please check if the link is useful:
http://stevemannspath.blogspot.jp/2013/04/sharepoint-2013-pdf-support-and.html
Best Regards,
Lisa Chen

LIBTUX_CAT:582: ERROR: Unable to register, registry table full

When we tried to call one of our service 100 times parallely we got an error as :-
181936.547.MLXWTAIXDEV!GWWS.3568042.1.0: LIBTUX_CAT:582: ERROR: Unable to register, registry table full
182718.591.MLXWTAIXDEV!GWWS.10432990.1.0: LIBTUX_CAT:585: ERROR: Invalid registry table slot index passed, unable to unregister
Can somebody help us out why this error is coming.
The UBB configuration for same is as:-
MAXACCESSERS 350
MAXSERVERS 430
MAXSERVICES 1200
MAXGROUPS 100
MAXNETGROUPS 20
MAXMACHINES 256
MAXWSCLIENTS = 100
MAXACLCACHE = 10
MAXPENDINGBYTES = 100000
"TMMETADATA"
SRVGRP = "M_JOLT_GRP"
CLOPT = "-A -- -f /dev_app/dtux5/bin/reposfile"
RESTART= Y
SRVID = 1
GRACE = 3600
MAXGEN = 5
"GWWS"
SRVGRP = "M_JOLT_GRP"
CLOPT = "-A -- -iGWWS1"
RESTART= Y
SRVID = 2
The wsdf file is as
<Definition
xmlns="http://www.bea.com/Tuxedo/WSDF/2007"
name="EBATEST" wsdlNamespace="urn:salt.EBATEST.wsdl">
<WSBinding id="CURTEST_Binding">
<SOAP>
<AccessingPoints>
<Endpoint
address="http://10.16.114.145:7001/ebaapp" id="eba_HTTP_IN">
</Endpoint>
</AccessingPoints>
</SOAP>
<Servicegroup id="ebatestGrp">
<Service name="SCD_GET_TRD_UND"></Service>
</Servicegroup>
</WSBinding>
</Definition>
And salt file used for making saltconfig is as
<Deployment xmlns="http://www.bea.com/Tuxedo/SALTDEPLOY/2007">
<WSDF>
<Import location="/dev_app/dtux5/bin/example.wsdf"></Import>
</WSDF>
<WSGateway>
<GWInstance id="GWWS1">
<Inbound>
<Binding ref="EBATEST:CURTEST_Binding">
<Endpoint use="eba_HTTP_IN"></Endpoint>
</Binding>
</Inbound>
<Properties>
<Property name="enableSOAPValidation" value="true"/>
</Properties>
</GWInstance>
</WSGateway>
<System></System>
</Deployment>
The trace file as generated is as :-
184541.717.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A HTTP message is received, SCO index=4095
184541.717.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A SOAP message is received, SCO index=4095
184541.717.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184541.718.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184541.722.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281396]
184541.723.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x1: SESSION: TIMEOUT VALUE IS [9999]:
184541.727.MLXWTAIXDEV!svr_errlog.11956518.1.0: User id :mamu2:
184541.727.MLXWTAIXDEV!svr_errlog.11956518.1.0: Sssn id :281396:
184541.727.MLXWTAIXDEV!svr_errlog.11956518.1.0: Business id :B21001:
184541.727.MLXWTAIXDEV!svr_errlog.11956518.1.0: Business msg :Invalid User:The Login Id entered is not valid
184541.727.MLXWTAIXDEV!svr_errlog.11956518.1.0: Service Name :SVC_SESSION
184541.727.MLXWTAIXDEV!svr_session.11043070.1.0: No Data in Session table for :mamu2:, :281396:
184541.728.MLXWTAIXDEV!GWWS.2277636.1.0: GWWS_CAT:21: WARNING: Tuxedo service returns TPFAIL.
184541.729.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Send a http message to net, SCO index=4095
184700.521.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A HTTP message is received, SCO index=4095
184700.521.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A SOAP message is received, SCO index=4095
184700.521.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184700.522.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184700.522.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184700.523.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x2: SESSION: TIMEOUT VALUE IS [9999]:
184700.524.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x2: SESSION: SESSION [281397] IS VALID:
184700.538.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184700.538.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.691.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.691.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.691.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.692.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.693.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x3: SESSION: TIMEOUT VALUE IS [9999]:
184707.694.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x3: SESSION: SESSION [281397] IS VALID:
184707.710.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.711.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.718.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.718.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.718.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.718.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.718.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.719.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x4: SESSION: TIMEOUT VALUE IS [9999]:
184707.719.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x4: SESSION: SESSION [281397] IS VALID:
184707.732.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.732.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.738.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.738.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.739.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.739.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.739.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.739.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x5: SESSION: TIMEOUT VALUE IS [9999]:
184707.740.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x5: SESSION: SESSION [281397] IS VALID:
184707.756.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.756.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.769.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.769.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.769.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.769.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.770.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.770.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x6: SESSION: TIMEOUT VALUE IS [9999]:
184707.771.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x6: SESSION: SESSION [281397] IS VALID:
184707.798.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.799.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.807.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.807.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.807.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.807.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.807.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.808.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x7: SESSION: TIMEOUT VALUE IS [9999]:
184707.808.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x7: SESSION: SESSION [281397] IS VALID:
184707.821.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.821.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.831.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.831.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.831.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.831.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.831.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.832.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x8: SESSION: TIMEOUT VALUE IS [9999]:
184707.832.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x8: SESSION: SESSION [281397] IS VALID:
184707.843.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.843.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.855.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.855.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.855.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.855.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.856.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.856.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x9: SESSION: TIMEOUT VALUE IS [9999]:
184707.857.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af x9: SESSION: SESSION [281397] IS VALID:
184707.869.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.869.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.876.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.876.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.876.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.876.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.876.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.877.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xa: SESSION: TIMEOUT VALUE IS [9999]:
184707.877.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xa: SESSION: SESSION [281397] IS VALID:
184707.899.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.899.MLXWTAIXDEV!GWWS.2277636.1291.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.906.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.906.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.906.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.907.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.907.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.907.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xb: SESSION: TIMEOUT VALUE IS [9999]:
184707.908.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xb: SESSION: SESSION [281397] IS VALID:
184707.918.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.919.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.932.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.932.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.932.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.932.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.932.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.933.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xc: SESSION: TIMEOUT VALUE IS [9999]:
184707.933.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xc: SESSION: SESSION [281397] IS VALID:
184707.945.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.945.MLXWTAIXDEV!GWWS.2277636.1034.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.957.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.957.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.957.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.957.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.957.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
184707.958.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xd: SESSION: TIMEOUT VALUE IS [9999]:
184707.958.MLXWTAIXDEV!svr_session.11043070.1.0: gtrid x0 x4f1968af xd: SESSION: SESSION [281397] IS VALID:
184707.973.MLXWTAIXDEV!GWWS.2277636.1.0: LIBTUX_CAT:585: ERROR: Invalid registry table slot index passed, unable to unregister
184707.973.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Got a message from Tuxedo, SCO index=4095
184707.973.MLXWTAIXDEV!GWWS.2277636.1548.0: TRACE:ms:Send a http message to net, SCO index=4095
184707.980.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A HTTP message is received, SCO index=4095
184707.980.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:A SOAP message is received, SCO index=4095
184707.980.MLXWTAIXDEV!GWWS.2277636.777.0: TRACE:ms:Begin data transformation of request message, buffer type = FML32, SCO index=4095
184707.980.MLXWTAIXDEV!GWWS.2277636.1.0: TRACE:ms:Delivering a message to Tuxedo, service name =SCD_GET_TRD_UND, SCO index=4095
184707.980.MLXWTAIXDEV!svr_session.11043070.1.0: SESS: INPUT IS [mamu2] : [281397]
Regards,
Anurag

Hi,
From the Tuxedo documentation, LIBTUX_CAT:582 is described as follows along with a recommended action.
>
582
ERROR: Unable to register, registry table full
Description
The BEA TUXEDO system was attempting to find a registry table slot for a process, but the registry table was full.
Action
Increase the MAXACCESSERS parameter in the UBBCONFIG file, rebuild the TUXCONFIG file, then reboot the application and try again.
>
So try increassing MAXACCESSERS and see if your problem goes away.
Regards,
Todd Little
Oracle Tuxedo Chief Architect

LIBTUX_CAT:681: ERROR: Failure to create message queue

I am getting the following error while starting PeopleSoft Application server for demo data base on Oracle Enterprise Linux 5.5 64 bit.
Can someone please help me what am I doing wrong here?
075417.localhost.localdomain!PSANALYTICSRV.4065.3909714272.0: LIBTUX_CAT:262: INFO: Standard main starting
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: 11-19-2010: Tuxedo Version 10.3.0.0, 64-bit
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:681: ERROR: Failure to create message queue
075418.localhost.localdomain!PSRENSRV.4072.491399232.-2: LIBTUX_CAT:248: ERROR: System init function failed, Uunixerr = : msgget: No such file or directory
075418.localhost.localdomain!tmboot.4023.3569636960.-2: CMDTUX_CAT:825: ERROR: Process PSRENSRV at localhost.localdomain failed with /T tperrno (TPEOS - operating system error)
075418.localhost.localdomain!tmboot.4023.3569636960.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
075422.localhost.localdomain!BBL.4020.2558671968.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
075425.localhost.localdomain!PSADMIN.4014: End boot attempt on domain fdmo91

Never mind, I changed the kernel.msgmni to 1024, rebooted the server and then it started just fine.

How to resolve - LIBTUX_CAT:4053: ERROR: Routing function failed - error ?

Hi,
We are using TUX 8.1 and i am getting the error :
LIBTUX_CAT:4053: ERROR: Routing function failed
while invoking a tpforward call.
My ubb file for the new service is below.
"NewXXInqu"
LOAD=50 PRIO=50
BUFTYPE="ALL"
ROUTING="PARTITION"
TRANTIME=90
AUTOTRAN=N
DEFAULT: LOAD=50 PRIO=50 BUFTYPE="ALL" AUTOTRAN=N
*ROUTING
"PARTITION"
FIELD="PARTITION_ID"
BUFTYPE="FML32"
RANGES="1:P1,2:P2"
Its also giving the error : GP_CAT:1064: ERROR: Routing field for 'NewXXInqu' null.
LIBTUX_CAT:1401: WARN: tpforward tpacall failure TPESYSTEM - internal system error
I have the NewXXInqu object file created,which is linked to NewXXSvr. This server NewXXSvr is up and running, and i can see that using ps -ef.
can any one please tell me what is that im missing here. What does routing field 'xx' null mean ?
Even if i invoke my new service directly, it is giving the same error :GP_CAT:1064: ERROR: Routing field for'xxx' null,
LIBTUX_CAT:4053: ERROR: Routing function failed.
Appreciate your reply,
thanks,
gopi.

Hi,
i am using tuxedo 9.1 and i am getting the same error:
tpacall("PP_GA_RECARGA3", 0x0x8088140, 140, 0x0)
GP_CAT:1064: ERROR: Routing field for 'PP_GA_RECARGA3' null
LIBTUX_CAT:4053: ERROR: Routing function failed
tpacall = -1 [tperrno TPESYSTEM]
tpabort(0x0)
My ubb file for the service is belong:
*SERVICES
PP_GA_RECARGA3
LOAD=50 PRIO=50
BUFTYPE="ALL"
TRANTIME=30
AUTOTRAN=Y
SVCTIMEOUT=60
ROUTING=snum_telefono
*ROUTING
snum_telefono
FIELD=__routing__
RANGES="0:GRP_PPGA_00,1:GRP_PPGA_01"
BUFTYPE="FML32"
The service define is:
PP_GA_RECARGA3_snum_telefono 443 string - -
PP_GA_RECARGA3_stipo_recarga 444 string - -
PP_GA_RECARGA3_fimp_recarga 445 double - -
PP_GA_RECARGA3_scod_moneda 446 string - -
PP_GA_RECARGA3_scod_promocion 447 string - -
PP_GA_RECARGA3_scod_usuario 448 string - -
PP_GA_RECARGA3_lper_validez 449 long - -
PP_GA_RECARGA3_ssec_actuacion 450 string - -
PP_GA_RECARGA3__rpr_ret 451 long - -
If i invoke the service in other environment with similar configuration, the ulog show this:
tpacall("PP_GA_RECARGA3", 0x0x80882d8, 140, 0x0)
tpacall = 64 [CLIENTID {1280130829, 0, 430}]
tpservice({"PP_GA_RECARGA3", 0x10, 0x0x814a4f0, 1164, 0, 0, {1280130829, 0, 430}})
tpalloc("FML32", "", 1024)
All it's right
The difference is that one it's over vmware.
Does anyone know if this can influence in the routing?
Thanks,
Paula.

LIBTUX_CAT:305 error

Hi ,
The BBL is not getting executed and gives a failure . I am getting the follwing
error in the ULOG
061148.babbage!BBL.774.1.0: LIBTUX_CAT:350: ERROR: Configuration file parameters
do not match existing bulletin board.
061148.babbage!BBL.774.1.0: LIBTUX_CAT:248: ERROR: System init function failed,
Uunixerr =
061148.babbage!tmboot.713.1.-2: 05-01-2004: Tuxedo Version 8.1, 64-bit
061148.babbage!tmboot.713.1.-2: CMDTUX_CAT:825: ERROR: Process BBL at babbage
failed with /T tperrno (TPESYSTEM - internal system error)
I started getting this error when i updated the license file with a new license
. The config file was the same before updation and after updation .
Any pointers would be really helpful .
Thanks in advance,
Arati,

Hi Roopesh ,
Thanks for the tips . Changing the value of IPCKEY to smthg else has solved the
problem .
Thanks,
Arati
"roopesh" <[email protected]> wrote:
>
Check if the same IPCKEY is not being used by an existing doamin and
env variable
TUXCONFIG parameter is pointing same file as defined in the ubbconfig
file.
"aphadke" <[email protected]> wrote:
Hi ,
The BBL is not getting executed and gives a failure . I am getting the
follwing
error in the ULOG
061148.babbage!BBL.774.1.0: LIBTUX_CAT:350: ERROR: Configuration file
parameters
do not match existing bulletin board.
061148.babbage!BBL.774.1.0: LIBTUX_CAT:248: ERROR: System init function
failed,
Uunixerr =
061148.babbage!tmboot.713.1.-2: 05-01-2004: Tuxedo Version 8.1, 64-bit
061148.babbage!tmboot.713.1.-2: CMDTUX_CAT:825: ERROR: Process BBL at
babbage
failed with /T tperrno (TPESYSTEM - internal system error)
I started getting this error when i updated the license file with anew
license
The config file was the same before updation and after updation .
Any pointers would be really helpful .
Thanks in advance,
Arati,

LIBTUX_CAT:481: ERROR: Service xa_start returned -9

Hi All,
We are getting a typical XA error in one of our application environments every day.
I found the error message in ULOG and the message says :
"180502.mddev!XYZ.1867.1.0: gtrid x0 x49b925ce xa384: LIBTUX_CAT:481: ERROR: Service xa_start returned -9"
"XYZ" is one of the data logic service used in the application.
[ NOTE : XYZ is a duplicate name used for the actual server respecting the security policy of the customer]
After a bit of analysis I found in if the logs called xa_NULL03132009.trc , the below messages
150702.19343.0:
xaostart: xid=0x28-6d64646576000000000000000000000000000000000000000000000000000000000744f249b925ce00008c8e-000000
0100000008, rmid=0, flags=0x0
150702.19343.0:
ORA-24776: cannot start a new transaction
150702.19343.0:
xaostart: XAER_OUTSIDE; session in local transaction
Please guide me in resolving the issue and let me know what to do to resolve the issue.
It'll be great if I'll get some help as soon as possible.
Thanks,
Sandhya...

The XAER_OUTSIDE error can occur when a service that uses embedded SQL is sometimes invoked transactionally and is sometimes invoked nontransactionally.
When such a service is invoked nontransactionally, the first SQL statement executed within the service starts a SQL unit of work that is not associated with an XA transaction. If the service includes code "if (tpgetlev() == 0) EXEC SQL COMMIT WORK;" or "if (tpgetlev() == 0) EXEC SQL ROLLBACK WORK;" before invoking tpreturn() then future calls to this server within an XA transaction will work. However, if the non-XA SQL unit of work is not committed or rolled back before calling tpreturn() then any future calls to this server within an XA transaction will fail with XAER_OUTSIDE.
The easiest way to fix this problem is to use the Tuxedo AUTOTRAN parameter for all services within such servers. If the UBBCONFIG file includes the lines
*SERVICES
DEFAULT: AUTOTRAN=Y
then all services will have AUTOTRAN turned on by default. When a service configured with AUTOTRAN=Y is invoked, Tuxedo will start an XA transaction before just before invoking the service if not already in an XA service. If Tuxedo started an autotran transaction, then it will automatically commit or roll back the transcaction when tpreturn() is invoked.
Using AUTOTRAN avoids the need to call COMMIT WORK or ROLLBACK WORK in the application code before tpreturn() if tpgetlev()==0. (When tpgetlev() == 1 transactions are managed by XA and the application should not use any SQL COMMIT WORK or ROLLBACK WORK statements.)

LIBTUX_CAT:295: ERROR: _gwlog_open: _e_vtoc_tblopen: corrupted VTOC or different release

I am getting the following error in the ULOG file.
===================
165631.eclipse!GWADM.22003.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165631.eclipse!GWADM.22003.1.0: LIBTUX_CAT:295: ERROR: gwlogopen: evtoc_tblopen:
corrupted VTOC or different release
165631.eclipse!GWADM.22003.1.0: LIBGW_CAT:1042: ERROR: Can't open domain log
165631.eclipse!GWTDOMAIN.22004.1.0: 06-07-2003: Tuxedo Version 8.0
165631.eclipse!GWTDOMAIN.22004.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165631.eclipse!GWTDOMAIN.22004.1.0: LIBTUX_CAT:295: ERROR: gwlogopen: evtoc_tblopen:
corrupted VTOC or different release
165631.eclipse!GWTDOMAIN.22004.1.0: LIBGW_CAT:1042: ERROR: Can't open domain log
=========================
Also I tried to shutdown Tuxedo by doing tmshutdown -y, then the BBL process can
not be shutdown... and the message in ULOG is as follows:
==================================
192620.eclipse!WSH.22611.1.0: WSNAT_CAT:1042: ERROR: tpcall() call failed, tperrno
= 6
193242.eclipse!GWADM.22003.1.0: LIBGW_CAT:1036: ERROR: Can't locate free block
in domain log
193242.eclipse!DMADM.22002.1.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
193242.eclipse!WSL.22001.1.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation
for shutdown
193242.eclipse!WSL.22001.1.0: WSNAT_CAT:1197: INFO: Exiting system
==============================
I think it may be something wrong with our dmconfig, but do not know how to track
down?
Any help would be very much appreciated!
Ping

create the new devices devices and TLOGs.
are you using DMTLOGDEV in dmconfig ?
if you are not using transactions then remove all references to TLOGs and domain
transaction
logs and then try.
hope it helps
Roopesh
"Ping LI" <[email protected]> wrote:
>
I am getting the following error in the ULOG file.
===================
165631.eclipse!GWADM.22003.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165631.eclipse!GWADM.22003.1.0: LIBTUX_CAT:295: ERROR: gwlogopen: evtoc_tblopen:
corrupted VTOC or different release
165631.eclipse!GWADM.22003.1.0: LIBGW_CAT:1042: ERROR: Can't open domain
log
165631.eclipse!GWTDOMAIN.22004.1.0: 06-07-2003: Tuxedo Version 8.0
165631.eclipse!GWTDOMAIN.22004.1.0: LIBTUX_CAT:262: INFO: Standard main
starting
165631.eclipse!GWTDOMAIN.22004.1.0: LIBTUX_CAT:295: ERROR: gwlogopen:
evtoc_tblopen:
corrupted VTOC or different release
165631.eclipse!GWTDOMAIN.22004.1.0: LIBGW_CAT:1042: ERROR: Can't open
domain log
=========================
Also I tried to shutdown Tuxedo by doing tmshutdown -y, then the BBL
process can
not be shutdown... and the message in ULOG is as follows:
==================================
192620.eclipse!WSH.22611.1.0: WSNAT_CAT:1042: ERROR: tpcall() call failed,
tperrno
= 6
193242.eclipse!GWADM.22003.1.0: LIBGW_CAT:1036: ERROR: Can't locate free
block
in domain log
193242.eclipse!DMADM.22002.1.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
193242.eclipse!WSL.22001.1.0: WSNAT_CAT:1196: INFO: Terminating handlers
in preparation
for shutdown
193242.eclipse!WSL.22001.1.0: WSNAT_CAT:1197: INFO: Exiting system
==============================
I think it may be something wrong with our dmconfig, but do not know
how to track
down?
Any help would be very much appreciated!
Ping

LIBTUX_CAT:1286: ERROR: tpreturn could not send reply TPEOS

Hi,
Our application uses tuxedo for loadbalancing. we are using this from last 4 years, but today i'm getting one error with one scenario. As per my understading tpreturn call is failing. ULOG file shows below given message
032615.ocpdev1!BBL.14797.1.0: LIBTUX_CAT:216: WARN: Process 18711 died; removing from BB
032813.ocpdev1!issueHolders.18634.1.0: ERROR: msgsnd err:(LIBTUX_CAT:669: ERROR: Message operation failed because of the invalid message queue identifier) er
rno=22,qid=188425,buf=-9223372026643562600,bytes=293,flag=2048
032813.ocpdev1!issueHolders.18634.1.0: LIBTUX_CAT:1286: ERROR: tpreturn could not send reply TPEOS - operating system error
I have searched google pages and couldn't get any clue. I have tried modifying UBB Config file with SYSTEM_ACCESS parameter to PROTECTED and other parameters but no use.
Please let me know what can be done.

Hi,
I think you are referring to the documentation for error LIBTUX_CAT:1286, which suggests tuning the kernel parameters as a more general solution. The explanation for LIBTUX_CAT:669 is more specific (earlier messages in the ULOG usually give a more specific reason for the problem):
+669 ERROR: Message operation failed because of the invalid message queue identifier+
Description
msgsnd to a queue failed because of invalid message queue identifier. This can also occur if a request is made by a client who exits before the request is satisfied. The cleanup after the client exits removes the message queue.
Action
Check the message queue identifier in msgsnd(). The message may be corrupted. Contact your ORACLE TUXEDO system Technical Support.
Increasing the kernel parameters will not help in this case, as the problem is due to the queue having been removed, which happens when the client program terminates, and it is quite likely that there will be no messages in the ULOG indicating what happened. You will need to follow the suggestions made earlier in this forum thread and find out what happened to the client.
Regards,
Malcolm.

LIBTUX_CAT:334: ERROR: No BBL

Hi,
I'm new to Tuxedo
I'm using solaris 10 as my server.
Whenever i try to run tmboot it give me some error. The snapshot of the ULOG file is
150956.blwebplsun!BBL.18596.1.0: 03-23-2007: Tuxedo Version 9.1, 32-bit, Patch L
evel (none)
150956.blwebplsun!BBL.18596.1.0: LIBTUX_CAT:334: ERROR: No BBL
150956.blwebplsun!BBL.18596.1.0: LIBTUX_CAT:248: ERROR: System init function fai
led, Uunixerr =
150956.blwebplsun!tmboot.18595.1.-2: 03-23-2007: Tuxedo Version 9.1, 32-bit
150956.blwebplsun!tmboot.18595.1.-2: WARN: No BBL available on site blwebplsun.
Will not attempt to boot server processes on that site.
Please help me out to fix this problem.
Thanks and Regards,
Abhijit.

Dear JR.
My UBB File is
DOMAINID     "SIMPAPP"
MASTER          "simple"
UID          106
GID          101
MAXACCESSERS     21
MAXSERVERS     5
MAXSERVICES     10
MODEL          SHM
LDBAL          Y
*MACHINES
DEFAULT:
          APPDIR="/home/texuser/atmi"
          TUXCONFIG="/home/texuser/atmi/tuxconfig"
          TUXDIR="/opt/bea/tuxedo9.1"
#Example:
#          APPDIR="/home/me/simpapp"
#          TUXCONFIG="/home/me/simpapp/tuxconfig"
#          TUXDIR="/usr/tuxedo"
blwebplsun     LMID=simple MAXWSCLIENTS=6
#Example:
#beatux          LMID=blwebplsun
*GROUPS
GROUP1
     LMID=simple     GRPNO=1     OPENINFO=NONE
WSGRP GRPNO=GROUP1 LMID=SITE1
*SERVERS
DEFAULT:
          WSL SRVGRP="GROUP1" SRVID=1000 RESTART=Y GRACE=0
          CLOPT="-A -- -n //10.25.118.45:5120 -K both"
          #CLOPT="-A"
simpserv     SRVGRP=GROUP1 SRVID=1 MIN=1 MAX=5
          #WSL SRVGRP="GROUP1" SRVID=1000 RESTART=Y GRACE=0
          CLOPT="-A -p 1,30:5,1"
          RQADDR="QUEUE1" REPLYQ=Y
*SERVICES
TOUPPER
AND THE WNSADDR IS given as 10.25.118.45
thanks and regards ...

LIBTUX_CAT:776: ERROR: Invalid server information given

Hello:
I am getting the above error, and I would like to find out what conditions this behavior occurrs. I don't know of an API that takes rlink as an arguement or a TMID.
david

Arul,
The -9 error from xa_start() is XAER_OUTSIDE, which occurs when "The
resource manager is doing work outside any global transaction on behalf of
the application."
Tuxedo servers associated with a resource manager (database) should let
Tuxedo handle transaction management, and should normally not include any
SQL trasnsaction management statements such as EXEC SQL BEGIN WORK, EXEC SQL
COMMIT WORK, or EXEC SQL ROLLBACK WORK.
If a server is sometimes invoked in transaction mode and is sometimes
invoked outside of a transaction, if the server uses EXEC SQL BEGIN WORK
when it is invoked outside of a transaction, if there is sometimes no
matching EXEC SQL COMMIT WORK or EXEC SQL ROLLBACK work for the BEGIN WORK,
and if the server is called within a Tuxedo tranasaction after such an
unmatched BEGIN WORK, then the XAER_OUTSIDE error will occur.
I'd recommend looking at the code for your server to see if there are any
BEGIN WORK, COMMIT WORK, or ROLLBACK WORK statements, and especially if
there are any unmatched BEGIN WORK statements. A server invoked outside of
a transaction can replace such statements with tpbegin(), tpcommit(), and
tpabort(), and if tpreturn() detects an unmatched tpbegin() in such a
situation, it will log LIBTUX_CAT:1397 and fail the service request with
TPESVCERR.
<Arulraj S> wrote in message news:[email protected]...
Hi ,
I am using Tuxedo 8.1 along with oracle 9i
(ORACLE XA: Version 9.2.0.1.0. RM name = 'Oracle_XA'.)
getting the below error from an application server - randomly whenservices are fired from a java application to this qrsBBF - a c++ tuxedo
based app. server.
>
155336.seidevas09!qrsBBF.26884.1.0: gtrid x0 x43e13636 x3bc1:LIBTUX_CAT:1384: ERROR: xa_start flags 0 returned -9
>
Could any one of you tell me how I can fix this - this is very random .
is there anything to do with oracle ptaches/shared pool.
there are lot of schemas in one instance of db. and my application sharesthe schema with other java appls(using jdbc ,weblogic).
>
thanks
Arul
[email protected]

LIBTUX_CAT:489: ERROR: Performed tpreturn() with outstanding replies

Hi all,
We have three asynchronous call (tpacall with flags TPNOTRAN).
Service A:
tpacall(TPNOTRAN) Service B -> tpcall Service X
tpacall(TPNOTRAN) Service C -> tpcall Service Y
tpacall(TPNOTRAN) Service D -> tpcall Service C
If one call returns fails, we use tpcancel for the other services, but in the ULOG we can see:
LIBTUX_CAT:489: ERROR: Performed tpreturn() with outstanding replies
It is possible to know what are the outstanding replies?
Thanks in advanced

Hi,
I think you are referring to the documentation for error LIBTUX_CAT:1286, which suggests tuning the kernel parameters as a more general solution. The explanation for LIBTUX_CAT:669 is more specific (earlier messages in the ULOG usually give a more specific reason for the problem):
+669 ERROR: Message operation failed because of the invalid message queue identifier+
Description
msgsnd to a queue failed because of invalid message queue identifier. This can also occur if a request is made by a client who exits before the request is satisfied. The cleanup after the client exits removes the message queue.
Action
Check the message queue identifier in msgsnd(). The message may be corrupted. Contact your ORACLE TUXEDO system Technical Support.
Increasing the kernel parameters will not help in this case, as the problem is due to the queue having been removed, which happens when the client program terminates, and it is quite likely that there will be no messages in the ULOG indicating what happened. You will need to follow the suggestions made earlier in this forum thread and find out what happened to the client.
Regards,
Malcolm.

LIBTUX_CAT:1367: ERROR: Expired TUXEDO System Binary License

Hi,
I get the following error in ULOG file
LIBTUX_CAT:1367: ERROR: Expired TUXEDO System Binary License
when i start a server.
eventhough we have Oct 01 2002 expiration date in the license. It was working
until yesterday.
Thanks,
Srinivas

do youhave your lic.txt file in $TUXDIR/udataobj? If not then Tux cannot see it.
Matt <[email protected]> wrote:
Hi,
when calling tmadmin in order to obtain the amount of currently connected
clients the following error did occur: 170058.cmsaptapp2!tmadmin.55880.1.-2:
LIBTUX_CAT:1367: ERROR: Expired TUXEDO System Binary License
I am using a 1,000,000 user license with no expiration. MAXACCESSERS
is set to 6,000, MAXWSCLIENTS is set to 4,000.
Thanks
Matt

Proc.17086.1.-2: LIBTUX_CAT:6274: ERROR: TMNOTHREADS set to yes but multipl

Similar Messages

Maybe you are looking for