Re: [xmlblaster] getting new messages like a subscribtion

[Cyrille Giquello <cyrille at giquello.com>]

Previous messages were from a Flash client test.

Now I've tested your XmlScript with the javaclient. It seems to work.

But, after running the XmlScript, I've stopped xmlBlaster, then restart it.
XmlBlaster seems to recreate the session.

[WARN  Thread-6
Authenticate-/node/xmlBlaster_192_168_0_151_3412.AccessDenied] SessionId
'sessionId:19
2.168.0.151-null-1134138825134--1492852909-7' is invalid, no access to
xmlBlaster.
[Thread-6 Authenticate-/node/xmlBlaster_192_168_0_151_3412.AccessDenied]
SessionId 'sessionId:19
2.168.0.151-null-1134138825134--1492852909-7' is invalid, no access to
xmlBlaster.
[Thread-6 Authenticate-/node/xmlBlaster_192_168_0_151_3412.AccessDenied]
SessionId 'sessionId:19

Perhaps it is just because of
   <persistent>true</persistent>
in the connect qos of the XmlScript

cyrille

Cyrille Giquello wrote:

> 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