Hi Vikas,
An OutOfMemoryError strongly suggests that cacheAttachments or one of the
other 3 associated properties are not being set properly. On the client
side, for receiving the file, one can code:
Options options = new Options();
options.setTo(new EndpointReference(url));
There is a known bug with MTOM attachments in Axis 1.1.1, fixed in Axis 1.2.
-Original Message-
From: Jochen Zink [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 23, 2007 1:19 AM
To: axis-user@ws.apache.org
Subject: Re: MTOM error java.lang.OutOfMemoryError: Java heap space
Hi Vikas,
Michele -
I don't know if this will help, but I modify values in the AxisConfiguration
using code like this:
MessageContext msgContext = MessageContext.getCurrentMessageContext();
AxisConfiguration axisConfig = msgContext.getConfigurationContext()
.getAxisConfiguration();
Parameter param =
:[EMAIL PROTECTED]
Sent: Thursday, March 29, 2007 8:34 AM
To: axis-user@ws.apache.org
Subject: RE: [Axis2] ConfigurationContext configuration
Betsy,
thanks. However I would like to change the parameters on the client
side.
Any clue?
Michele
On Thu, 2007-03-29 at 08:13 -0700, Betsy Frey wrote
Both problems below seem to be fixed by Axis2-1.2-RC1.
Thilina was right when he guessed I had not replaced all the jars when I
said I had tested with RC1.
Betsy
-Original Message-
From: Thilina Gunarathne [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 27, 2007 12:12 PM
To:
I have some MTOM sample code in which a client sends all files in its
transfer directory to a service. The server sends the files back to the
client, which stores them in its received directory, and does a
byte-to-byte compare to make sure the files in the two directories match.
1. Sometimes 1
in
the range of ~6.5 MB/s, which translates in to 375 to 400 MB/Min..
My environments is Ubuntu Linux 6.10
java version 1.5.0_10
file system: ext3
Apache Tomcat 5.5.20
FileCacheThreshold 4 bytes
The program I used was the SoapWithAttachments sample of Axis2.
Thanks,
Thilina
On 3/20/07, Betsy Frey
/jars/axi
om-impl-SNAPSHOT.jar
On 3/19/07, Betsy Frey [EMAIL PROTECTED] wrote:
Thanks, Rodirigo, but the problem is not my disks.
I changed the code to generate bytes on the fly, instead of from a
source file. I changed the reference from localhost to 127.0.0.1.
I am
just looking
I've just made some measurements, transferring files using MTOM in Axis2
on tomcat. My client and servlet are on the same machine. Attachments
are cached. For files of 1mb or more, the transfer rate,
client-to-servlet, is about 3.7mb per minute. In contrast, a file
system copy transfers at
to move the file in the server side to
its final location instead of copying it. The performance is totally
different.
Hope this helps you,
Rodrigo Ruiz
Betsy Frey wrote:
I've just made some measurements, transferring files using MTOM in
Axis2
on tomcat. My client and servlet are on the same
In Axis 1.4, you can use code like this:
boolean isClientLocal = true;
MessageContext msgContext =
MessageContext.getCurrentContext();
String remoteIP =
msgContext.getStrProp(org.apache.axis.Constants.MC_REMOTE_ADDR);
if
To use eclipse to debug a tomcat servlet:
1. Be sure that tomcat is started with the below. One way to do that is to
edit tomcat/bin/catalina.bat, where JAVA_OPTS is defined.
-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
2. Set a breakpoint in the servlet code.
whether SAX or DOM is used for XML
parsing in Axis2.
Thanks.
Betsy Frey
**
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed. Any
One does not have to use an ImageDataSource or FileDataSource. You can code
your own DataSource, implementing javax.activation.DataSource.
When receiving MTOM data, one gets a DataHandler from the OMText element, and
one can get the input stream from that:
OMText data = (OMText)
Hi Thilina,
Are you using the Axis2 tip? I ask because when I use MTOM in Axis2 v
1.0, with file caching on, transferring 1gb of data causes my tomcat
5.5.17 server to see: java.lang.OutOfMemoryError: Java heap space.
Thanks,
Betsy
-Original Message-
From: Thilina Gunarathne
-
From: Betsy Frey
Sent: Saturday, September 16, 2006 3:29 AM
To: 'axis-user@ws.apache.org'
Subject: RE: Axis using more than 256MB for a 9MB file
Hi Thilina,
Are you using the Axis2 tip? I ask because when I use MTOM in Axis2 v
1.0, with file caching on, transferring 1gb of data causes my
SOAP without an attachment is inappropriate for sending large amounts of binary
data, because the XML requires it to be converted to Base64, which is
inefficient.
With an attachment, SOAP over http has the overhead of the protocol, which is
not as fast as ftp, for instance.
I have used DIME
to send large files with axis2 ?
I get fast always broken pipe exception.
German Sakaryan
Betsy Frey schrieb:
SOAP without an attachment is inappropriate for sending large amounts
of binary data, because the XML requires it to be converted to Base64,
which is inefficient.
With an attachment, SOAP
Is there a way in which Axis 2 will allow the client to
start receiving the response while the server is still adding children to the
SOAP response?
Thanks you.
Betsy Frey
**
This email and any files
19 matches
Mail list logo
