axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (AXIS-1567) Client out of memory exception calling webservice with a return string > 1MB
Date Wed, 22 Sep 2004 11:04:37 GMT
The following comment has been added to this issue:

     Author: Guenther Zwetti
    Created: Wed, 22 Sep 2004 4:03 AM
Sorry, but there is an error in my source code fragment listing:
instead of service.loadInventors(2003) the original source
of course contains the lines service.loadPerosns(2003) and
then causes the described out-of-memory exception.

Are there any ideas how this could happen (I've already set more
memory for vm and when I measure available mem, there must be more than enough - nevertheless,
this error occurs)

Please give me a hint.
Btw: I'm new here and so I'm not sure, whether this is the correct place to discuss/report
the problem mentioned above. So if it's not
correct, please tell me or tell me newsgroups for this problem.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1567
    Summary: Client out of memory exception calling webservice with a return string > 1MB
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: Axis
             Basic Architecture

   Reporter: Guenther Zwetti

    Created: Wed, 22 Sep 2004 3:55 AM
    Updated: Wed, 22 Sep 2004 4:03 AM
Environment: winxp

I have implemented a very simple webservice which produces
a String return value holding a special XML structure.
The length of this string is about 900kB. When I return this string
the client throws an out of memory exception.
The stubs for the client have been created with wsdl2java.
Are there any size limitations?


	public String loadPersons(int year) {
          // produces a string with size > 1MB
          return myString


	ServiceXLocator location = new ServiceXLocator();
	try {
	   ServiceX service = location.getServiceX(new URL(LOC));	String x = service.loadInventors(2003);

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message