Cyrille,
just set for your <callback> the delay to something like 100000000 millis.
This reduces the 'No connection established, ...' logging.
Additionally, you could add a fake callback address like
<callback ....>
http://localhost:99999/RPC2
</callback>
so the first WARN is not too ugly.
You'll find some more XmlScripts in the directory
xmlBlaster/demo/javaclients/script.
regards
Marcel
Marcel,
I've tried you tips, now the connect and subscribe works.
But, on the server side there are messages :
[WARN Thread-6
DispatchConnection-callback:/node/xmlBlaster_192_168_0_151_3412/cl
ient/aaa/3] Connection transition UNDEF -> POLLING:
xmlBlaster://192.168.0.151:3412 is unaccessible,
we poll for it every 1000 msec: errorCode=communication.noConnection
message=#exported init() faile
d : java.net.MalformedURLException: no protocol:
[INFO Thread-6 Authenticate-/node/xmlBlaster_192_168_0_151_3412]
Successful login
for client /node/xmlBlaster_192_168_0_151_3412/client/aaa/3, session
expires after [ 1 h 0 millis ]
, 1 of 10 sessions are in use.
[WARN XmlBlaster.PingTimer
DispatchConnection-callback:/node/xmlBlaster_192_168_0
_151_3412/client/aaa/3] No connection established,
xmlBlaster://192.168.0.151:3412 still seems to be
down after 301 connection retries.
[WARN XmlBlaster.PingTimer
DispatchConnection-callback:/node/xmlBlaster_192_168_0
_151_3412/client/aaa/3] No connection established,
xmlBlaster://192.168.0.151:3412 still seems to be
down after 241 connection retries.
Here is my Connect Qos :
<qos>
<session name="'+username+'/3" timeout="3600000" maxSessions="10"
clearSessions="false" />
<queue relating="connection">
<address type="XMLRPC" pingInterval="5000" retries="-1" delay="1000" />
</queue>
<queue relating="callback" maxEntries="5" maxEntriesCache="2">
<callback type="XMLRPC" pingInterval="5000" retries="-1"
dispatcherActive="false" delay="1000"/>
</queue>
</qos>
Cyrille
