Re: [ebxmlms-general] Out of memory error in the MSH monitor

[David W. \(XML\) <da...@dr...>]

Mattias,

The patches and fixes to allow sending of any size message (we tested up =
to 150MB) are in the source code ZIP downloadable from:

 http://ebxmlbook.com/interop/=20

Included in that is the fixes to the error in the mimetype handling that =
corrupts the first 16 bytes of a binary file.

I'm not sure if any of these corrections made it into the main trunk =
codebase.

Basically you need these fixes to send files larger than 10Mb.

DW

  ----- Original Message -----=20
  From: Mattias J=20
  To: ebx...@li...=20
  Sent: Thursday, July 21, 2005 7:37 AM
  Subject: Re: [ebxmlms-general] Out of memory error in the MSH monitor


  At 2005-07-21 12:48, you wrote:

    When I repeatedly sent a message with one attachment of size 600KB =
100 times from the MSH monitor in one Windows PC (call it A) to the MSH =
monitor in another Windows PC (call it B), the monitor in B showed the =
java.lang.OutOfMemoryError after displaying the first 66 messages =
received in the "Receive History" (the remaining 34 messages could be =
displayed after OutOfMemoryError occurred), while the monitor in A =
revealed all 100 messages sent with the state "Sent and Acknowledgement =
Received" when right-clicking the messages in the "Sent History" in A.=20

    The OutOfMemoryError still occurred until the MSH monitor in B was =
restarted.  Right after the restart, the remaining 34 messages were =
displayed in the "Receive History".=20

    The default MaxPayloadSize (1000000) in msh_client.properties.xml is =
used. PC A has 512MB RAM and paging file size allocated is 768MB, while =
PC B has 768MB RAM and paging file size allocated is 1152MB.

  Well, how much memory did you assign to the JVM?
  Check out -Xmn, -Xms and -Xmx