[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmlblaster] 0.848 connection error

Madere, Colin wrote:

I've got only SOCKET turned on on the server (a CVS update done today around
12pm CDT) with a port of 7900.

I've got the client connecting specifying the protocol and port via command
line with all the new syntax (from a client machine running the downloaded
0.848 jar file).

I get an exception saying my Socket URL is bad and is "IOR:010203041020...".
Shouldn't it start with "socket?".  Error below:

[May 23, 2003 8:27:01 PM INFO SocketConnection] Creating default callback
server type=SOCKET [May 23, 2003 8:27:01 PM INFO SocketCallbackImpl-dummyLoginName] Started
callback receiver plugin on 'socket://' [May 23, 2003 8:27:01 PM ERROR BlasterClientTest] XmlBlasterException
errorCode=[resource.configuration.address] serverSideException=true
node=[xmlBlaster_192_168_200_195_3412] location=[SocketUrl] message=[Your
given SOCKET url
'IOR:000000000000004049444C3A6F72672E786D6C426C61737465722...' is invalid :

(I put in the '...' since the string was extrememly long.)

This exact client worked with the same settings before the update to 0.848.
Just changed the client command line syntax as required and server config
variable name to set the port. Could the fact that the server is


start the server:

 java org.xmlBlaster.Main -plugin/socket/port 7900

start the client:

  java HelloWorld3 -protocol SOCKET -plugin/socket/port 7900

works fine (-protocol will be used as the default for 'connection' and for 'callback').

You probably configured:

java HelloWorld3 -dispatch/connection/protocol SOCKET -plugin/socket/port 7900

which forces the client side connection to SOCKET, but still leaves the callback connection
with the default setting IOR (Corba).
Unfortunately mixing protocols with SOCKET is currently not possible since SOCKET resuses
the same TCP socket to tunnel the callback back to the client.

Mixing protocol for client side access and callback access is free possible with Corba, RMI
and XmlRpc. So a client can connect with RMI and receive callbacks with XmlRpc:

java HelloWorld3 -dispatch/connection/protocol RMI -dispatch/callback/protocol XMLRPC

You need to configure your client like this:

  java HelloWorld3 -protocol SOCKET -plugin/socket/port 7900

or like this

java HelloWorld3 -dispatch/connection/protocol SOCKET -dispatch/callback/protocol SOCKET -plugin/socket/port 7900

or most precise like this

java HelloWorld3 -dispatch/connection/protocol SOCKET -dispatch/callback/protocol SOCKET -dispatch/connection/plugin/socket/port 7900



(We need to cleanup the misleading exception)