Hello,
we expect extreme (I think) long latency while using HWS WebService, up to
30 seconds during operations like chnanging the status of the task. Does
anyone have any idea about this behaviour ?
This is not regular behaviour, the processor utilization is low during these
operations, the server load is also minimal.
Regards
Artur Jedynak

[ Post a follow-up to this message ]

The task status change is processed by the HWS interceptor, and only
reflected once a persistence point is hit.  Try wrapping your task message
receive shape in an atomic scope.  Since the scope will force a persistence
point when it exits, that may improve the latency you see.

--Chris

--------------------[vbcol=seagreen] 
these[vbcol=seagreen] 

This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

[ Post a follow-up to this message ]