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

Re: [xmlblaster] AW: XMLBlaster exceptions

I sent an answer directly, here a copy for the community:

Hi Serge,

Konrad Krafft wrote:
Dear Vinahradau,

sorry, but I’m not so deep in those details any more.

You have to send your request to xmlblaster at server.xmlblaster.org <mailto:xmlblaster at server.xmlblaster.org>

Maybe Marcel or Michele will help you.



-----Ursprüngliche Nachricht-----
*Von:* Siarhei Vinahradau [mailto:vinahradau at yahoo.de]
*Gesendet:* Sonntag, 4. September 2005 22:48
*An:* konrad.krafft at doubleslash.de
*Betreff:* XMLBlaster exceptions

Dear Konrad,

I was wondering if you could help me with some XMLBlaster problems:

   1. I’m getting an exception on the server/publisher side (wrong
      protocol…) for Socket connections. Is it possible to solve the


[04-Sep-2005 21:39:16 WARN XmlBlaster.SOCKET SocketCallbackImpl-floor] Closing

connection to server: java.net.SocketException: Software caused connection abort

: recv failed

It seems that the protocol used on the client side is not the same as the one on which the serverside is listening. My guess is that you are using SSL on the server side and not on the clientside or the opposite or the keys are not synchronized.

Could you test that everything is working by using the "clean" SOCKET without any SSL (see http://www.xmlblaster.org/xmlBlaster/doc/requirements/protocol.socket.html).


[04-Sep-2005 21:39:16 WARN XmlBlaster.SOCKET.tcpListener-floor SOCKET-HandleCli

ent-floor] Error parsing TCP data from '/', check if client an

d server have identical compression or SSL settings: java.net.SocketException: C

onnection reset

   2. When a subscriber connects to a server, it automatically gets the
      last message (although it was not subscribed yet). Is it a
      protocol feature?

No that is not a feature and should not happen. My guess (again this is just a guess) is that you did a persistent subscription earlier and you did not cleanup the persistence (per default it is set to hsqldb).

You can clean it up by removing the files ${HOME}/tmp/client* and ${HOME}/tmp/xmlBlaster*


Thanks a lot for your help.

Best regards,

Serge Vinahradau

Student, MSc in Computing, Imperial College, London


Gesendet von Yahoo! Mail <http://de.mail.yahoo.com> - Jetzt mit 1GB kostenlosem Speicher