The normal causes are those reported in the onServerError documentation.
Other causes are possible from the Server point of view, but they should not happen when the Web Client Library is used.

If JMX is not used or not enabled
and the Metadata Adapter does never leverage the ConflictingSessionException,
then the case should be investigated;
the corresponding Server log might contain some hint.