We can not us mod_axis2 module, so we used httpd as proxy server only. When I try the same SOAP request with Apache as proxy server and without tcpmon, I got the same NULL element problem for 226K base64Binary non-optimized data.
case 1) SOAP Request -> Apache Proxy Server -> axis2_http_server (NULL element) case 2) SOAP Request -> Apache Proxy Server -> tcpmon -> axis2_http_server (Works fine) case 3) SOAP Request -> axis2_http_server (NULL element) case 4) SOAP Request -> tcpmon -> axis2_http_server (works fine) Could it be tcpmon can handle TCP packet (1460 bytes/packet) better than axis2_http_server in Axis2C 1.5? Thanks, Ellen On Sun, Feb 22, 2009 at 8:01 AM, Manjula Peiris <manj...@wso2.com> wrote: > This may be related to https://issues.apache.org/jira/browse/AXIS2C-1117 > > BTW, Can you try with httpd without tcpmon ? > > -Manjula. > > > On Sun, 2009-02-22 at 02:14 -0800, Ellen Chou wrote: > > Hi all, > > > > I'm using Axis2C 1.5, and encounter a very strange problem with > > base64Binary. > > > > Case A: I put a 226K bytes file into base64Binary element and send to > > axis2_http_server. Yet when my service gets the element, it is NULL. > > Case B: When I send the same base64Binary to tcpmon and forward to > > axis2_http_server, then it works fine. > > > > In Case A, I use WireShark to monitor the TCP packets. I'm surprised > > to find out that the packets were not sent to axis2_http_server > > completely. Somehow axis2_http_server can't handle the TCP/IP > > handshaking very well in this case. > > > > I saw some email threads regarding to bug fixes for base64Binary to > > handle 58MB data with no problem. If base64Binary can handle 58MB > > data, I don't see any reason it can't handle 226K data. > > > > Any idea would be appreciated. > > > > Thanks, > > Ellen > >
