powered by Jive Software

Problem with Bosh connection

#1

When we connect using Bosh we don’t receive the correct xml namespace during a Bosh handshake reply.

Expected server response:

Actual server response:

Please refer to post #11 on this thread http://forum.ag-software.de/thread/879

#2

Greetings,

Thanks for letting us know about the issue, I filed it here OF-346 with high priority.

If there are any other issues with Openfire’s BOSH implementation, please let us know or point out old posts on the matter.

thanks,

daryl

#3

I’ve committed the attached patch to the trunk, this should fix the issue for the next release.

[Edited]: removed incorrect patch and reopened the Jira ticket.

#4

Thanks Guenther. Sorry I had the ticket filed backwards

daryl

#5

Can you please point us to the SVN path that will have the latest released stable OpenFire source that we can apply this patch on top?

Thanks.

#6

Hello,

http://www.igniterealtime.org/downloads/source.jsp

svn co [http://svn.igniterealtime.org/svn/repos/openfire/trunk](http://svn.igniterealtime.org/svn/repos/openfire/trunk) openfire

daryl

#7

Hi Daryl,

I work with Arthur123 on the same team. We are a little skeptical in using the code in the trunk. What is the latest stable release tag that your patch will work on?

–Stefanos.

#8

Hello,

I understand your skeptism on using trunk, but it is basically what will be released as 3.7.0 beta and has been working great for me in production. Trunk is very stable right now.

daryl

#9

Hey Daryl,

I’m working with the above guys and I’m having trouble connecting to the svn repository. I keep getting a “could not connect to server http://svn.igniterealtime.org” error. I’m trying to follow the directions contained here: http://www.igniterealtime.org/community/docs/DOC-1020. I’m trying to connect to this url: http://svn.igniterealtime.org/svn/repos**.** Any ideas?

#10

Hello Stan,

I don’t seem to be having any troubles with that URL. Is a firewall perhaps blocking access?

Would it help you folks to have a binary of the beta? I can easily generate a RPM for you.

daryl

#11

I suppose it’s possible we might have something on our firewall blocking access. Regardless, a binary of the beta would be awesome and solve the problem. Thanks!

#12

Here you go:

http://mesonet.agron.iastate.edu/pickup/openfire-3.7.0.beta-1.i386.rpm

daryl

#13

We’ve run into this issue as well. Is there a windows installer for the 3.7 beta as well? I have the trunk and all, but it looks like I need to register for a install4j license if I want to build the Windows installer, and I was wondering if there was an alternate path.

#14

Hey thanks for making that fix for us. It looks to have mostly fixed the problem. We are still having a problem with receiving chat messages however. It appears to be due to an unneeded empty namespace inserted into the response xml:

Expected server response:

Hello stan

Actual server response:

Can you see this?
#15

Hi Stan, thanks for reporting! It seems my patch wasn’t correct, I will have another look on that topic.

#16

Hello,

I updated my linux binary based on the latest set of patches.

http://mesonet.agron.iastate.edu/pickup/openfire-3.7.0.beta-1.i386.rpm

daryl