https://www.ejabberd.im/node/1503 en https://www.ejabberd.im/node/1503#comment-3634 <p>I am _not_ an expert on this, so please forgive me if I a spreading voodoo rather than accurate answers.</p> <p>Recently, I had similar (but not identical) problems. I ended up splitting up the transports on to separate ports, one each. So, in your example above, you are connecting all three transports to port 8888. Try doing one on 8888, one on 8889, and one on 8890 (just examples for the port numbers), and fire them up again. You will need to edit the "config.xml" file for _each_ transport separately, and match up the correct port with the one you selected in your ejabberd.cfg file.</p> <p>Anyway, all of my problems went away when I did that. Like I said, could be that I changed something else and didn't realize it, and the above is just superstition...</p> <p>I am running on a CentOS 5.0 box, so it's not Windows, but I suspect that this isn't your problem.</p> <p>P.S. A quick test would be to simply drop two of the three transports and leave just one running on port 8888, and see it that one behaves correctly. Also, I would _delete_ the files in the "ha" directory in the "spool" directory of the transports, because they may be _corrupt_ from the interactions on the same port!</p> Mon, 30 Apr 2007 20:27:30 +0000 hadar comment 3634 at https://www.ejabberd.im