Marcel Ruff wrote:
Jürgen Prinz wrote:
I use this feature to assure, that only one client with this
session-id is connected. i only wondered that the exception did not
occure with the connect.
It happens on connect, but you are notified asynchronously as you are
in fail safe mode.
Note tha
Jürgen Prinz wrote:
I use this feature to assure, that only one client with this
session-id is connected. i only wondered that the exception did not
occure with the connect.
It happens on connect, but you are notified asynchronously as you are in
fail safe mode.
Note that you can max log in onc
I use this feature to assure, that only one client with this session-id
is connected. i only wondered that the exception did not occure with the
connect.
Best regards and thanks
Jürgen
P.S. What about my problem with OSF/Motif timmers ?
Marcel Ruff wrote:
Dear Jürgen,
the details of this
Dear Jürgen,
the details of this feature are described here:
http://www.xmlblaster.org/xmlBlaster/doc/requirements/client.configuration.html
(search "Assuring a client singleton " there)
First you should set
maxSessions='1'
in your use case!
You get the exception "errorCode=user.configuratio
To prevent identical users , i use setReconnectSameClientOnly(true) in
SessionQos. It works, but the error is a bit confusing (see below) The
connect is ok, but the following get has a exception.
Sep 25 10:16:41 vpngateway Objserv(2007,650,INFO,,,#1)[24414]:
[EMAIL PROTECTED] connecting to xml
