Problem:

• Product Name: VisiBroker for C
• Product Version: 5.2.1
• Product Component: Client-side ORB runtime
• Platform/OS Version: HP-UX
• JDK/Compiler Version: all

VBC 5.x - Crash pointing to VISDelegate::invoke (). 

The following crash is reported on VBC Client process when multiple simultaneous Client requests are made on the same Server object. 

Program terminated with signal 10, Bus error.
#0 0xc54139bc in () from /sms/smsapp/vbroker/BES/5.2/lib/liborb_r.sl(gdb) thread apply all btThread 37 (system thread 8376400):
#0 0xc54139bc in () from /sms/smsapp/vbroker/BES/5.2/lib/liborb_r.sl
#1 0xc551a144 in VISDelegate::invoke () from /sms/smsapp/vbroker/BES/5.2/lib/liborb_r.sl
#2 0xc56949a0 in CORBA_Object::_invoke () from /sms/smsapp/vbroker/BES/5.2/lib/liborb_r.sl
#3 0xc690d9a4 in WOMgr::WorkOrderFactory::distReqResult () from /sms/smsapp/lib/libwomgr_c.sl
#4 0xce49cc30 in DmDistReqOp::exec (this=0x4053f028) at /proj/sms/esm24.3/offsrc/nsms/src/libsrc/nedm/DmDistReqOp.C:1666

Resolution:

This crash is reported in application stress testing and attempts to reproduce this crash in Borland testing have not been successful. The crash was narrowed down to the use of Client side request header cache, but the root cause of the crash could not be determined.If this crash is reproducible, then Borland support will like to do more debugging of the application that reproduces this crash to find out the root cause.

Fortunately, a workaround is available to avoid this crash by disabling the use of Client side request header cache. This cache is on by default. This workaround for failure 43282 is available in VBE 5.2.1.P13 and subsequent patches which are available for download from http://support.borland.comThe workaround fix provides a new property to turn off request header cache on the Client side.

The process is to be started with following property to avoid this failure:

-Dvbroker.orb.cacheRequestHeader=false

Old KB# 26658