JDENETTimeout setting in [NETWORK QUEUE SETTINGS]

DavidHuang

DavidHuang

Active Member
Hi all,

Due to the performance issue, PO receipt run very slowly (2 minutes per
record), system report "commit fialed" and we have to use P42210 to roll
back inventory. To alleviate user's pain, we want to increase the value of
JDENETTimeout. If it is changed from 180 to 1800, is there any negative
affect caused by the long Timeout on other application? Can you kindly share
you experience of setting JDENETTimeout?

Any advice is welcome.

Out current settings:

[NETWORK QUEUE SETTINGS]
UBEQueue=QB7334
UBEPriority=5
PrintImmediate=FALSE
SaveOutput=TRUE
InstallSpecs=Y
JDENETTimeout=180
InstallERSpecs=N

Thanks,
David
 
David,

The same setting applies for all other Client-2-Server communications, for example, when a Fat Client cannot connect to the Security Server, so in such cases the users will have to wait for 30 minutes (with the timeout set to 1800) until they finally get an error.

If that's acceptable, then go for it. Sometimes it's unavoidable, but you should really consider rectifying the cause of your issue - the performance of the server. There's usually a lot that can be done to improve it in most cases. Even without a hardware upgrade.
 
Back
Top