Bea.jolt.JoltRemoteService.decodeCALL()

I am trying to make a call to the TUX service via JOLT. The servers are running
in Sun Solaris E10K box. When I make a call to the function, call of JoltRemoteService
class , I am getting the following exception.
Can anyone help me to fix this issue?
Exception in thread "main" bea.jolt.ServiceException: bea.jolt.JoltRemoteService
(SFSODRP).decodeCALL()
bea.jolt.MessageException: bea.jolt.BufException: java.io.UTFDataFormatException
at java.lang.Throwable.fillInStackTrace(Native Method)
at java.lang.Throwable.fillInStackTrace(Compiled Code)
at java.lang.Throwable.<init>(Compiled Code)
at java.lang.Exception.<init>(Exception.java:42)
at java.lang.RuntimeException.<init>(RuntimeException.java:47)
at bea.jolt.JoltException.<init>(JoltException.java:58)
at bea.jolt.ServiceException.<init>(ServiceException.java:37)
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:412)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:307)
at XXCallTux.callService(XXCallTux.java:42)
at XXDrpDTran.getData(XXDrpDTran.java:68)
at drpdeptest.main(drpdeptest.java:27)
thanks
ram

Hi Ajay,
Please see my response to your other post.
Regards,
Todd Little
BEA Tuxedo Chief Architect

Similar Messages

Bea.jolt.ServiceException: TPENOENT - no entry found

Hi,
I am getting this error.Also find the ULOG contents pasted below.
D:\bea\tuxedo9.1\samples\jolt\ToUpper>java ToUpper
Authentication Level set To :0
Exception caught error no is:6
bea.jolt.ServiceException: TPENOENT - no entry found
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:460)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:345)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:267)
at ToUpper.main(ToUpper.java:39)
I have checked the jrepository file and also the Applet window for the service defination(TOUPPER)but still its not recognizing the service.Is there some configuration thing I have missed out before running JOLT client.
ULOG File Contents
132947.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1197: INFO: Exiting system
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
132956.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1197: "INFO: Exiting system"
132956.GVC3ZA03TESTING!DMADM.5844.5348.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
132959.GVC3ZA03TESTING!BBL.3216.4372.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
133028.GVC3ZA03TESTING!BBL.6140.5124.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
133028.GVC3ZA03TESTING!BBL.6140.5124.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
133028.GVC3ZA03TESTING!JSL.5608.6088.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!JSL.5608.6088.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!JSL.5608.6088.0: INFO: JOLT Listener version-BEA Jolt 9.1
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: INFO: JOLT Handler version-BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Current version: BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
133029.GVC3ZA03TESTING!WSL.3292.4892.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSL.3292.4892.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!WSH.2568.3772.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.2568.3772.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133029.GVC3ZA03TESTING!WSH.5764.3836.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.5764.3836.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133242.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133359.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133456.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid32(ACCOUNT_ID) failed for INQUIRY: LIBFML_CAT:8: ERROR: Unknown field name. Maybe FIELDTBLS32 is not set properly.
133612.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
143325.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid(SAMOUNT) failed for DEPOSIT: LIBFML_CAT:11: ERROR: Cannot find or open field table. Maybe FIELDTBLS is not set properly.
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1197: INFO: Exiting system
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144116.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1197: "INFO: Exiting system"
144116.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144119.GVC3ZA03TESTING!BBL.6140.5124.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144148.GVC3ZA03TESTING!BBL.4144.4376.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144148.GVC3ZA03TESTING!BBL.4144.4376.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144148.GVC3ZA03TESTING!JSL.5072.2444.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSL.5072.2444.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JSL.5072.2444.0: INFO: JOLT Listener version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Current version: BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144148.GVC3ZA03TESTING!WSL.3040.5488.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSL.3040.5488.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!WSH.5740.2764.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.5740.2764.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144148.GVC3ZA03TESTING!WSH.1784.5448.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.1784.5448.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144157.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144207.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144226.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144229.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1197: INFO: Exiting system
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144518.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1197: "INFO: Exiting system"
144519.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144522.GVC3ZA03TESTING!BBL.4144.4376.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144543.GVC3ZA03TESTING!BBL.5440.4548.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144543.GVC3ZA03TESTING!BBL.5440.4548.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144543.GVC3ZA03TESTING!JSL.1796.5232.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSL.1796.5232.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JSL.1796.5232.0: INFO: JOLT Listener version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Current version: BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144543.GVC3ZA03TESTING!WSL.2596.4404.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSL.2596.4404.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!WSH.3508.5136.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.3508.5136.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144543.GVC3ZA03TESTING!WSH.4288.5676.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.4288.5676.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144548.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144634.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144734.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"

Hi Ajay,
Please see my response to your other post.
Regards,
Todd Little
BEA Tuxedo Chief Architect

Bea.jolt.ServiceException:- TPETRAN - error starting transaction

I configured the simpapp application (I have pasted the ubb config below)
And i got the following error at the jolt client end:
bea.jolt.ServiceException:- TPETRAN - error starting transaction
At tuxedo end, i'm getting this in the log
160304.blrgislin42!JSH.24963.2696928160.-2: gtrid x0 x499be280 x1: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 14"
How can I resolve this issue?
here is the ubbsimple file::
RESOURCES+
IPCKEY 123456*
DOMAINID simpapp*
MASTER simple*
MAXACCESSERS 10*
MAXSERVERS 10*
MAXSERVICES 15*
MODEL SHM*
LDBAL N*
MACHINES+
DEFAULT:*
TUXDIR="/ais_local/share/ankumar/BEA/tuxedo8.1/"*
APPDIR="/ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp"*
TUXCONFIG="/ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp/tuxconfig"*
MAXWSCLIENTS=5*
+"XXXXXXX" LMID=simple+
GROUPS+
GROUP1*
LMID=simple GRPNO=1 OPENINFO=NONE*
JSLGRP*
LMID=simple GRPNO=2 OPENINFO=NONE*
SERVERS+
DEFAULT:*
CLOPT="-A"*
simpserv SRVGRP=GROUP1 SRVID=1*
JSL SRVGRP=JSLGRP SRVID=2 RESTART=Y MAXGEN=2 CLOPT="-A -- -n//xx.xx.xx.xx:3051"*
JREPSVR SRVGRP=JSLGRP SRVID=3 RESTART=Y MAXGEN=2 GRACE=0 CLOPT="-A -- -W -P /ais_local/share/ankumar/BEA/tuxedo8.1/udataobj/jolt/repository/jrepository"*
SERVICES+
DEFAULT: AUTOTRAN=Y TRANTIME=30*
TOUPPER*

Hi,
Thank you Malcolm and Todd for your replies.
Please help me resolve the issue.
I removed the AUTOTRAN option and I still get the error
bea.jolt.ServiceException: TPETRAN - error starting transaction
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:460)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:345)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:267)
@ tuxedo end, i get this error msg
!JSH.24293.2696928160.-2: gtrid x0 x499d214d x1: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 14"
Java client code:
JoltTransaction trans = null;
try {
trans = new JoltTransaction(0, jSessSync);
jServ.call(trans);
trans.commit();
catch(Exception e) {
trans.rollback();
log.logException("Caught exception in executeService(): ", e);
return(e.toString());
I also tried AUTOTRAn=Y option after configuring TLOG, but i still get the same error
TLOG
$ ./crtlog.sh -m
tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.
Echo now on.
crdl -b 500 -z /ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp/TLOG
Device created: /ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp/TLOG
crlog -m simple
crlog successfully completed.
q
crtlog.sh successful.
This is my current ubbsimple file::::::::::::::::::::::::
*RESOURCES
IPCKEY 123456
#Example:
#IPCKEY 123456
DOMAINID simpapp
MASTER simple
MAXACCESSERS 10
MAXSERVERS 10
MAXSERVICES 15
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
TUXDIR="/ais_local/share/ankumar/BEA/tuxedo8.1/"
APPDIR="/ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp"
TUXCONFIG="/ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp/tuxconfig"
TLOGDEVICE="/ais_local/share/ankumar/BEA/tuxedo8.1/apps/simpapp/TLOG"
TLOGNAME="TLOG"
MAXWSCLIENTS=5
#Example:
# APPDIR="/home/me/simpapp"
# TUXCONFIG="/home/me/simpapp/tuxconfig"
# TUXDIR="/usr/tuxedo"
"blrgislin42" LMID=simple
#Example:
#beatux LMID=simple
*GROUPS
GROUP1
LMID=simple GRPNO=1 OPENINFO=NONE
JSLGRP
LMID=simple GRPNO=2 OPENINFO=NONE
*SERVERS
DEFAULT:
CLOPT="-A"
simpserv SRVGRP=GROUP1 SRVID=1
JSL SRVGRP=JSLGRP SRVID=2 RESTART=Y MAXGEN=2 CLOPT="-A -- -n//10.11.23.66:3051"
JREPSVR SRVGRP=JSLGRP SRVID=3 RESTART=Y MAXGEN=2 GRACE=0 CLOPT="-A -- -W -P /ais_local/share/ankumar/BEA/tuxedo8.1/udataobj/jolt/repository/jrepository"
*SERVICES
TOUPPER
Am I missing anything? am i missing any parameter for JSL server?
I have another Tuxedo9.1 in which the bankapp was configured (by somebody years back) and i was able to run the withdrawal, inquiry services with the same client. not sure why its not working with TOUPPER service.
The simple C client (simpcl) works fine.
Please Advise.
I have whole lot of other doubts with subscribing to events. Will open a new thread for that.
Thanks,
Anish Kumar
Edited by: Bangalore_anish on Feb 19, 2009 2:23 AM
Edited by: Bangalore_anish on Feb 19, 2009 2:29 AM

Exception in thread "main" bea.jolt.ServiceException: Service is not availa

Hi All,
I'm new to Tuxedo. I've installed tuxedo. I've deployed simpapp given as sample. It's c clients and server are working fine. Now I'm trying to use Java client for the same server. In my office I need to work with Tuxedo9.1 and JOLT. When I'm trying to run I'm getting problem. I'm not able to find any solution. Please help me. I'm giving entire work done by me as follows.
Problem in Running Java Client with Tuxedo.
My ASCII tuxconfig file details:
# (c) 2003 BEA Systems, Inc. All Rights Reserved.
#eident "@(#) samples/atmi/simpapp/ubbsimple $Revision: 1.5 $"
#Skeleton UBBCONFIG file for the TUXEDO Simple Application.
#Replace the <bracketed> items with the appropriate values.
*RESOURCES
IPCKEY 123456
#Example:
#IPCKEY 123456
DOMAINID simpapp
MASTER simple
MAXACCESSERS 50
MAXSERVERS 30
MAXSERVICES 50
MODEL SHM
LDBAL N
*MACHINES
DEFAULT:
APPDIR="/shashi/mysimpleapp/simpapp"
TUXCONFIG="/shashi/mysimpleapp/simpapp/tuxconfig"
TUXDIR="/newutitux/newtux/tuxedo9.1"
#Example:
# APPDIR="/home/me/simpapp"
# TUXCONFIG="/home/me/simpapp/tuxconfig"
# TUXDIR="/usr/tuxedo"
systest LMID=simple MAXWSCLIENTS=4
#Example:
#beatux LMID=simple
*GROUPS
GROUP1
LMID=simple GRPNO=1 OPENINFO=NONE
JSLGROUP LMID=simple GRPNO=2 OPENINFO=NONE
JREPGROUP LMID=simple GRPNO=3 OPENINFO=NONE
*SERVERS
DEFAULT:
CLOPT="-A"
simpserv SRVGRP=GROUP1 SRVID=1
JSL SRVGRP=JSLGROUP SRVID=2
CLOPT=" -- -n //10.10.100.110:5000 -d /dev/tcp "
JREPSVR SRVGRP=JREPGROUP SRVID=4
CLOPT=" -- -W -P /shashi/mysimpleapp/simpapp/jrepository "
JRAD SRVGRP=JSLGROUP SRVID=3
CLOPT=" -- -l //10.10.100.110:5555 -c //10.10.100.110:5000 "
*SERVICES
TOUPPER
I've started the server using command tmboot -y.5 servers are started.
When I test using tmadmin command following is the output.
>psr
Prog Name Queue Name Grp Name ID RqDone Load Done Current Service
BBL 123456 simple 0 0 0 ( IDLE )
simpserv 00001.00001 GROUP1 1 0 0 ( IDLE )
JSL 00002.00002 JSLGROUP 2 0 0 ( IDLE )
JRAD 00002.00003 JSLGROUP 3 0 0 ( IDLE )
JREPSVR 00003.00004 JREPGRO+ 4 0 0 ( IDLE )
pscService Name Routine Name Prog Name Grp Name ID Machine # Done Status
TOUPPER TOUPPER simpserv GROUP1 1 simple 0 AVAIL
My Jrlyconfig file content is:-
LOGDIR=/shashi/mysimpleapp
ACCESS_LOG=access.log
ERROR_LOG=error.log
LISTEN=10.10.100.110:4444
CONNECT=10.10.100.110:5555
SOCKETTIMEOUT=30
and jrly is also running.
Content of jrepository file is:-
#!JOLT1.0^M
add SVC/TOUPPER:vs=1:ex=1:bt=STRING:\^M
bp:pn=STRING:pt=string:pf=167772161:pa=rw:ep:^M
add PKG/SIMPSERV:TOUPPER:^M
ULOG Message is:-
165446.systest!BBL.5691.1.0: 06-10-2010: Tuxedo Version 9.1, 64-bit, Patch Level (none)
165446.systest!BBL.5691.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165446.systest!simpserv.5692.1.0: 06-10-2010: Tuxedo Version 9.1, 64-bit
165446.systest!simpserv.5692.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165446.systest!simpserv.5692.1.0: Welcome to the simple server
165446.systest!JSL.5693.1.0: 06-10-2010: Tuxedo Version 9.1, 64-bit
165446.systest!JSL.5693.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165446.systest!JSL.5693.1.0: INFO: JOLT Listener version-BEA Jolt 9.1
165446.systest!JSL.5693.1.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2664953090480>, Expiration Date : <None>"
165446.systest!JSL.5693.1.0: JOLT_CAT:1564: "INFO: Licensee : <Customer>"
165446.systest!JREPSVR.5694.1.0: 06-10-2010: Tuxedo Version 9.1, 64-bit
165446.systest!JREPSVR.5694.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165446.systest!JREPSVR.5694.1.0: Current version: BEA Jolt 9.1
165446.systest!JREPSVR.5694.1.0: Repository "/shashi/mysimpleapp/simpapp/jrepository" (2 records) is writable.
165446.systest!JRAD.5695.1.0: 06-10-2010: Tuxedo Version 9.1, 64-bit
165446.systest!JRAD.5695.1.0: LIBTUX_CAT:262: INFO: Standard main starting
165446.systest!JRAD.5695.1.0: INFO: JRAD version-BEA Jolt 9.1
I don't find any problem in starting and running the system.
Problem faced:-
1.Repository Editor is connected to the system using port number given for jrly( i.e.. 4444) but it is giving an exception
"bea.jolt.ServiceException:Service is not available:.GETKEYS"
2.When trying to load bulk loader after setting jolt.jar and joltadmin.jar to the classpath it is giving the exception
java bea.jolt.admin.jbld //10.10.100.110:4444 services.txt
Exception in thread "main" bea.jolt.ServiceException: Service is not available:.GETKEYS
at bea.jolt.JoltRemoteService.init(JoltRemoteService.java:156)
at bea.jolt.JoltRemoteService.<init>(JoltRemoteService.java:112)
at bea.jolt.admin.JSvcPkgTbl.initTable(jbld.java:1010)
at bea.jolt.admin.JSvcPkgTbl.<init>(jbld.java:990)
at bea.jolt.admin.JBldDefRec.<init>(jbld.java:138)
at bea.jolt.admin.jbld.main(jbld.java:801)
Note:- I've tested on port number 5000 and file as jrepository also.The content of services.txt is as follows
service=TOUPPER
export=true
inbuf=STRING
outbuf=STRING
access=inout
3.While running the ToUpper.java given in sample it is giving the exception as follows.
"Exception in thread "main" bea.jolt.ServiceException: Service is not available:TOUPPER
at bea.jolt.JoltRemoteService.init(JoltRemoteService.java:156)
at bea.jolt.JoltRemoteService.<init>(JoltRemoteService.java:112)
at ToUpper.main(ToUpper.java:36)"
Content of ToUpper.java:-
/* Copyright 1996 BEA Systems, Inc. All Rights Reserved */
import bea.jolt.*;
public class ToUpper
public static void main (String[] args)
JoltSession session;
JoltSessionAttributes sattr;
JoltRemoteService toupper;
JoltTransaction trans;
String userName=null;
String userPassword=null;
String appPassword=null;
String userRole="myapp";
String outstr;
sattr = new JoltSessionAttributes();
sattr.setString(sattr.APPADDRESS, "//10.10.100.110:4444");
switch (sattr.checkAuthenticationLevel())
case JoltSessionAttributes.NOAUTH:
break;
case JoltSessionAttributes.APPASSWORD:
appPassword = "appPassword";
break;
case JoltSessionAttributes.USRPASSWORD:
userName = "myname";
userPassword = "mysecret";
appPassword = "appPassword";
break;
sattr.setInt(sattr.IDLETIMEOUT, 300);
session = new JoltSession(sattr, null, null,
null, null);
toupper = new JoltRemoteService ("TOUPPER", session);
toupper.setString("STRING", "hello world");
toupper.call(null);
outstr = toupper.getStringDef("STRING", null);
if (outstr != null)
System.out.println(outstr);
session.endSession();
System.exit(0);
} // end main
} // end ToUpper
Please help me. Thanks in Advance. Waiting for ASAP help.
Regards
Shashi Ranjan

Hi,
As per your suggestion I'm again giving the detail of all the files which I'm using.
tmboot -y output:-
Booting all admin and server processes in /home/oracle/simaapp/tuxconfig
INFO: Oracle Tuxedo, Version 11.1.1.1.0, 32-bit, Patch Level (none)
Booting admin processes ...
exec BBL -A :
     process id=6116 ... Started.
Booting server processes ...
exec TMUSREVT -- -f /home/oracle/simaapp/tmusrevt.dat :
     process id=6117 ... Started.
exec simpserv -A :
     process id=6118 ... Started.
exec JSL -- -n //station1.example.com:7000 -d /dev/tcp :
     process id=6119 ... Started.
exec JREPSVR -- -W -P /home/oracle/simaapp/jrepository :
     process id=6120 ... Started.
exec JRAD -- -l //station1.example.com:5555 -c //station1.example.com:7000 :
     process id=6121 ... Started.
6 processes started.
TMUSREVT.ENV content:-
FIELDTBLS=Usysflds; export FIELDTBLS
FLDTBLDIR=$TUXDIR/udataobj; export FLDTBLDIR
FIELDTBLS32=jrep.f32; export FIELDTBLS32;
FLDTBLDIR=$TUXDIR/udataobj; export FLDTBLDIR;
tux.env content:-
TUXDIR=/u01/tuxedo/tuxedo11gR1; export TUXDIR
JAVA_HOME=$TUXDIR/jre; export JAVA_HOME
JVMLIBS=$JAVA_HOME/lib/i386/server:$JAVA_HOME/jre/bin
PATH=$TUXDIR/bin:$JAVA_HOME/bin:$PATH; export PATH
COBCPY=:$TUXDIR/cobinclude; export COBCPY
COBOPT="-C ANS85 -C ALIGN=8 -C NOIBMCOMP -C TRUNC=ANSI -C OSEXT=cbl"; export COBOPT
SHLIB_PATH=$TUXDIR/lib:$JVMLIBS:$SHLIB_PATH; export SHLIB_PATH
LIBPATH=$TUXDIR/lib:$JVMLIBS:$LIBPATH; export LIBPATH
LD_LIBRARY_PATH=$TUXDIR/lib:$JVMLIBS:$LD_LIBRARY_PATH; export LD_LIBRARY_PATH
WEBJAVADIR=$TUXDIR/udataobj/webgui/java; export WEBJAVADIR
UBBCONFIG content:-
*RESOURCES
IPCKEY 78111
MASTER "station1"
UID 501
GID 501
PERM 0600
MAXACCESSERS 50
MAXACLGROUPS 16384
MAXGTT 100
DOMAINID "simpapp"
MAXGROUPS 100
MAXNETGROUPS 8
MAXMACHINES 256
MAXQUEUES 50
MAXDRT 0
MAXRFT 0
MAXRTDATA 4
MAXSPDATA 33924
MAXSERVERS 50
MAXSERVICES 100
MAXCONV 10
MODEL SHM
LDBAL Y
1,10 Top
CMTRET COMPLETE
MAXBUFTYPE 16
MAXBUFSTYPE 32
SCANUNIT 10
SANITYSCAN 12
DBBLWAIT 2
BBLQUERY 30
BLOCKTIME 6
NOTIFY DIPIN
SYSTEM_ACCESS FASTPATH
MAXINTERFACES 150
MAXOBJECTS 1000
SIGNATURE_AHEAD 3600
SIGNATURE_BEHIND 604800
USIGNAL SIGUSR2
*MACHINES
DEFAULT:
"station1.example.com" LMID="station1"
TUXCONFIG="/home/oracle/simaapp/tuxconfig"
TUXDIR="/u01/tuxedo/tuxedo11gR1"
APPDIR="/home/oracle/simaapp"
TLOGNAME="TLOG"
TLOGSIZE=100
CMPLIMIT="MAXLONG,MAXLONG"
NETLOAD=0
SPINCOUNT=0
MAXACLCACHE=100
MAXOBJECTS=1000
SICACHEENTRIESMAX="500"
MAXWSCLIENTS=4
*GROUPS
GROUP1
LMID=station1 GRPNO=1 OPENINFO=NONE
JSLGROUP LMID=station1 GRPNO=2 OPENINFO=NONE
JSRGROUP LMID=station1 GRPNO=3 OPENINFO=NONE
TMUGROUP LMID=station1 GRPNO=4 OPENINFO=NONE
TMUSREVTGROUP LMID=station1 GRPNO=5 OPENINFO=NONE
*NETGROUPS
*SERVERS
DEFAULT:
CLOPT="-A"
simpserv SRVGRP=GROUP1 SRVID=1
JSL SRVGRP=JSLGROUP SRVID=2
CLOPT=" -- -n //station1.example.com:7000 -d /dev/tcp "
JREPSVR SRVGRP=JSRGROUP SRVID=3
CLOPT=" -- -W -P /home/oracle/simaapp/jrepository "
JRAD SRVGRP=JSLGROUP SRVID=4
CLOPT=" -- -l //station1.example.com:5555 -c //station1.example.com:7000 "
TMUSREVT SRVGRP=TMUSREVTGROUP SRVID=5 GRACE=3600
ENVFILE="/home/oracle/simaapp/TMUSREVT.ENV"
CLOPT=" -- -f /home/oracle/simaapp/tmusrevt.dat "
SEQUENCE=11
*MODULES
*JDBCCONNPOOLS
*SERVICES
TOUPPER
LOAD=50 PRIO=50
BUFTYPE="ALL"
TRANTIME=30
AUTOTRAN=N
AFFINITYSCOPE=SERVER
*INTERFACES
*ROUTING
jrepository content:-
#!JOLT1.0
add SVC/TOUPPER:vs=1:ex=1:bt=STRING:\
bp:pn=STRING:pt=string:pf=167772161:pa=rw:ep:
add PKG/SIMPSERV:TOUPPER:
After exception the content of ULOG:-
175351.station1.example.com!BBL.6116.3086526144.0: 06-13-2010: client high water (0), total client (0)
175351.station1.example.com!BBL.6116.3086526144.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit, Patch Level (none)
175351.station1.example.com!BBL.6116.3086526144.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!TMUSREVT.6117.3086412000.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
175351.station1.example.com!TMUSREVT.6117.3086412000.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!simpserv.6118.3086706368.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
175351.station1.example.com!simpserv.6118.3086706368.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!simpserv.6118.3086706368.0: Welcome to the simple server
175351.station1.example.com!JSL.6119.3086870208.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
175351.station1.example.com!JSL.6119.3086870208.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!JSL.6119.3086870208.0: INFO: JOLT Listener version-Oracle Jolt 11.1.1.1.0
175351.station1.example.com!JREPSVR.6120.3086403264.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
175351.station1.example.com!JREPSVR.6120.3086403264.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!JREPSVR.6120.3086403264.0: Current version: Oracle Jolt 11.1.1.1.0
175351.station1.example.com!JREPSVR.6120.3086403264.0: Repository "/home/oracle/simaapp/jrepository" (2 records) is writable.
175351.station1.example.com!JRAD.6121.3086603968.0: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
175351.station1.example.com!JRAD.6121.3086603968.0: LIBTUX_CAT:262: INFO: Standard main starting
175351.station1.example.com!JRAD.6121.3086603968.0: INFO: JRAD version-Oracle Jolt 11.1.1.1.0
180656.station1.example.com!JRAD.6121.3086603968.0: JRAD_CAT:1526: INFO: JRLY connection is UP
180656.station1.example.com!JSH.6187.3086858464.-2: 06-13-2010: Tuxedo Version 11.1.1.1.0, 32-bit
180656.station1.example.com!JSH.6187.3086858464.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
180656.station1.example.com!JSH.6187.3086858464.-2: INFO: JOLT Handler version-Oracle Jolt 11.1.1.1.0
180657.station1.example.com!JSH.6187.3086858464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'oracle'; client name 'admin'"
Content of stderr:-
tpcall .GETREC failed: TPENOENT - no entry found
tpcall .GETREC failed: TPENOENT - no entry found
tpcall .GETREC failed: TPENOENT - no entry found
tpcall .GETREC failed: TPENOENT - no entry found
services.txt content
service=TOUPPER
export=true
inbuf=STRING
outbuf=STRING
access=inout
The content of jrlyconfig file:-
LOGDIR=/home/oracle/simaapp
ACCESS_LOG=access_log
ERROR_LOG=errorlog
LISTEN=station1.example.com:4444
CONNECT=station1.example.com:5555
then I'm running jrly -f jrlyconfig
The exception occurs when I run the command. "java bea.jolt.admin.jbld //station1:4444 services.txt"
Exception in thread "main" bea.jolt.ServiceException: Service is not available:.GETKEYS
     at bea.jolt.JoltRemoteService.init(JoltRemoteService.java:156)
     at bea.jolt.JoltRemoteService.<init>(JoltRemoteService.java:112)
     at bea.jolt.admin.JSvcPkgTbl.initTable(jbld.java:1010)
     at bea.jolt.admin.JSvcPkgTbl.<init>(jbld.java:990)
     at bea.jolt.admin.JBldDefRec.<init>(jbld.java:138)
     at bea.jolt.admin.jbld.main(jbld.java:801)
similarly when I'm trying to connect through RE.html
the exception is
bea.jolt.ServiceException: Service is not available:.GETKEYS
The output of command JREPSVR -v is
# List of services and corresponding handler functions built into the server
:ADDREC
:DELREC
:FLUSHCACHE
:GARBAGECOLLECT
.GETALL:GETALL
.GETKEYS:GETKEYS
.GETREC:GETREC
.GETSVC:GETSVC
:LOCKREP
.NUMRECS:NUMRECS
Regards,
Shashi Ranjan

Calling Tuxedo Service using BEA Jolt.

I'm trying to call Tuxedo service from java stored procedure using BEA JOLT.My normal java client works fine but when i use the same client as java stored procedure i get following error message :
can not connect to any //lucy:9021(host:port)
Reason:Nwhdlr:can not open socket
I've successfully loaded all required JOLT jar files using loadjava and created the procedure successfully .Java code is given below :
import bea.jolt.*;
import java.sql.*;
public class JoltToTux
     public static void callTuxService() throws Exception
          JoltSession session;
          JoltSessionAttributes sattr;
          JoltRemoteService toupper;
          JoltTransaction trans;
          String userName=null;
          String userPassword=null;
          String appPassword=null;
          String userRole=null;
          String outstr;
          try {
          sattr = new JoltSessionAttributes();
          sattr.setString(sattr.APPADDRESS, "//lucy:9021");
          sattr.setInt(sattr.IDLETIMEOUT, 300);
          session = new JoltSession(sattr, userName, userRole,userPassword, appPassword);
                    toupper = new JoltRemoteService ("CB_EXESUB", session);
          toupper.setString("CLFY_SUB", "PingSrvr");
          toupper.call(null);
          System.out.println( "Call to Tuxedo complete" );
          outstr = toupper.getStringDef("WF_MESSAGE","" );
          System.out.println("return string : " + outstr);
                    session.endSession();
          System.exit(0);
          } //end of try
          catch (Exception e) {
               // System.err.println(e.getMessage());}
               e.printStackTrace();
     } // end main
     public static void main( String args[] ) {
          try {
               JoltToTux jt = new JoltToTux();
               jt.callTuxService();
          catch ( Exception e0 ) {
               e0.printStackTrace();
} // end ToUpper
thanks
anurag

Ams,
You can't do that with JOLT. You will need to use the WTC product,
currently in beta - see WTC Questions and Answers
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.
Ams wrote:
Hi Manoj,
I want to call a tuxedo service and also want to update
database (using entity beabs) in same transaction so I
can't use AUTOTRAN , Am I right ?
I am using bea.jolt.pool.SessionPool's startTransaction
method to start a transaction and passing this
to SessionPool's call method.
Ams.
"Manoj SASIDHARAN" <[email protected]> wrote:
Hello Ams,
Could u plz give more information abt the usage scenario. Another way
to test
would be to put AUTOTRAN=Y for the service in question.
HTH
regards
MS
"Ams" <[email protected]> wrote:
Hi,
I am calling Tuxedo service from ejb using jolt.
I want the service call in transaction started in ejb.
I am getting following error.
LIBTUX_CAT:481: ERROR: Service xa_start returned -7
Does jolt support transaction ?
Ams
[att1.html]

Bea.jolt.ApplicationException:TPESVCFAIL-application level service failure

Hi All,
When I try to open PIA 3 tier I'm getting following error on webpage: "bea.jolt.ApplicationException: TPESVCFAIL - application level service failure".
Thanks and Regards,
Vineel.

This is a very generic error
See this doc for possible causes and resolutions.
E-AS: Master Note for "'bea.jolt.ApplicationException: TPESVCFAIL" Error [ID 1201223.1]
https://support.oracle.com/epmos/faces/DocContentDisplay?id=1201223.1

Bea.jolt.ServiceException: Invalid Session

Good day to all!
I know that this is common problem, but if you kindly point me in the right direction, that would be more appreciated. I am currently running PT8.50 HRMS 9.1 DMO on Windows 7. The PIA is giving this error:
CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ServiceException: Invalid Session
When logging in, I get that the app server is down. I am in familiar with why I see app server is down. I also believe that I understand why I am getting the above error. During installation, I put my own password for PTWEBSERVER as oppose to the default. I thought I updated the password with the default, but doesn't seem to work.
I also understand to check the appserver logs, but I am not familiar where it is located, so if 'I could get the location of these logs, I will post the log and that would confirm if it is a password issue, or not.
And if I need to uninstall and reinstall PIA, please tell me what I should do there. Thank you and Be Blessed

Thank you for that helpful tip. I misunderstood Bob's post then. I though the updating was only if the acct was locked (which it wasn't because I checked). In any rate, I did rerun the script and the script was successful. Just to be sure, I logged into datamover via bootstrap mode and just typed in exactly the command that was given. I didn't miss anything I am assuming correct?
I am still getting the same error message, even after updating the password. Here is the log, maybe this will help. Be Blessed
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "DefaultSecure[7]" is now listening on 0:0:0:0:0:0:0:1:443 for protocols iiops, t3s, ldaps, https.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "Default[4]" is now listening on fe80:0:0:0:0:100:7f:fffe:80 for protocols iiop, t3, ldap, snmp, http.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "Default[7]" is now listening on 0:0:0:0:0:0:0:1:80 for protocols iiop, t3, ldap, snmp, http.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "Default[3]" is now listening on fe80:0:0:0:1975:e9d2:ad58:81a3:80 for protocols iiop, t3, ldap, snmp, http.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "DefaultSecure" is now listening on 10.10.10.10:443 for protocols iiops, t3s, ldaps, https.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "DefaultSecure[5]" is now listening on fe80:0:0:0:741d:f596:ab4:94cd:443 for protocols iiops, t3s, ldaps, https.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "Default[5]" is now listening on fe80:0:0:0:741d:f596:ab4:94cd:80 for protocols iiop, t3, ldap, snmp, http.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <Server> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-002613> <Channel "Default[2]" is now listening on fe80:0:0:0:818a:caaf:319d:8d73:80 for protocols iiop, t3, ldap, snmp, http.>
####<Nov 17, 2010 12:55:52 PM CST> <Notice> <WebLogicServer> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152368> <BEA-000329> <Started WebLogic Admin Server "PIA" for domain "INNOVATI" running in Production Mode>
####<Nov 17, 2010 12:55:52 PM CST> <Warning> <Server> <Kelvin> <PIA> <DynamicSSLListenThread[DefaultSecure]> <<WLS Kernel>> <> <> <1290020152368> <BEA-002611> <Hostname "Kelvin", maps to multiple IP addresses: 10.10.10.10, fe80:0:0:0:ad0e:4847:e1ac:9d13%23>
####<Nov 17, 2010 12:55:52 PM CST> <Info> <EJB> <Kelvin> <PIA> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020152977> <BEA-010008> <EJB Deploying file: mejb.jar>
####<Nov 17, 2010 12:55:55 PM CST> <Notice> <WebLogicServer> <Kelvin> <PIA> <Main Thread> <<WLS Kernel>> <> <> <1290020155629> <BEA-000365> <Server state changed to RUNNING>
####<Nov 17, 2010 12:55:57 PM CST> <Notice> <WebLogicServer> <Kelvin> <PIA> <Main Thread> <<WLS Kernel>> <> <> <1290020157204> <BEA-000360> <Server started in RUNNING mode>
####<Nov 17, 2010 12:56:06 PM CST> <Info> <EJB> <Kelvin> <PIA> <[STANDBY] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1290020166611> <BEA-010009> <EJB Deployed EJB with JNDI name ejb.mgmt.MEJB.>
####<Nov 17, 2010 1:35:20 PM CST> <Info> <ServletContext-> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1290022520267> <BEA-000000> <ERROR: WebProfile loading internal default settings because of an Exception while communicating with "kelvin:9000">
####<Nov 17, 2010 1:35:33 PM CST> <Info> <ServletContext-> <Kelvin> <PIA> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1290022533121> <BEA-000000> <ERROR: WebProfile loading internal default settings because of an Exception while communicating with "kelvin:9000">
Edited by: 792295 on Nov 17, 2010 11:41 AM

Bea.jolt.pool.ServiceException: TPETRAN - error starting transaction

I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4.

I am ctreating the transaction object and try to operate PoolManager.call()
with the transaction object as parameter. The call fails with the following
exception:
bea.jolt.pool.ServiceException: TPETRAN - error starting transaction
at bea.jolt.pool.Connection.call(Connection.java, Compiled Code)
at bea.jolt.pool.SessionPool.call(SessionPool.java:412)
at bea.jolt.pool.SessionPool.call(SessionPool.java:211)
at
mcs.connectjolt.bandetails.BanDetailesDAO.getBanDetailes(BanDetailesDAO.java
:87)
at
mcs.connectjolt.bandetails.BanDetailsBean.getBanDetailes(BanDetailsBean.java
:68)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl.getBanDetailes(BanDetailsBea
nEOImpl.java:105)
at
mcs.connectjolt.bandetails.BanDetailsBeanEOImpl_WLSkel.invoke(BanDetailsBean
EOImpl_WLSkel.java:83)
at
weblogic.rmi.extensions.BasicServerObjectAdapter.invoke(BasicServerObjectAda
pter.java, Compiled Code)
at
weblogic.rmi.extensions.BasicRequestHandler.handleRequest(BasicRequestHandle
r.java:69)
at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:1
5)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java, Compiled
Code)
My configuration: WebLogic 5.1, Jolt 1.2, Tuxedo 6.4.

Configure a BEA Jolt connection pool

The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primary server at //10.0.0.7:8001'.
When is the reason?

Hi there!
You have to start Tuxedo JOLT servers at the same address of parameters
"appaddrlist", and if you have security implemetation you have to add those
parameters.
You should use Jolt 1.2 in tuxedo Application
Best Regards
Mauricio
"Chaang" <[email protected]> wrote in message
news:[email protected]..
The Jolt for Weblogic property in the property file is as follow :
eblogic.system.startupClass.demojoltpoolStart=\
bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
weblogic.system.startupArgs.demojoltpoolStart=\
poolname=demojoltpool,\
appaddrlist=//10.0.0.7:8001,\
failoverlist=//10.0.0.7:8005,\
minpoolsize=1,\
maxpoolsize=3
weblogic.system.shutdownClass.demojoltpoolStop=\
bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
weblogic.system.shutdownArgs.demojoltpoolStop=\
poolname=demojoltpool
I couldn't get it connected, a message said 'Unable to connect to primaryserver at file://10.0.0.7:8001'.
>
When is the reason?

Got 'bea.jolt.ServiceException: Data conversion failed; check log file'

Got CHECK APPSERVER LOGS. THE SITE BOOTED WITH INTERNAL DEFAULT SETTINGS, BECAUSE OF: bea.jolt.ServiceException: Data conversion failed; check log file
when started PIA and login screen appeared.

What version of PeopleTools are you using? Have you looked at E-AS: Error "Cannot find or open field table. Maybe FIELDTBLS32 is not set properly" (Doc ID 660607.1) yet?

Bea.jolt.ServiceException: Data conversion failed

Having problem with this error on Linux 6.2, Tuxedo 7.1, and JOLT 1.2.1
connecting
to SCO 5 and Tuxedo 6.5. The error in the ULOG is JSH.30085.1024.-2:
Can't map Jolt field id 167772175 to name
I read previous posts on problems with 7.1 connecting to 6.5. We have a
successful domains connection.
But, I think the problem is on the JOLT/Linux side. We received /
applied a patch that was supposed to correct this problem to no avail.
Any ideas are appreciated.

This problem could be due to a number of things :-
1- The definition for your service in the repository does not have all the fields
defined that the service can return.
2- The length of the fieldname is greater than 28 characters
I believe there is now a jolt patch to get over this problem
3- Your service is defined at OUTBUF=FML32 when it is not a 32bit service or visa
versa
4- The fields file pointed to by FIELDTBLDIR and FIELDTBLS does not contain the
correct values for the field
I hope this helps
Joe

BEA Jolt/WTC - expert advice invited

Hello All,
I am looking for some tips to speedup/shorten our development cycle of Java interface
to our Tuxedo application. We have around 200+ Tuxedo services in 30 Tuxedo servers.
Any hints on:
a. Can we avoid Jolt repository when using Jolt?
b. If not, how to quickly build the Jolt repository for each service?
c. Will the cycle time be less if WTC is used instead of Jolt?
Thanks in advance for the valuable tips/suggestions/comments.
Best Regards
MS

MS wrote:
I am looking for some tips to speedup/shorten our development cycle ofJava interface
to our Tuxedo application. We have around 200+ Tuxedo services in 30Tuxedo servers.
>
Any hints on:
a. Can we avoid Jolt repository when using Jolt?
b. If not, how to quickly build the Jolt repository for each service?
c. Will the cycle time be less if WTC is used instead of Jolt?Our system uses 1500+ Tuxedo services (written in COBOL), so we've seen the
same issues.
You have to use the repository, but don't rely on the RE applet. We only
use the bulkloader and generate the load file with a Perl program. [In
fact, the applet always crashes for us because it can't deal with >255
fields in a VIEW32 buffer). The batch upload runs on our fastest server
machine (1.4+ GHz Intel). WTC looks like a good bet to reduce development
time, and we are planning on using it in the future.
Felix Hack
SPL WorldGroup
[email protected]

Re: During installation: "bea.jolt.ServiceException: Invalid Session"

I am facing the same issue and in my configuration.properties file it says:
psserver=gaurav:9000
You said that you used server ip. Where I can get the server ip. Please revert as soon as possible.
Thanks in advance
Gaurav

Hi Nick,
I tried that already after going through this thread but no success. Still same error.
As shown below :
# For example: psserver=SERVER1:9000,SERVER2:9010,SERVER3:9020
## sd="Application Server Connect String", ld="This string embodies the failover and load balancing string for PIA to connect to Application Server domains. Consult the PeopleBooks recommendations on load balancing and failover for more information. The format is psserver=AppSrvr:JSLport where AppSrvr is your fully qualified domain name. Multiple domains should be comma separated", tip="Format: psserver=AppSrvr:JSLport where AppSrvr is your fully qualified domain name, e.g psserver=SERVER1.oracle.com:9000,SERVER2.oracle.com:9010"
psserver=192.168.0.1:9000
Please guide me further.
Gaurav.

UTFDataFormatException in JOLT buffer

I would appreciate some tips on how to track down the cause to my problems with
fetching certain strings from my database from my Java client using Tuxedo and
JOLT.
When reading a certain 380 characters long string from the database, the client
crashes, and I get the following message in my Java console:
"bea.jolt.ServiceException: bea.jolt.JoltRemoteService(ServiceName).decodeCALL()
bea.jolt.MessageException: bea.jolt.BufException: java.io.UTFDataFormatException
at bea/jolt/JoltRemoteService.decodeCALL
at bea/jolt/JoltRemoteService.call"
I have tried to find faulty characters by fetching various substrings of the string,
but only the substring with characters 1 to 379 or the entire 380 characters long
string seems to cause the problem. A substring with, for instance, characters
350 to 380 does not cause any error.
I have tested my service with UD32, and it works fine. The problem seems to be
at the JOLT level. Although the string was once written using the client, it is
not possible to regenerate the error by writing the exact same string via the
keyboard into my client. I cannot see any illegal characters when looking at the
string using SQL commands.
When looking in the JOLT API, I only get some information about the MessageException.
The BufException is not visible in the API documentation. Why is that?
Please, could someone help? Where can I look for the cause to this problem?
Thank You!
/Fredrik Israelsson
Systems used:
Tuxedo 7.1
Java 1.2.something
Oracle 8.1.7

Hi,
I'm not sure where you are wanting to check the buffer. If it is on the Jolt side, i.e., Java client side, then you get use the JoltMessage class accessors to find out what is in the buffer. On the Tuxedo side (JSL/JSH side) the handling of the buffers is done by C code, not Java and the protocol is not documented. There is no code in the JSH that does what you want, as it doesn't process the buffer in the same format as the Java side.
Can you explain a little more about what it is you are trying to accomplish?
Regards,
Todd Little
Oracle Tuxedo Chief Architect

How to run a sample Jolt client

Can any one explain me how to run a sample jolt client.
Iam trying to run the following jolt client code ToUpper.java at the command prompt but I am getting the following error.I am getting the same error when i run the Jrepository Applet RE.html.
D:\ToUpper>javac ToUpper.java
D:\ToUpper>java ToUpper
bea.jolt.SessionException: Cannot connect to any //localhost:3050.
Reason:NwHdlr: Network Error: chkauth: J_CHECKAUTH FAILED
at bea.jolt.JoltSessionAttributes.getDomainInfoJoltSessionAttributes.java:584)
at bea.jolt.JoltSessionAttributes.checkAuthenticationLevel(JoltSessionAttributes.java:507)
at ToUpper.main(ToUpper.java:20).
I have the tlistener running and provided apppassword and userpassword as my System login password where I have the complete Tuxedo Installation(server and client). Please see the attached sample jolt client program I am trying to run. I am not sure what configuration Settings I need to do.
ToUpper.java
/* Copyright 1996 BEA Systems, Inc. All Rights Reserved */
import bea.jolt.*;
public class ToUpper
public static void main (String[] args)
JoltSession session;
JoltSessionAttributes sattr;
JoltRemoteService toupper;
JoltTransaction trans;
String userName=null;
String userPassword=null;
String appPassword=null;
String userRole="myapp";
String outstr;
          try{
sattr = new JoltSessionAttributes();
sattr.setString(sattr.APPADDRESS, "//GVC3ZA03TESTING:3050");
switch (sattr.checkAuthenticationLevel())
case JoltSessionAttributes.NOAUTH:
break;
case JoltSessionAttributes.APPASSWORD:
appPassword = "123456"//"appPassword";
break;
case JoltSessionAttributes.USRPASSWORD:
userName = "myname";
userPassword = "123456";
appPassword = "123456";
break;
sattr.setInt(sattr.IDLETIMEOUT, 300);
session = new JoltSession(sattr, userName, userRole,
userPassword, appPassword);
toupper = new JoltRemoteService ("TOUPPER", session);
toupper.setString("STRING", "hello world");
toupper.call(null);
outstr = toupper.getStringDef("STRING", null);
if (outstr != null)
System.out.println(outstr);
session.endSession();
System.exit(0);
          }catch(Exception e){
          e.printStackTrace();
} // end main
} // end ToUpper

Hi Todd,
I am not getting the jcheckauthentication error now as i changed the port no. to the port where JSL is running.Now I am getting this error.Also find the ULOG contents pasted below.
D:\bea\tuxedo9.1\samples\jolt\ToUpper>java ToUpper
Authentication Level set To :0
Exception caught error no is:6
bea.jolt.ServiceException: TPENOENT - no entry found
at bea.jolt.JoltRemoteService.decodeCALL(JoltRemoteService.java:460)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:345)
at bea.jolt.JoltRemoteService.call(JoltRemoteService.java:267)
at ToUpper.main(ToUpper.java:39)
I have checked the jrepository file and also the Applet window for the service defination(TOUPPER)but still its not recognizing the service.Is there some configuration thing I have missed out before running JOLT client.
ULOG File Contents
132947.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
132956.GVC3ZA03TESTING!WSL.432.5308.0: WSNAT_CAT:1197: INFO: Exiting system
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
132956.GVC3ZA03TESTING!JSH.4000.2464.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
132956.GVC3ZA03TESTING!JSL.2644.2356.0: JOLT_CAT:1197: "INFO: Exiting system"
132956.GVC3ZA03TESTING!DMADM.5844.5348.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
132959.GVC3ZA03TESTING!BBL.3216.4372.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133021.GVC3ZA03TESTING!tmloadcf.6104.3164.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
133028.GVC3ZA03TESTING!BBL.6140.5124.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
133028.GVC3ZA03TESTING!BBL.6140.5124.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
133028.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
133028.GVC3ZA03TESTING!JSL.5608.6088.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133028.GVC3ZA03TESTING!JSL.5608.6088.0: LIBTUX_CAT:262: INFO: Standard main starting
133028.GVC3ZA03TESTING!JSL.5608.6088.0: INFO: JOLT Listener version-BEA Jolt 9.1
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
133028.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
133029.GVC3ZA03TESTING!JSH.6028.5748.-2: INFO: JOLT Handler version-BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Current version: BEA Jolt 9.1
133029.GVC3ZA03TESTING!JREPSVR.3476.4980.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
133029.GVC3ZA03TESTING!WSL.3292.4892.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSL.3292.4892.0: LIBTUX_CAT:262: INFO: Standard main starting
133029.GVC3ZA03TESTING!WSH.2568.3772.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.2568.3772.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133029.GVC3ZA03TESTING!WSH.5764.3836.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
133029.GVC3ZA03TESTING!WSH.5764.3836.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
133242.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133300.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
133359.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
133456.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid32(ACCOUNT_ID) failed for INQUIRY: LIBFML_CAT:8: ERROR: Unknown field name. Maybe FIELDTBLS32 is not set properly.
133612.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
143325.GVC3ZA03TESTING!JSH.6028.5748.-2: Fldid(SAMOUNT) failed for DEPOSIT: LIBFML_CAT:11: ERROR: Cannot find or open field table. Maybe FIELDTBLS is not set properly.
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144116.GVC3ZA03TESTING!WSL.3292.4892.0: WSNAT_CAT:1197: INFO: Exiting system
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144116.GVC3ZA03TESTING!JSH.6028.5748.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144116.GVC3ZA03TESTING!JSL.5608.6088.0: JOLT_CAT:1197: "INFO: Exiting system"
144116.GVC3ZA03TESTING!DMADM.4928.1868.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144119.GVC3ZA03TESTING!BBL.6140.5124.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144142.GVC3ZA03TESTING!tmloadcf.2668.3316.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144148.GVC3ZA03TESTING!BBL.4144.4376.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144148.GVC3ZA03TESTING!BBL.4144.4376.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144148.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144148.GVC3ZA03TESTING!JSL.5072.2444.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSL.5072.2444.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JSL.5072.2444.0: INFO: JOLT Listener version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144148.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144148.GVC3ZA03TESTING!JSH.5856.5268.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Current version: BEA Jolt 9.1
144148.GVC3ZA03TESTING!JREPSVR.2952.1248.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144148.GVC3ZA03TESTING!WSL.3040.5488.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSL.3040.5488.0: LIBTUX_CAT:262: INFO: Standard main starting
144148.GVC3ZA03TESTING!WSH.5740.2764.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.5740.2764.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144148.GVC3ZA03TESTING!WSH.1784.5448.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144148.GVC3ZA03TESTING!WSH.1784.5448.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144157.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144207.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144226.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144229.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1196: INFO: Terminating handlers in preparation for shutdown
144518.GVC3ZA03TESTING!WSL.3040.5488.0: WSNAT_CAT:1197: INFO: Exiting system
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1506: "INFO: Terminating Jolt administration services in preparation for shutdown"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1196: "INFO: Terminating handlers in preparation for shutdown"
144518.GVC3ZA03TESTING!JSH.5856.5268.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name 'jolt'; client name 'joltadmin'"
144518.GVC3ZA03TESTING!JSL.5072.2444.0: JOLT_CAT:1197: "INFO: Exiting system"
144519.GVC3ZA03TESTING!DMADM.4436.5968.0: CMDGW_CAT:1655: INFO: DMADMSVR is exiting
144522.GVC3ZA03TESTING!BBL.4144.4376.0: CMDTUX_CAT:26: INFO: The BBL is exiting system
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144537.GVC3ZA03TESTING!tmloadcf.4892.4980.-2: CMDTUX_CAT:872: INFO: TUXCONFIG file D:\bea\tuxedo9.1\samples\jolt\ToUpper\tuxconfig has been updated
144543.GVC3ZA03TESTING!BBL.5440.4548.0: 02-01-2007: Tuxedo Version 9.1, 32-bit, Patch Level (none)
144543.GVC3ZA03TESTING!BBL.5440.4548.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3149: INFO: BDMCONFIG environment variable not set. Using $APPDIR/BDMCONFIG
144543.GVC3ZA03TESTING!DMADM.1016.6128.0: CMDGW_CAT:3761: INFO: Using version 2 BDMCONFIG, 3DES is enabled.
144543.GVC3ZA03TESTING!JSL.1796.5232.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSL.1796.5232.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JSL.1796.5232.0: INFO: JOLT Listener version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1563: "INFO: Serial Number : <454493271161-2140437240256>, Expiration Date : <2007-02-15>"
144543.GVC3ZA03TESTING!JSL.1796.5232.0: JOLT_CAT:1564: "INFO: Licensee : <BEA Evaluation Customer>"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1030: "INFO: Jolt Handler joining application"
144543.GVC3ZA03TESTING!JSH.3164.4076.-2: INFO: JOLT Handler version-BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Current version: BEA Jolt 9.1
144543.GVC3ZA03TESTING!JREPSVR.860.2916.0: Repository "D:\bea\tuxedo9.1\udataobj\jolt\repository\jrepository" (16 records) is writable.
144543.GVC3ZA03TESTING!WSL.2596.4404.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSL.2596.4404.0: LIBTUX_CAT:262: INFO: Standard main starting
144543.GVC3ZA03TESTING!WSH.3508.5136.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.3508.5136.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144543.GVC3ZA03TESTING!WSH.4288.5676.0: 02-01-2007: Tuxedo Version 9.1, 32-bit
144543.GVC3ZA03TESTING!WSH.4288.5676.0: WSNAT_CAT:1030: INFO: Work Station Handler joining application
144548.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"
144634.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1198: "WARN: Forced shutdown of client; user name ''; client name 'myapp'"
144734.GVC3ZA03TESTING!JSH.3164.4076.-2: JOLT_CAT:1043: "ERROR: tpacall() call failed, tperrno = 6"

Bea.jolt.JoltRemoteService.decodeCALL()

Similar Messages

Maybe you are looking for