I had problems with large arrays (about 100.000 items)...
You can try to pass the data attached to the soap message (like e-mail attached files)
Alberto.
-Mensaje original-
De: Senaka Suriyaarachchi [mailto:[EMAIL PROTECTED]
Enviado el: viernes, 06 de agosto de 2004 9:34
Para:
The SOAP communication is Language independent. You can write your client in basic if
you want.
-Mensaje original-
De: matthew.hawthorne [mailto:[EMAIL PROTECTED]
Enviado el: martes, 08 de junio de 2004 3:41
Para: [EMAIL PROTECTED]
Asunto: Re: C++ with Java?
Ding Lei wrote:
> Hello fol
JBoss.NET?
If so, JBoss.NET forum is the right place.
Takenori,
> -Original Message-
> From: Lerena, Alberto [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 25, 2004 4:09 PM
> To: [EMAIL PROTECTED]
> Subject: JBoss Axis Web Service Deployment
>
>
>
> Hi peopl
Hi people,
i have a problem by deploying a web service over a jboss server.
I've deployed it and i can saw the wsdl, but when i try to make a request, i've not
answer...
¿Someone has the same problem?
---
Este mensaje se
Hi Peter,
Obviously the max request size for a GET request is about 256 characters, and that's
really short xD
My error was to think the method getContentLength was going to read the http header
content-length with a low memory cost, but i miss... so i was surprised when i got the
OOM :S
Yes,
Hi Nelson,
The problem is that if I increase the JVM memory, if the request length increases too,
i will have the same problem.
I can't control the request size because "my client" makes it, not me.
:S I saw this solution, but it's more like a temporal dirty patch than a nice
solution.
Thank
idea of how to arrange it, i will be very thankful :D
-Mensaje original-
De: Aleksander Slominski [mailto:[EMAIL PROTECTED]
Enviado el: miércoles, 12 de mayo de 2004 19:33
Para: [EMAIL PROTECTED]
Asunto: Re: SOAP message size limit with Axis
Lerena, Alberto wrote:
>Hi,
>
>I think
Hi,
I think the problem isn't the size of the soap message, but the number of elements it
has.
I had a problem with messages around 1 MB whose were formed by an Array of strings
with 80.000 items, so I had memory DoS problems.
The solution was to implement an Axis Handler to Limit the Request
Hello,
I have an axis web service running over a Tomcat Server. If I make a request to this
service, where there's an arg of type array with around 7 items, the Tomcat goes
out of memory and crashes down.
Is there a way to fix it? A way of limit the request maximum size in the server side
Hi,
I've a problem with an axis deployed webservice. This service is running over a
Tomcat Server and when i make a request of around 700KBytes-1MByte size, the tomcat
fails and shows a "No Memory Exception".
Anybody knows how can i fix this problem? Can i fix it by axis or i should configure
Hello,
I've some problems with an axis web service.
I've generated the client stubs and skeletons with the sun wscompile tool, and when i
try to connect to the WS and get the WSDL to create the service, it's unable to do it.
I suspect it 's because the wsdl:port name is the same as the wsdl:p
11 matches
Mail list logo