>Subject: Re: [sipX-dev] Http Message Content Length Limit > >Raymond Dans wrote: >> Subject: Re: [sipX-dev] Http Message Content Length Limit >>> >>> On Thu, 2008-11-06 at 14:05 -0500, Raymond Dans wrote: >>>> I've verified that on a system with 4200 users defined >that at least >>>> one of the tables being replicated generates a message >>> content length >>>> of about 6.5 Mb and of course will fail because it exceeds >>> the current >>>> limit. >> >> Scott wrote: >>> out of curiosity... which is it? >>> >>> >> The table was "permission". >> >> For those of you who like "Seinfeld". I'm starting to feel like >> Kramer when he test drove a car and wanted to see how far he could >> drive it before running out of gas. I just can't help >myself - got to keep going >> :) >> >> I'm now at 7200 Users and have now failed on the same table >> (permission) because of the timeout in sipXConfig (i.e. 15 >seconds). >> Content Length for this table is 10,258,764 bytes. >> Damian wrote: > >For the record: I am pretty sure I could replicate 100k users >using the old HTTP push mechanism. We could probably come up >with XML/RPC method definition that results in shorter >messages but Scott is right. Doing replication in batches is >probably the right thing to do. >D. > SipXsupervisor already supports the capability of doing table updates in batches using the "insertRows" and "deleteRows" XML RPC methods so I guess we would just need to add the logic in SipXconfig to use these in an appropriate manner. For File replication, I don't think we need to make any changes after my patch for Base64 decoding is submitted. It should resolve any file size issues we were seeing.
Raymond _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
