Hi,
we have a Web Dynpro ABAP IView in Portal. The Portal communicates via Web Dispatcher (load balancing) to one of two SRM ABAP instances in order to launch Web Dynpro application. Users of the portal often get blank screen during transition to the next screen.
In ICM trace of SRM ABAP instance I've found a lot of errors:
*** ERROR => HttpExtractESID: illegal ESID len 29
according to note 2128269 - HttpExtractESID: illegal ESID len <length>
I've found that Web Dynpro program name, and that http request header 'sap-ext-sid' is really 29 bytes instead of 48.
Could anybody tell howto change size of sap-ext-sid, and how it critical for Web Dispatcher to make right decision to forward http request to the right ABAP instance, where the user had been authorized and rollout?
[Thr 140628798547728] *** ERROR => HttpExtractESID: illegal ESID len 29 [http_plg_mt. 6848]
[Thr 140628798547728] Address Offset IcmReadFromConn received
[Thr 140628798547728]
[Thr 140628798547728] 7fe6b98f1148 000000 504f5354 202f7361 702f6263 2f776562 POST /sap/bc/web
[Thr 140628798547728] 7fe6b98f1158 000016 64796e70 726f2f73 61702f7a 74656e64 dynpro/sap/ztend
[Thr 140628798547728] 7fe6b98f1168 000032 6572732f 3b736170 2d657874 2d736964 ers/;sap-ext-sid
[Thr 140628798547728] 7fe6b98f1178 000048 3d534650 4b2a6c58 6447586e 57735f30 =SFPK*lXdGXnWs_0
[Thr 140628798547728] 7fe6b98f1188 000064 3678684a 4655772d 2d384e78 45653f73 6xhJFUw 8NxEe?s
[Thr 140628798547728] 7fe6b98f1198 000080 61702d63 6f6e7465 78746964 3d534944 ap-contextid=SID
[Thr 140628798547728] 7fe6b98f11a8 000096 25336141 4e4f4e25 33617361 70733534 %3aANON%3asaps54
[Thr 140628798547728] 7fe6b98f11b8 000112 63695f53 35345f35 34253361 4c577434 ci_S54_54%3aLWt4
[Thr 140628798547728] 7fe6b98f11c8 000128 524d6b56 5274386c 41417673 73395150 RMkVRt8lAAvss9QP
[Thr 140628798547728] 7fe6b98f11d8 000144 4c487364 6c325155 56656f5a 6c6f3776 LHsdl2QUVeoZlo7v
[Thr 140628798547728] 7fe6b98f11e8 000160 36793057 2d4e4557 20485454 502f312e 6y0W-NEW HTTP/1.