[xmlblaster-devel] connection problems with native clients in .848+

[Michael Atighetchi <matighet at bbn.com>]

I have a native client within an xmlblaster master node which tries to
connect to another master node, and I'm getting the following case
(see trace).

yyy.yyy.yyy.yyy is the master the native client is trying to connect
to. As you see in the trace, I'm getting the callback in the
PSQNativeClient via reachedAlive, however, .toXml on the
connectionhandler reports "<connected>false</connected>" 

What could cause such a condition ?


[May 30, 2003 1:53:34 PM INFO  CorbaConnection] Accessing xmlBlaster AuthServer IOR using builtin http connection to xmlBlaster://yyy.yyy.yy.yy:7601
[ Connected to yyy.yyy.yy.yy:47946 from local port 40650 ]
[May 30, 2003 1:53:34 PM INFO  DeliveryConnection-connection:client/psqplugin_128.33.15.34] Connection transition POLLING -> ALIVE: Success, connection:client/psqplugin_128.33.15.34 connected.
[May 30, 2003 1:53:34 PM INFO  PSQNativeClient] reachedAlive called - connected to 
 <XmlBlasterAccess id='client/psqplugin_xxx.xxx.xxx.xxx' state='ALIVE'>
  <connected>false</connected>
 </XmlBlasterAccess>

-- 
matighet at bbn.com   BBN Technologies