axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ann Robinson (JIRA)" <>
Subject [jira] Closed: (AXIS2-2967) Reduce memory consumption to alleviate server-side Out-of-memory error
Date Fri, 12 Oct 2007 16:05:50 GMT


Ann Robinson closed AXIS2-2967.

    Resolution: Duplicate

The footprint reduction is not as significant as the WSDL4J Definition object footprint.

Refer to work done for axis2-2968.

> Reduce memory consumption to alleviate server-side Out-of-memory error 
> -----------------------------------------------------------------------
>                 Key: AXIS2-2967
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Ann Robinson
>            Assignee: Ann Robinson
>            Priority: Critical
> In some server-side environments, there is an out-of-memory problem when attempting to
handle a large number of JAXWS-based web service applications.
> In the test scenario that fails, the server is attempting to load and start 100 web service
applications. A variety of heap sizes was tried to see if a heap size for the server could
be found to work, ranging from 1 GB to 4 GB
> Increasing the heap size did not work - the out-of-memory error continued to occur.
> In analyzing the java heap dumps, a big consumer of memory is the DescriptionBuilderComposite
> especially where a wsd4j WSDLDefinition object is held.
> Is it possible to release the DBC objects and/or table of DBC objects to alleviate memory

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message