axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jerry Hong" <Je...@digitalfoundry.com>
Subject RE: Buffer Size Problem?
Date Fri, 28 Feb 2003 23:07:20 GMT
Maybe I didn't understand the question... So If I am talking about
something else, please ignore ;)

 

Since I am new to axis, I don't know any service related buffer problem,
but I have seen problem regarding StringBuffer.

I do not remember the limit, but StringBuffer had some bug.  If you are
using StringBuffer, you might want to look into that.

Otherwise, ignore like I said ;)

 

-----Original Message-----
From: Betsy Frey [mailto:Betsy.Frey@merant.com] 
Sent: Friday, February 28, 2003 2:51 PM
To: axis-user@ws.apache.org
Subject: RE: Buffer Size Problem?

 

I've seen a problem sending a DIME attachment over the DIME limit of
2^32-1 bytes.  Axis ought to automatically chunk into an additional
attachment, but it doesn't seem to do so.  I have successfully sent DIME
attachments just under that limit.

Betsy 

-----Original Message----- 
From: Phee, Martin J (Jump Tech) [mailto:Marty.Phee@bp.com] 
Sent: Friday, February 28, 2003 2:41 PM 
To: 'axis-user@ws.apache.org' 
Subject: RE: Buffer Size Problem? 

 

I'm sending 85k+ using a byte[] without any problems.  10k really isn't
much. 

-----Original Message----- 
From: Roy Wood [mailto:roy.wood@filogix.com] 
Sent: Friday, February 28, 2003 3:36 PM 
To: axis-user@ws.apache.org 
Subject: Buffer Size Problem? 

 

I'm sending a big chunk of text to my Axis-based service, and have run 
into problems when the total size gets too big (over 10k, I think). 

Is anyone aware of any sort of hard-coded buffer size limits that may be

a problem? 

 

-Roy 

 

"Disclaimer - The opinions expressed in this message are strictly 
personal and do not necessarily reflect those of FiLogix." 

Notice: This email transmission and/or the attachments accompanying it
may contain confidential information belonging to Merant. The
information is only for the use of the intended recipient. If you have
received this transmission in error, please notify the sender
immediately by reply email, and then destroy all copies of the
transmission.


Mime
View raw message