Bug #771

PROTO error - no reply from service in multi-threaded server mode without long jump

Added by Madars 8 months ago. Updated 8 months ago.

Status:ClosedStart date:04/17/2022
Priority:Normal (Code 4)Due date:
Assignee:-% Done:

100%

Category:-
Target version:-

Description

Following errors might appear in XATMI servers log, which is running with <mindispatchthreads> > 1 and is using ndrx_main_integra() with ATMI_SRVLIB_NOLONGJUMP flag entry point for the server:

N:NDRX:2:c9e5ad48:259189:7fcb54353700:002:20220416:232150352374:v_serve_call:spatch.c:0592:PROTO error - no reply from service [ECHO]
N:NDRX:2:c9e5ad48:259189:7fcb520c3700:006:20220416:232150423756:v_serve_call:spatch.c:0592:PROTO error - no reply from service [ECHO]
N:NDRX:2:c9e5ad48:259189:7fcb5320b700:004:20220416:232150452208:v_serve_call:spatch.c:0592:PROTO error - no reply from service [ECHO]
N:NDRX:2:c9e5ad48:259189:7fcb5320b700:004:20220416:232151036922:v_serve_call:spatch.c:0592:PROTO error - no reply from service [ECHO]

History

#1 Updated by Madars 8 months ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 100

Release notes

XATMI server library has been fixed so that in no-long-jump mode (.e.g. server started by ndrx_main_integra()), tpreturn()/tpfroward() would properly finish the processing

Available from Enduro/X release 8.0.6+, 7.5.38+

#2 Updated by Madars 8 months ago

  • Description updated (diff)

#3 Updated by Madars 8 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF