|
From: David W. \(XML\) <da...@dr...> - 2005-07-21 14:43:32
|
See patches available from http://ebxmlbook.com/interop ZIP file - to = correct problems with binary attachment handling in Hermes. DW ----- Original Message -----=20 From: em...@og...=20 To: ebx...@li...=20 Sent: Thursday, July 21, 2005 6:48 AM Subject: [ebxmlms-general] Out of memory error in the MSH monitor 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.=20 I have some questions based on the above incident:=20 1. Although PC B did not reveals all messages, PC A reveals that all = mesages "Sent and Acknowledgement Received", I wonder whether PC B = successfully receive all 100 messages?=20 2. Any recommendation on the hardware requirements on running Hermes, = especially a large volume of messages need to be processed?=20 3. Although PC B has more RAM and virtual memory than PC A, but the = out of memory error did not occur in A. Is there any difference in the = memory or other hardware requirement for sending messages and receiving = messages.=20 4. Any other experience sharing is welcomed.=20 Regards,=20 MC |