=allowedMethods value=*/
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
on the copy command in ant.
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
, struct));
Object result = struct.getObjectValue();
return result;
}
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
the leak?
Thanks
Suzy
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
On Jan 18, 2005, at 10:42 AM, Lyndon Tiu wrote:
The past few days, we did have a few emails regarding memory leaks,
but these were for the client-side.
All my posts over the last few days have been about issues which affect
both the server and the client side.
--
Peter Molettiere
Senior
was the point of Suzy's original post.
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
ignoring the actual
multi-reference. Please, correct me if I am wrong.
Thank you.
Alexander.
On Tue, 14 Dec 2004 15:22:34 -0800, Peter Molettiere
[EMAIL PROTECTED] wrote:
I'm having similar problems, I think. Maybe we can pool our resources?
On Dec 14, 2004, at 2:24 PM, Alexander Sherkin wrote
instead of
myElement.
Looking through DeserializerImpl, I don't see where this happens.
Is this behavior normal? If so, how can I get true localName (i.e.
myElement) from my derserializer?
... I'm not sure about this...
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
that says serialization subsystem docs are
coming.
Thanks in advance!
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
componentQName = context.getQNameForClass(searchCls);
- 144
}
if (componentQName != null) {
componentType = searchCls;
}
}
--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/
Message-
From: Peter Molettiere [mailto:[EMAIL PROTECTED]
Sent: Monday, July 26, 2004 8:39 PM
To: [EMAIL PROTECTED]
Subject: HttpClient and Tomcat: Can someone explain something?
I'm wondering if someone can explain something fairly basic for me.
We're using axis with CommonsHTTPSender
I'm wondering if someone can explain something fairly basic for me.
We're using axis with CommonsHTTPSender in order to get Keep Alive to
work, in preparation for implementing SSL.
I understand how the axis config can control the class which does the
socket handling on the client, but on the
After upgrading to the latest CVS source, we're noticing a new error
being thrown by axis during the execution of our app.
DeserializationContextImpl.getDeserializerForClass():490 - No
deserializer for java.lang.Object
One of the classes we register a type mapping for has a bean property
)
[our application code removed from trace]
--Peter
On Jul 21, 2004, at 7:39 PM, Davanum Srinivas wrote:
do you have a stack trace? please post a bug to JIRA.
thanks,
dims
On Wed, 21 Jul 2004 13:19:52 -0700, Peter Molettiere
[EMAIL PROTECTED] wrote:
After upgrading to the latest CVS source, we're
Jira bug filed:
http://nagoya.apache.org/jira/browse/AXIS-1471
--Peter
On Jul 21, 2004, at 8:28 PM, Peter Molettiere wrote:
Here's a trace, bug in jira coming up:
java.lang.NoSuchMethodException:
java.lang.Object.getDeserializer(java.lang.String, java.lang.Class,
javax.xml.namespace.QName
The out-of-memory during object serialization bug is the single most
important bug fix to our application. Any chance you'll be able to look
at it dims? I know you've been busy with other things since I posted
the test case to jira, but maybe now you can take a look?
I notice it is marked
I've posted a bug to jira with a reproducible test case for the issue
with axis hitting OutOfMemoryErrors during
serialization/deserialization of large object graphs on the server. If
you're running into similar problems, you may want to vote for the bug.
Hey there,
We're trying to use the new streaming option checked into CVS. We're
running into problems however -- we're getting this exception as an
Axis Fault:
org.xml.sax.SAXException: SimpleDeserializer encountered a child
element, which is NOT expected, in something it was trying to
Hey guys,
A quick question.
Buffering the output might not be as memory intensive as building an
in-memory representation of the stream, so there is probably something
to be gained in streaming the response to a buffer.
In our application, we find that serializing our SOAP response causes
OOM
Not technically -- but if it will handle larger message sizes with the
constraints set by the SOAP specification with regards to fault
handling, then it is a step in the right direction.
--Peter
On May 15, 2004, at 3:40 PM, Brian Abbott wrote:
If you where to do that, I dont think it's any
We've been having possibly similar problems, and traced it into axis.
Apparently, axis does a lot of short-term object creation during
serialization, which can result in OutOfMemoryExceptions for reasonably
large data sets (30M), even with -Xmx set to values up to 1.5G. In a
profiler we can
21 matches
Mail list logo
