Gisbert
Member
Hi, we have a custom middleware that process interop with JDE 9.1 via XML Request, we have the logic to reuse the session generated for each user, after some time the server doesn't response anymore to xml requests, but still works for web client.
In the server manager the errors looks like: jdeSawImpGetKernelUserListV3:Error:JDENET_ReceiveMsg:le_net_error 11:<srvbd02>,<6016>,15925416,5
Here is a sample of the XML sent:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<jdeRequest sessionidle="900" environment="JPD910" session="17760508.1448400516.2" comment="" user="XXX" type="callmethod" role="*ALL" pwd="XXX">
<callMethod name="FormatLocation" app="cme">
<params>
<param name="szCostCenter"> 103</param>
<param name="szDisplayFormatLocation">00000000</param>
<param name="cValidate">2</param>
<param name="cMode">2</param>
</params>
</callMethod>
</jdeRequest>
As you can see the session is reused with a timeout of 15 minutes until jde return it's expired, then we create a new one; so there is no clue why the overhead.
If someone can share any tip would be great.
Thanks.
Som
In the server manager the errors looks like: jdeSawImpGetKernelUserListV3:Error:JDENET_ReceiveMsg:le_net_error 11:<srvbd02>,<6016>,15925416,5
Here is a sample of the XML sent:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<jdeRequest sessionidle="900" environment="JPD910" session="17760508.1448400516.2" comment="" user="XXX" type="callmethod" role="*ALL" pwd="XXX">
<callMethod name="FormatLocation" app="cme">
<params>
<param name="szCostCenter"> 103</param>
<param name="szDisplayFormatLocation">00000000</param>
<param name="cValidate">2</param>
<param name="cMode">2</param>
</params>
</callMethod>
</jdeRequest>
As you can see the session is reused with a timeout of 15 minutes until jde return it's expired, then we create a new one; so there is no clue why the overhead.
If someone can share any tip would be great.
Thanks.
Som