Title: Axis 1.1 Memory leaks
Hi,
I have succesfully deployed a web service which main function is to exchange small/medium files between two Axis instances.
I'm using wsdl/wsdd generation and everything work smooth (a part from some known workarounded Axis problems).
Last week we did some
it find it :
# ldd /usr/local/apache/libexec/libaxiscpp_mod.so
libxerces-c.so.25 => /usr/lib/libxerces-c.so.25 (0x40076000)
libdl.so.2 => /lib/libdl.so.2 (0x403fc000)
libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0x4040)
libc.so.6 => /lib/libc.so.6 (0x404b9000)
I take from the lack of response that the answer to this question
is no unless I extend AXIS?
Stuart Barlow wrote:
Is there a way to automatically map javadoc to tags
in AXIS 1.1?
Or in AXIS 1.2?
Thanks,
Stuart.
hello
Sorry if this question is too much NTG
I am going thru jax-rpc spec, and came across something that is not clear
"During the deployment of a service endpoint component on a servlet
container based
JAX-RPC runtime system, a service endpoint class is associated with a
servlet. The
associa
unfortunately...yes
--- Stuart Barlow <[EMAIL PROTECTED]> wrote:
> I take from the lack of response that the answer to this question
> is no unless I extend AXIS?
>
> Stuart Barlow wrote:
> > Is there a way to automatically map javadoc to tags
> > in AXIS 1.1?
> >
> > Or in AXIS 1.2?
> >
> >
A simple proxy service can be found at /samples/proxy . if the code is
modified to set an alternative transport on the outbound call, you would
have a gateway.
/Chris
-Original Message-
From: Biörn Biörnstad [mailto:[EMAIL PROTECTED]
Sent: Friday, February 20, 2004 7:44 AM
To: [EMAIL
Hi ya,
when passing parameters for method call, do the parameters have to be in
the right order that is defined on the services side? e.g. there is a web
service method "helloWorld(String forename, String surname)", can i pass the
parameters in the order of 'surname' then 'forename' or does
Hello *,
I'm looking axis .jws files but I don't understand why this
code-snippet don't work...
If I change
out.toString();
in
((ByteArrayOutputStream).out).size();
it works perfectly :(
Seems to have some problems with fop
I need only to generate a pdf from a Xml+Xsl-fo urls
some h
Hey Stuart,
AXIS uses reflection to generate the WSDL. As such, it does not have
access to the JavaDoc, which is only contained within the Java source.
What we have done is place our documentation within a seperate XML file,
then we have a seperate servlet which merges this documentation with th
>when passing parameters for method call, do the parameters have to be in
>the right order that is defined on the services side?
For all practical purposes, in SOAP the parameters have to be in the
same order as the service expects. I believe that in theory the SOAP
spec allows for out-of-order p
>Last week we did some heavy testing on the web service and we
>discovered that we cannot send documents bigger than 1.5Mb. Axis
>fails with a OutOfMemory exception.
How are you encoding the file you're sending? Is it some sort of SOAP
attachment, or is it an element in the query?
Your most direc
Title: [newbie] Axis implementation of JAXM and SAAJ
Hi,
Can someone please tell me which version of JAXM and SAAJ that AXIS is implementing?
I compare the API in the saaj.jar in the AXIS distribution with the saaj-api.jar in JWSDP 1.3, they look different.
Thanks in advance for any help.
FWIW, we run with an initial heap size of 256MB and a max heap size of
512MB, and that seems to work pretty welll...
HTH,
Ian
Nelson Minar
Title: RE: Axis 1.1 Memory leaks
Hi Nelson,
the problem that I'm experiencing is related to some (known?) Axis problem to
handle large xml documents.
In fact, I'm sending back and forth binary files or large xml files (2.5Mb) without using the SAAJ specification or the code used in the /sa
Title: RE: Axis 1.1 Memory leaks
Hi Ian,
increasing the heap size is a risky solution in my opinion, because (at least in my case)
I will never know when the memory will be enough to handle my large xml document.
I believe that there is some inefficiency in Axis code when it comes to handl
Parul,
Are you trying to embed an XML document string in your request. If yes, did
you check if your DOM tree has been formed correctly. I mean try validating
it against the schema and see if it is well-formed.
HTH,
Vivek
From: [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED
Hi Richard,
I tried implementing a web service which returns an XML document. I am not
sure if you could return an XML "Document" object directly but what I did
was serialized the XML DOM tree to a string and returned it. It worked fine!
If you need further information, do email the list
HTH,
According to the FAQ http://ws.apache.org/soap/faq/ (How do you return a
DOM Element from an RPC Call? ) You can return a DOM Element... As
well according to an IBM paper "Exploring Apaches serialzation APIs"
http://www-106.ibm.com/developerworks/webservices/library/ws-soapmap1/ -
If
Since I didn't get any response I thought I should try again.
I have a webservice that accepts as input some string parameters and also an
attachment. The attachment is a ascii file.
The webservice then returns back another attachment as a response.
The service works fine , I am able to send back
>the problem that I'm experiencing is related to some (known?) Axis problem to
>handle large xml documents.
Understood. Does anyone have a simple benchmark that shows how much
memory Axis consumes as a function of the size of the SOAP messages?
>In fact, I'm sending back and forth binary files or
Title: RE: Axis 1.1 Memory leaks
I actually found a solution to the memory inefficiency problem.
It is kind of tricky, so this mail will be a little verbose...
1)
*Original* interface exposed as webservice:
public String doSomething(ExecutionArgumentTO to) { ... }
where Executi
Title: RE: Axis 1.1 Memory leaks
>I suspect you'll find many SOAP environments have a hard time with
>this. If you're sending giant data, attachments are likely to be more
>efficient. But attachments have interop troubles, and they're not
>objects. I'd like to be able to send arrays of 100
Luciano,
Just curious regarding your proposed solution. Since you are using a
DataHandler as an input parameter to the service which is a Java API, if you
had a non Java client (like .NET client) access this service, how does one
do it?
Any ideas
-regards,
kumar
> -Original Message
Here is the feedback I got from the list, in regard of basic profile:
Attachments were left out of BP 1.0 with the statement they'd be covered
in 1.1. The WS-I site (http://www.ws-i.org/) now has both a BP 1.1
Working Draft and an Attachments Profile 1.0 Working Draft that the
former references.
The DataHandler type is Axis proprietary, it won't work with .Net client.
This type is used by wsdl2java.
It will work unless you have another tool that recognize this type and
generate .Net stub. It would be
nice to have such tool though.
That is based on what I understand and experienced couple
This clears the MessageContext's bag of user-defined goodies, namely the
HTTPConstants.REQUEST_HEADERS property that can specify tokens for the http
header. Please, can an axis dev explain the reason(s) behind this? Or at
least tell me what I am misunderstanding?
Cheers,
Christoph
Hi all,
The Axis serialization framework is
not tightly controlled to be part of the SOAP envelope
only.
I have tested it using the codes below
MessageContext msgContext0 = new MessageContext(new AxisServer());
Writer stringWriter = new StringWriter(); Serializati
The problem was with the Date and time, Axis was trying to use the Calendar Serializer and de-serializer, but I think the format of the incoming data was a bit weird hence it could not deserialize it correctly, I changed it to be a "String" and it worked.. partially .
Now the problem that I am ru
Dear Axis Users,
I tried to deploy Axis 1.1 to Tomcat 5 ( provided with Web Service
Developer Pack 1.3 ) by copying the webapps/axis directory from Axis
installation to Tomcat webapps directory. After starting Tomcat, I could
not find the start page, 127.0.0.1:8080/axis. When I try to start ax
Hi All,
I had a simple axis service installed on Tomcat and everything was
working fine. We do not use any custom ser's / de-ser's . Suddenly I am
seeing this error pop up.
Am I missing anything?? Thank you all for your time and help.
Exception in thread "main" AxisFault
faultCode: {http://s
Hi!
> > >after compilation and instalation, I've this error with Apache:
> > >
> > ># /usr/local/apache/bin/apachectl start
> > >Syntax error on line 946 of /usr/local/apache/conf/httpd.conf:
> > >Cannot load /usr/local/apache/libexec/libaxiscpp_mod.so into server:
> > >/usr/local/apache/libexec/l
Hi!
>I tried to deploy Axis 1.1 to Tomcat 5 ( provided with Web Service
> Developer Pack 1.3 ) by copying the webapps/axis directory from Axis
> installation to Tomcat webapps directory. After starting Tomcat, I could
> not find the start page, 127.0.0.1:8080/axis. When I try to start axis
>
On Tue, 24 Feb 2004, Srinivas Vemula wrote:
> Hi All,
> I had a simple axis service installed on Tomcat and everything was
> working fine. We do not use any custom ser's / de-ser's . Suddenly I am
> seeing this error pop up.
> Am I missing anything?? Thank you all for your time and help.
>
>
-Original Message-
From: Kay Chee Cheung [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 24, 2004 10:21 AM
To: [EMAIL PROTECTED]
Subject: Problem in deploying Axis 1.1 to Tomcat 5
Dear Axis Users,
I tried to deploy Axis 1.1 to Tomcat 5 ( provided with Web Service
Developer Pack 1.
Hi,
Thanks very much for the hints. I look at the log file,
launcher.server.log. I found the following entry related to the failure
to deploy Axis :-
23/02/2004 13:17:09 org.apache.catalina.core.StandardHostDeployer
install
INFO: Installing web application at context path /servlets-examples
f
Hi!
> INFO: Installing web application at context path /axis from URL
> file:C:\jwsdp-1.3\webapps\axis
>
> 23/02/2004 13:17:09 org.apache.catalina.core.StandardContext start
>
> SEVERE: Error listenerStart
>
> 23/02/2004 13:17:09 org.apache.catalina.core.StandardContext start
>
> SEVERE: Context s
36 matches
Mail list logo
