<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Message</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2800.1491" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial size=2>
<DIV><SPAN class=405053219-22032005><FONT face=Arial size=2>
We just ported to omniORB, and so far it has been wonderful, but we have had the
following problem that I have been unable to fix except by working around
it.</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005><FONT face=Arial size=2>
When our users try to send more than 5 pictures over our CORBA Connection, we
get a MARSHAL exception. I have read in <A
href="http://www.omniorb-support.com/pipermail/omniorb-list/2003-March/023245.html">http://www.omniorb-support.com/pipermail/omniorb-list/2003-March/023245.html</A> that
this is the expected behavior when the size of the message goes over the number
of bytes set by giopMaxMessageSize, which is defaulted to 2 MB.
</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005> <FONT face=Arial
size=2>However, I found the giopMaxMsgSize variable, and I set it as an
environment variable on a Windows 2000 platform to be 10 MB, well over the size
of the particular messages we were trying to pass over the wire, but to no
effect. We are compiling and running against the libraries in
the omniORB-4.0.5-win32-vc6.zip.</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005> <FONT face=Arial><FONT
size=2>For reference, I also set the <FONT face="Courier New"><FONT
face=Arial>maxGIOPVersion = 1.1 in the same way I set giopMaxMsgSize, as an
environment variable, so it would interface with the a JRE 1.3 ORB.
When it is not set, the interface will not work. When it is set, it
will. So I know omniORB can pick up the environment variables from the
place I am setting them. I am wondering if there is a bug with it picking
up this particular variable.</FONT></FONT></FONT></FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005> <FONT face=Arial
size=2>While I am on that note, setting maxGIOPVersion via the environment has
been the only way we were able to get it to work. When we followed the
directions on passing it in as a command line parameter, the threw an error
stating that it did not recognize that parameter. It's not killing us now,
though. Just wondered if you had seen it.</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005> <FONT face=Arial
size=2>Our work around for the large messaging was to find a way to pass
pictures one at a time over the wire. It works, but if omniORB has a bug,
I'm sure you guys would like to know.</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005> <FONT face=Arial
size=2>Let me know if you need more details.</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=405053219-22032005><FONT face=Arial
size=2>Thanks,</FONT></SPAN></DIV>
<DIV><SPAN class=405053219-22032005><FONT face=Arial size=2>John
C</FONT></SPAN></DIV></FONT></DIV></BODY></HTML>