HTTP chunking is probably already in use, but in any case is unlikely to
make any difference in your memory usage. XMLBeans *always* builds the
document representation in memory - that's just how it's written. The
representation it builds is not as memory-intensive as that used by
WS-Security, but it's still a lot more than the size of the data objects
that are being serialized.
Your other alternative is to use multiple messages to send the data.
Since you have some control over the server side you should be able to
change the interface to allow multiple calls to the same operation. This
would allow you to just break up the data into multiple requests when it
gets beyond a certain size (perhaps 20000 objects, or whatever number
makes sense). Maybe this is what you meant by the reference to chunking?
- Dennis
Sudhir Mongia wrote:
Hi Dennis,
Thanks for your reply, Sorry I missed to thanks you in my previous
email, I was slightly inside the problem.
Just to add here we are also thinking of using another approaches like
http chunking.
Thanks,
Sudhir
On Wed, May 6, 2009 at 10:12 AM, Sudhir Mongia
<[email protected] <mailto:[email protected]>> wrote:
Hi Dennis,
We are not using WS-Security. Still its paining us.
The problem we are facing is memory consumption while serialization.
We are using xmlbeans databinding, we couldn't go for ADB as it
doesn't supports Complex type extension and restrictions and we
have not evaluated other binding options as of now.
Thanks,
Sudhir
On Wed, May 6, 2009 at 3:01 AM, Dennis Sosnoski <[email protected]
<mailto:[email protected]>> wrote:
Hi Sudhir,
Are you using WS-Security for the service? WS-Security builds
an in-memory model of the XML if you're using signatures (and
perhaps at other times - I haven't checked, but there appeared
to be some issues in this area).
If you're not using WS-Security this type of data should not
be causing problems. What data binding approach are you using?
(ADB, XMLBeans, JiBX, JAXB?)
- Dennis
--
Dennis M. Sosnoski
SOA and Web Services in Java
Axis2 Training and Consulting
http://www.sosnoski.com - http://www.sosnoski.co.nz
Seattle, WA +1-425-939-0576 - Wellington, NZ +64-4-298-6117
Sudhir Mongia wrote:
Hi,
Has anyone got any experience in this type of problem ?
One possible solution we used temporarily is, pass data
fragment in in a call and do multiple calls to send the
complete data.But we are reluctant to go with this
approach in production.
Any help/pointer ?
Thanks,
Sudhir
On Mon, May 4, 2009 at 2:23 PM, Sudhir Mongia
<[email protected] <mailto:[email protected]>
<mailto:[email protected]
<mailto:[email protected]>>> wrote:
Hi,
We have a web method exposed by .net app and we using
client stubs
generated through Axis2. This method accepts an array
of objects.
The object is very heavy object containing 25+ members
variables
of double and string type.
The calls to this method fails sometimes due to memory
when we are
trying to send large number of objects e.g. 100000-200000.
Any suggestions/idea , how can we compress the size of
data to fix
this problem? We have control up to some extent on
server side as
well.
Thanks,
Sudhir
