powered by Jive Software

Implementation of connection manager

Openfire Openfire Support
#1

hey,

i have a few questions regarding implementation of connection manager / openfire / bosh.

i have a working OF server that is using punjab bosh service. thru this service clients ar connecting using js(stanza) chat web client.

so successfully installed connection manager it’s up and running and i see in OF server.

so my question is should i redirect ussers like this

server1 : OF

server2 : CM

(http://server2/bosh)--)> mod_rewrite-> (http://server1/bosh)

OR

(http://server2/bosh)--)>punjab->(server1:5280) ??

so im looking as optimal performance vise solution every comment will be appreciated

**

**

#2

Punjab translates BOSH to XMPP. It’s important to remember that BOSH and XMPP are different. The reason you would use Punjab over the built in BOSH method is that you pretty much cap at about 1500 simultaneous BOSH users with the Openfire BOSH setup. These are BOSH, not XMPP connections. XMPP connections in Openfire can go up to 50K< supposidly. With that being said the solution if you require much more than 1000 simultaneous BOSH users would be to deploy multiple servers using Punjab to utilize the higher number of XMPP socket connections. The setup would work as follows;

Client1 ==BOSH> Pujab_Server_A ==XMPP> Openfire_Server_A

Client2 ==BOSH> Pujab_Server_B ==XMPP> Openfire_Server_A

Client3 ==BOSH> Pujab_Server_C ==XMPP> Openfire_Server_A

Ideally if you have access to a load balancer or are familiary with any free load balancing techniques it would go more like this;

Client1 ==BOSH> Load_Balancer ==> Punjab_Server_A ==XMPP> Openfire_Server_A

Client2 ==BOSH> Load_Balancer ==> Punjab_Server_B ==XMPP> Openfire_Server_A

Client3 ==BOSH> Load_Balancer ==> Punjab_Server_C ==XMPP> Openfire_Server_A

An important note is that the load balancer will need to have some sort of sticky source IP setup where the client always goes to the same Punjab_server. If this isn’t setup right then the client will get invalid SID errors causing BOSH to stop functioning. Hope this helps!

#3

thnx j@cob,

well i solve this some time ago,

my solution was so simple :>

did new vmware image installed ubuntu server

installed punjab; cloned this server

on the client side i used nginx and ip_hash option 4 load balancing ;> simple and elegant

#4

Hello,

Just curious if you both are still happily using punjab with openfire?

daryl

#5

hi @itwellis

I am also implementing Bosh client with open fire and need to scale this asafter about 500 connections the open fire stops responding.

i saw you wrote

"

well i solve this some time ago,

my solution was so simple :>

did new vmware image installed ubuntu server

installed punjab; cloned this server

on the client side i used nginx and ip_hash option4 load balancing ;> simple and elegant"

if you can elaborate more on this and explained exactly what you did itwould be very helpful to me and save time

Thanks

Dror.