[JDEV] Karma and transferring large XML message packets...

[Keith Minkler]

That is not a karma problem..

your karma settings are rather high, and would not interfere with a data chunk that size..
(incidentally, you can "turn off" karma all together by just setting <dec>0</dec>)

most likely, if you are SURE that you do not have bad XML, and all of your tags are UTF-8 
encoded.. you are hitting an internal node size limit.. which I thought was somewhere around
500K bytes, but that might have been changed somewhere along the line... I can't look into
it right now, but I'll take a look, and see if I can find out what the max node size is
now adays.. =]

Happy Hunting!
Keith

On Sun, Apr 22, 2001 at 09:46:42AM -0400, Peter Sparago wrote:
> Hi All,
> 
> I am fairly new to Jabber (since about Feb 1) but I must say, It ROCKS! I am designing a P2P system that uses Jabber as one of the information transports. In addition to normal chat messaging, we are using Jabber messaging to transfer large amounts of XML data (using an 'x' namespace) between Jabber users. The 'x' XML data will probably be in the 30K - 300K range. I am able to send a 6K packet without any trouble, the packet I am having trouble with is 60K.
> 
> We are using Jabber 1.4.1. I've adjusted the Karma settings as follows:
> 
>       <karma>
>         <heartbeat>2</heartbeat>
>         <init>64</init>
>         <max>64</max>
>         <inc>6</inc>
>         <dec>1</dec>
>         <penalty>-3</penalty>
>         <restore>64</restore>
>       </karma>
> 
> 
> When I send the problem packet I get the following from Jabber:
> 
>     <stream:error xmlns="http://etherx.jabber.org/streams">Invalid XML</stream:error>
> 
> And then I get the following Java program exception:
> 
>     Exception processing results: java.net.SocketException: Connection aborted by peer: socket write error
> 
> I have checked the message packet that Jabber is complaining about by running the XML through a couple of different XML checkers. The XML (as far as I can tell) is valid. I'm assuming that this is may be some kind of burst or buffering error.
> 
> I realize that I can transmit the XML out of band, but most of our users will be behind firewalls and therefore the OOB approach is not going to work for us. 
> 
> Any help would be greatly appreciated.
> 
> peter
Keith Minkler

-------
Software Developer
Jabber.COM, Inc.
-------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 232 bytes
Desc: not available
URL: <https://www.jabber.org/jdev/attachments/20010425/cb0b176f/attachment-0002.pgp>