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

Question

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.

Answer 1

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.