You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ann Robinson (JIRA)" <ji...@apache.org> on 2007/07/15 23:48:04 UTC
[jira] Created: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
-----------------------------------------------------------------
Key: AXIS2-2968
URL: https://issues.apache.org/jira/browse/AXIS2-2968
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Components: kernel
Reporter: Ann Robinson
Assignee: Ann Robinson
Priority: Critical
Fix For: 1.3
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, one of the biggest consumers of the memory
is with the wsdl4j WSDLDefinition objects. In the test scenario, the
wsdl4j-related objects consumed about a quarter to a third of the entire heap.
The WSDLDefinition object is a very heavy-weight object, much of which stems
from its use of the xerces dom objects as underlying support, particularly
for the schemas.
One area to investigate is the saving of the WSDLDefinition as a Parameter
in the AxisService's ParameterInclude list so that, if some component needs
to utilize the WSDLDefinition object, it can be accessed via the AxisService
object.
Is it possible to reduce the utilization of the WSDLDefinition?
Some ideas are:
(a) releasing it when it is no longer needed
- this might not be possible to determine
(b) putting a wrapper on the WSDLDefinition
- so that the WSDLDefinition,or a portion of the WSDLDefinition,
can be released
- but if the WSDLDefinition is accessed after it was released,
the wrapper can reload the WSDLDefinition transparently to the
user
(c) create a layer for caching wsdl-related information
- this would allow for releasing memory based on some algorithm
and/or interface that could indicate what's no longer needed
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davanum Srinivas updated AXIS2-2968:
------------------------------------
Fix Version/s: (was: 1.3)
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Tom Seelbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Seelbach updated AXIS2-2968:
--------------------------------
Attachment: patchViaSVNdiff.txt
same code changes as patch-5.txt, produced using svn diff. Note that the last 2 files in the diff (axis2.xml and the testcase) were diffed with /dev/null since they are new files.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch-5.txt, patch_01.txt, patch_02_part1.txt, patch_03.txt, patchViaSVNdiff.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Amila Chinthaka Suriarachchi (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Chinthaka Suriarachchi updated AXIS2-2968:
------------------------------------------------
Attachment: wsdlFromFileSystem.patch
here is an another option for this problem.
we keep wsdl4j object structure in memory to show the wsdl file to the user when they request with ?wsdl.
So if we can display the wsdl file without keeping the wsd4j definition then there is not need to keep the
wsdl4j object and hence solve the problem.
Here is the way I suggest to display the wsdl.
For the moment wsdl file is kept in the aar file and here I am suggesting to let users to keep them in a
seperate folder. This allows them to an directory hiarachy to manage the wsdl files.
To get the wsdl location we can use two parameters.
1. wsdlBaseUri used in axis2.xml to keep the base uri location
2. wsdlFileLocation used in service.xml keep the exact wsdl location.
Here is the way.
When the first request comes ?wsdl, Axis2 redirect the request giving the wsdl location
This is done by adding the wsdl file path to the contextRoot and serviceName.
i.e.
AxisService axisServce = (AxisService) serviceObj;
Parameter wsdlFileLocationParameter = axisServce.getParameter("wsdlFileLocation");
if (wsdlFileLocationParameter != null){
String wsdlLocation = (String) wsdlFileLocationParameter.getValue();
String redirectUrl = null;
if (configContext.getServiceContextPath().endsWith("/")){
redirectUrl = configContext.getServiceContextPath()
+ serviceName + "/" + wsdlLocation;
} else {
redirectUrl = configContext.getServiceContextPath()
+ "/" + serviceName + "/" + wsdlLocation;
}
res.sendRedirect(redirectUrl);
}
then when the requests come to show the wsdl and xsd files Axis2 can simply append the file path to
the base uri and get that from the file system.
String uri = req.getRequestURI();
String contextPath = configContext.getServiceContextPath();
String servicePart = null;
if (configContext.getServiceContextPath().endsWith("/")){
servicePart = uri.substring(uri.indexOf(contextPath) + contextPath.length());
} else {
servicePart = uri.substring(uri.indexOf(contextPath) + contextPath.length() + 1);
}
String serviceName = servicePart.substring(0, servicePart.indexOf("/"));
String filePath = servicePart.substring(servicePart.indexOf("/") + 1);
AxisService axisServce = configContext.getAxisConfiguration().getService(serviceName);
Parameter wsdlFileLocationParameter = axisServce.getParameter("wsdlFileLocation");
if (wsdlFileLocationParameter != null) {
//i.e we have the wsdl file locator
Parameter wsdlBaseUriParameter =
configContext.getAxisConfiguration().getParameter("wsdlBaseUri");
if (wsdlBaseUriParameter != null) {
String wsdlBaseUri = (String) wsdlBaseUriParameter.getValue();
String fileToRead = wsdlBaseUri + filePath;
// read and send the file
InputStream fileInputStream = new FileInputStream(fileToRead);
if (fileInputStream != null) {
OutputStream out = res.getOutputStream();
res.setContentType("text/xml");
ListingAgent.copy(fileInputStream, out);
out.flush();
out.close();
return;
}
}
}
I have attached the complete patch for the same jira.
This works fine when the wsdl file is viewed from the browser. Browsers can handle redirect correctly.
The problem is when I try to generate the code for this using wsdl2java tool it does not work since,
wsdl4j can not handle redirects properly.
if I give the url directly to the wsdl without using the ?wsdl it works fine.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WS invocation problem
Posted by Saminda Abeyruwan <sa...@gmail.com>.
Hi All,
I've observe this behavior too. If service is returing a
NullPointerException as checked or unchecked, the soap fault reason comes as
"unknown", is this the norm way of handling NPE of service.
Thank you,
Saminda
On 7/22/07, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi Ecker,
>
> First it could have been better if you sent this mail to users list.
>
> Anyway, can you send us the request messages from Axis2 (whatever the
> succesfull version) and from SOAP client? You might already know that
> you can intercept SOAP messages using a tool like tcpmon.
>
> Chinthaka
>
> Ecker Severin wrote:
> > Hi,
> >
> > I have the following setup:
> > Tomcat 5.5, axis2 (versions 1.1.1, 1.2 and snapshot), java 1.6.0_02
> > (which was used for the WS I've written and is used to run tomcat)
> >
> > The webservice exposes a method with a parameter (MethodRequest). Now
> > I'm facing the following problem:
> >
> > The request is as simple as this:
> >
> > <soap:Envelope
> > xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> > xmlns:ns="http://my.org/WS/types/1.0">
> > <soap:Header/>
> > <soap:Body>
> > <ns:MethodRequest/>
> > </soap:Body>
> > </soap:Envelope>
> >
> > Using the sendReceive method of the ServiceClient class (in the axis2
> > lib) the method invocation works just fine.
> >
> > BUT using a soap client (such as SOAPui) I get different kinds of error
> > responses depending on the version of axis2 that I'm using
> >
> > Errors:
> >
> > Axis2 1.1.1:
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> > <soapenv:Header/>
> > <soapenv:Body>
> > <soapenv:Fault>
> > <soapenv:Code>
> > <soapenv:Value>soapenv:Sender</soapenv:Value>
> > </soapenv:Code>
> > <soapenv:Reason>
> > <soapenv:Text xml:lang="en-US">null; nested exception is:
> > java.lang.NullPointerException</soapenv:Text>
> > </soapenv:Reason>
> > <soapenv:Detail/>
> > </soapenv:Fault>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> >
> > Axis2 1.2:
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> > <soapenv:Body>
> > <soapenv:Fault>
> > <soapenv:Code>
> > <soapenv:Value>soapenv:Sender</soapenv:Value>
> > </soapenv:Code>
> > <soapenv:Reason>
> > <soapenv:Text xml:lang="en-US">unknown</soapenv:Text>
> > </soapenv:Reason>
> > <soapenv:Detail/>
> > </soapenv:Fault>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> >
> > Axis2 snapshot:
> >
> > <soapenv:Envelope
> > xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> > <soapenv:Body>
> > <soapenv:Fault>
> > <soapenv:Code>
> > <soapenv:Value>soapenv:Sender</soapenv:Value>
> > </soapenv:Code>
> > <soapenv:Reason>
> > <soapenv:Text
> > xml:lang="en-US">org.apache.axis2.AxisFault.makeFault(Ljava/lang/Excepti
> > on;)Lorg/apache/axis2/AxisFault;</soapenv:Text>
> > </soapenv:Reason>
> > <soapenv:Detail/>
> > </soapenv:Fault>
> > </soapenv:Body>
> > </soapenv:Envelope>
> >
> >
> > Also the TRACE output of axis2 does not give me ANY clue about what's
> > going on (I have the traces here, but before bloating the post with a
> > huge logfile I'll just wait and see if someone can shed some light on
> > what's going on) What I can tell is that my service implementation never
> > receives the method invocation request but the axis/soap handling
> > mechanisms throw the exception beforehand. (oh and yes it's SOAP 1.2)
> >
> > My thanks in advance!
> >
> > Cheers,
> > severin
> >
> >
> > -------------
> > Severin Ecker
> > Business Unit Software Systems
> > Smart Systems Division
> > Austrian Research Centers GmbH - ARC
> > 2444 Seibersdorf
> > T: + 43 (0) 50 550 - 3122
> > M: + 43 (0) 664 60780 3122
> > F: + 43 (0) 50 550 - 2813
> > mailto:severin.ecker@arcs.ac.at
> > www.smart-systems.at
> > HG Wien - FN 115980i - ATU14703506
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGo5NDjON2uBzUhh8RAjw0AKCHSyYN5SN1XyeDuuCXwbubBOUe1ACfSv2P
> NRUmvnCYqlDqFVCmCphYKyc=
> =EDo1
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Saminda Abeyruwan
Software Engineer
WSO2 Inc. - www.wso2.org
AW: WS invocation problem
Posted by Ecker Severin <Se...@arcs.ac.at>.
Hi,
Doing some debugging I found out that the errors I've stated are produced when the service implementation throws an exception.
(while unknown might be true, changing the message to something that hints a problem in the service implementation might help error tracing)
Cheers and thanks,
severin
ps.: I did send this to the users mailing list but got no reply at all so I figured I might try it here, especially since I figured that the axis decs would know a lot better where 'unknown' might come from in the source.
-----Ursprüngliche Nachricht-----
Von: Eran Chinthaka [mailto:chinthaka@opensource.lk]
Gesendet: Sonntag, 22. Juli 2007 19:26
An: axis-dev@ws.apache.org
Betreff: Re: WS invocation problem
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ecker,
First it could have been better if you sent this mail to users list.
Anyway, can you send us the request messages from Axis2 (whatever the
succesfull version) and from SOAP client? You might already know that
you can intercept SOAP messages using a tool like tcpmon.
Chinthaka
Ecker Severin wrote:
> Hi,
>
> I have the following setup:
> Tomcat 5.5, axis2 (versions 1.1.1, 1.2 and snapshot), java 1.6.0_02
> (which was used for the WS I've written and is used to run tomcat)
>
> The webservice exposes a method with a parameter (MethodRequest). Now
> I'm facing the following problem:
>
> The request is as simple as this:
>
> <soap:Envelope
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> xmlns:ns="http://my.org/WS/types/1.0">
> <soap:Header/>
> <soap:Body>
> <ns:MethodRequest/>
> </soap:Body>
> </soap:Envelope>
>
> Using the sendReceive method of the ServiceClient class (in the axis2
> lib) the method invocation works just fine.
>
> BUT using a soap client (such as SOAPui) I get different kinds of error
> responses depending on the version of axis2 that I'm using
>
> Errors:
>
> Axis2 1.1.1:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header/>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">null; nested exception is:
> java.lang.NullPointerException</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Axis2 1.2:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">unknown</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Axis2 snapshot:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text
> xml:lang="en-US">org.apache.axis2.AxisFault.makeFault(Ljava/lang/Excepti
> on;)Lorg/apache/axis2/AxisFault;</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Also the TRACE output of axis2 does not give me ANY clue about what's
> going on (I have the traces here, but before bloating the post with a
> huge logfile I'll just wait and see if someone can shed some light on
> what's going on) What I can tell is that my service implementation never
> receives the method invocation request but the axis/soap handling
> mechanisms throw the exception beforehand. (oh and yes it's SOAP 1.2)
>
> My thanks in advance!
>
> Cheers,
> severin
>
>
> -------------
> Severin Ecker
> Business Unit Software Systems
> Smart Systems Division
> Austrian Research Centers GmbH - ARC
> 2444 Seibersdorf
> T: + 43 (0) 50 550 - 3122
> M: + 43 (0) 664 60780 3122
> F: + 43 (0) 50 550 - 2813
> mailto:severin.ecker@arcs.ac.at
> www.smart-systems.at
> HG Wien - FN 115980i - ATU14703506
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGo5NDjON2uBzUhh8RAjw0AKCHSyYN5SN1XyeDuuCXwbubBOUe1ACfSv2P
NRUmvnCYqlDqFVCmCphYKyc=
=EDo1
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WS invocation problem
Posted by Eran Chinthaka <ch...@opensource.lk>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Ecker,
First it could have been better if you sent this mail to users list.
Anyway, can you send us the request messages from Axis2 (whatever the
succesfull version) and from SOAP client? You might already know that
you can intercept SOAP messages using a tool like tcpmon.
Chinthaka
Ecker Severin wrote:
> Hi,
>
> I have the following setup:
> Tomcat 5.5, axis2 (versions 1.1.1, 1.2 and snapshot), java 1.6.0_02
> (which was used for the WS I've written and is used to run tomcat)
>
> The webservice exposes a method with a parameter (MethodRequest). Now
> I'm facing the following problem:
>
> The request is as simple as this:
>
> <soap:Envelope
> xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
> xmlns:ns="http://my.org/WS/types/1.0">
> <soap:Header/>
> <soap:Body>
> <ns:MethodRequest/>
> </soap:Body>
> </soap:Envelope>
>
> Using the sendReceive method of the ServiceClient class (in the axis2
> lib) the method invocation works just fine.
>
> BUT using a soap client (such as SOAPui) I get different kinds of error
> responses depending on the version of axis2 that I'm using
>
> Errors:
>
> Axis2 1.1.1:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Header/>
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">null; nested exception is:
> java.lang.NullPointerException</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Axis2 1.2:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text xml:lang="en-US">unknown</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Axis2 snapshot:
>
> <soapenv:Envelope
> xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
> <soapenv:Body>
> <soapenv:Fault>
> <soapenv:Code>
> <soapenv:Value>soapenv:Sender</soapenv:Value>
> </soapenv:Code>
> <soapenv:Reason>
> <soapenv:Text
> xml:lang="en-US">org.apache.axis2.AxisFault.makeFault(Ljava/lang/Excepti
> on;)Lorg/apache/axis2/AxisFault;</soapenv:Text>
> </soapenv:Reason>
> <soapenv:Detail/>
> </soapenv:Fault>
> </soapenv:Body>
> </soapenv:Envelope>
>
>
> Also the TRACE output of axis2 does not give me ANY clue about what's
> going on (I have the traces here, but before bloating the post with a
> huge logfile I'll just wait and see if someone can shed some light on
> what's going on) What I can tell is that my service implementation never
> receives the method invocation request but the axis/soap handling
> mechanisms throw the exception beforehand. (oh and yes it's SOAP 1.2)
>
> My thanks in advance!
>
> Cheers,
> severin
>
>
> -------------
> Severin Ecker
> Business Unit Software Systems
> Smart Systems Division
> Austrian Research Centers GmbH - ARC
> 2444 Seibersdorf
> T: + 43 (0) 50 550 - 3122
> M: + 43 (0) 664 60780 3122
> F: + 43 (0) 50 550 - 2813
> mailto:severin.ecker@arcs.ac.at
> www.smart-systems.at
> HG Wien - FN 115980i - ATU14703506
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGo5NDjON2uBzUhh8RAjw0AKCHSyYN5SN1XyeDuuCXwbubBOUe1ACfSv2P
NRUmvnCYqlDqFVCmCphYKyc=
=EDo1
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
anonymous operation invocation
Posted by Ecker Severin <Se...@arcs.ac.at>.
Hi,
//this has been sent to the axis-users list before with no feedback
I think I stumbled over a bug but I wanted to check here first in case
I'm just being stupid.
I have a webservice (using axis2 to handle the soap stuff) and I wanted
to use this service with both, WSDL-based access and anonymous operation
invocation (with the ServiceClient.sendReceive(OMElement elem) method).
Using WSDL base access everything works as intended (e.g.: using the
following SOAP envelope)
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns="http://myNS.com">
<soap:Header/>
<soap:Body>
<ns:GetCapabilitiesRequest/>
</soap:Body>
</soap:Envelope>
At service implementation site within the method
getCapabilities(OMElement e); (<-- this is the invoked method)
the parameter e is
<ns:GetCapabilitiesRequest/>
So far so good.
Now when trying to access anonymously I have to encode the operation
somewhere so I have the following envelope
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns="http://myNS.com">
<soap:Header/>
<soap:Body>
<ns:getCapabilities>
<in0>
<ns:GetCapabilitiesRequest/>
</in0>
</ns:getCapabilities>
</soap:Body>
</soap:Envelope>
The request gets resolved correcty by axis (using the
SOAPMessageBodyBasedDispatcher) BUT here's the catch. Suddenly the
parameter which the (correct!) service operation gets is
<ns:getCapabilities>
<in0>
<ns:GetCapabilitiesRequest/>
</in0>
</ns:getCapabilities>
This is rather useless because in that case the service operation must
be ready to handle all kinds of different parameters depending on the
invocation method used!? Shouldn't the SOAPMessageBodyBasedDispatcher
remove the 'meta-informational' stuff (in this case the getCapabilities
(aka operation-name), and in0 (parameter direction)) and only send the
real parameter to the operation?
If I'm mistaken, how can I invoke an operation anonymously and does not
have the problem of ending up with wrong parameters on the service side?
If I'm correct please let me know and I will file a bug report.
Many thanks in advance!
Cheers,
Severin
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
WS invocation problem
Posted by Ecker Severin <Se...@arcs.ac.at>.
Hi,
I have the following setup:
Tomcat 5.5, axis2 (versions 1.1.1, 1.2 and snapshot), java 1.6.0_02
(which was used for the WS I've written and is used to run tomcat)
The webservice exposes a method with a parameter (MethodRequest). Now
I'm facing the following problem:
The request is as simple as this:
<soap:Envelope
xmlns:soap="http://www.w3.org/2003/05/soap-envelope"
xmlns:ns="http://my.org/WS/types/1.0">
<soap:Header/>
<soap:Body>
<ns:MethodRequest/>
</soap:Body>
</soap:Envelope>
Using the sendReceive method of the ServiceClient class (in the axis2
lib) the method invocation works just fine.
BUT using a soap client (such as SOAPui) I get different kinds of error
responses depending on the version of axis2 that I'm using
Errors:
Axis2 1.1.1:
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Header/>
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">null; nested exception is:
java.lang.NullPointerException</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Axis2 1.2:
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text xml:lang="en-US">unknown</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Axis2 snapshot:
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope">
<soapenv:Body>
<soapenv:Fault>
<soapenv:Code>
<soapenv:Value>soapenv:Sender</soapenv:Value>
</soapenv:Code>
<soapenv:Reason>
<soapenv:Text
xml:lang="en-US">org.apache.axis2.AxisFault.makeFault(Ljava/lang/Excepti
on;)Lorg/apache/axis2/AxisFault;</soapenv:Text>
</soapenv:Reason>
<soapenv:Detail/>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>
Also the TRACE output of axis2 does not give me ANY clue about what's
going on (I have the traces here, but before bloating the post with a
huge logfile I'll just wait and see if someone can shed some light on
what's going on) What I can tell is that my service implementation never
receives the method invocation request but the axis/soap handling
mechanisms throw the exception beforehand. (oh and yes it's SOAP 1.2)
My thanks in advance!
Cheers,
severin
-------------
Severin Ecker
Business Unit Software Systems
Smart Systems Division
Austrian Research Centers GmbH - ARC
2444 Seibersdorf
T: + 43 (0) 50 550 - 3122
M: + 43 (0) 664 60780 3122
F: + 43 (0) 50 550 - 2813
mailto:severin.ecker@arcs.ac.at
www.smart-systems.at
HG Wien - FN 115980i - ATU14703506
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513938 ]
Ann Robinson commented on AXIS2-2968:
-------------------------------------
I will check with the wsdl4j team to see what they can do.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Fix For: 1.3
>
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530139 ]
Ann Robinson commented on AXIS2-2968:
-------------------------------------
Amila, Thanks for the comments and suggestions.
The problem is having a solution that will work in all WSDL cases, and not impact the customer's setup or API usage. Also, not every server environment will be resource constrained - for those server environments, it would be nice to avoid the processing overhead.
So, I was thinking of having a configuration parameter to control how the in-memory copy of the WSDL definition is handled on the AxisService object.
For example, given a configuration parameter named ReduceWSDLMemoryCache (or something similar), then the WSDL definition wrapper could query the configuration parameter. If the configuration setting is "True", then the wrapper takes the steps to reduce the memory used by the WSDL defintion. For now, that would be serializing the WSDL definition object if it can be. When the updates to WSDL4J are available, then the wrapper could take advantage of new APIs or steps provided by WSDL4J.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513930 ]
Davanum Srinivas commented on AXIS2-2968:
-----------------------------------------
Ann, Both XMLSchema and WSDL4J are holding onto the original DOM node for the schema. In WSDL4J, there is a SchemaImpl class which is used with the ExtensionRegistry which has a reference to it. Also the DocumentationElement as well. I wonder if we could store them as strings instead. In XmlSchema, XmlSchemaDocumentation and XmlSchemaAppInfo store references, am trying some local changes to see if we can get rid of them. May involve an API change. Can you please chase the issue on the wsdl4j side?
thanks,
dims
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Fix For: 1.3
>
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ann Robinson updated AXIS2-2968:
--------------------------------
Attachment: patch_01.txt
The attached file, patch_01.txt, contains changes to do a wrapper on the wsdl defintion object that is saved as a Parameter on an AxisService object. The intent of the wrapper is to reduce the memory footprint by releasing portions of the WSDLDefinition object. Then, if anyone accesses those portions of the WSDLDefinition object, the wrapper can reload the WSDLDefinition.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Fix For: 1.3
>
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Tom Seelbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568213#action_12568213 ]
Tom Seelbach commented on AXIS2-2968:
-------------------------------------
I was trying to use the new memory-reduced WSDL definitions. It seems that some additional changes are needed because not all of the WSDLDefinitionWrapper constructors have access to the "ReduceWSDLMemoryCache" parameters. Various parts of axis2 are not calling a "ReduceWSDLMemoryCache aware" WSDLDefinitionWrapper constructor. Since the needed parameters would be in axis2.xml which is represented by AxisConfiguration which is inside ConfigurationContext, I decided to pass the ConfigurationContext down, eventually to WSDLDefinitionWrapper. The following files are affected:
./kernel/src/org/apache/axis2/wsdl/util/WSDLDefinitionWrapper.java
./kernel/src/org/apache/axis2/wsdl/util/WSDLWrapperReloadImpl.java
./kernel/src/org/apache/axis2/wsdl/util/WSDLWrapperBasicImpl.java
./kernel/src/org/apache/axis2/wsdl/util/WSDLWrapperSaveImpl.java
./metadata/src/org/apache/axis2/jaxws/description/DescriptionFactory.java
./metadata/src/org/apache/axis2/jaxws/description/impl/ServiceDescriptionImpl.java
./metadata/src/org/apache/axis2/jaxws/description/impl/DescriptionFactoryImpl.java
./metadata/src/org/apache/axis2/jaxws/description/builder/DescriptionBuilderComposite.java
./metadata/src/org/apache/axis2/jaxws/util/WSDL4JWrapper.java
./metadata/test-resources/axis2.xml
./metadata/test/org/apache/axis2/jaxws/description/impl/DescriptionFactoryImplTests.java
./metadata/test/org/apache/axis2/jaxws/description/DBCwithReduceWSDLMemoryParmsTests.java
WSDLDefinitionWrapper.java: added constructor with ((Definition def,AxisConfiguration axisConfig)
- factored out "setupMemoryParms(axisConfig)"
- added debug
WSDLWrapperReloadImpl.java, WSDLWrapperBasicImpl.java, WSDLWrapperSaveImpl.java
- in toString() - print class name
- added debug
DescriptionFactory.java
- add createServiceDescriptionFromDBCMap() method with ConfigurationContext parameter.
ServiceDescriptionImpl.java
- add ConfigurationContext to constructor call. Change other constructors to delegate to contructor with configContext
- change calls to WSDL4JWrapper to pass the ConfigurationContext
- added debug to trace exactly which way we construct WSDL4JWrapper
- added debugMemoryParms() method (probably should go in a utility class?
DescriptionFactoryImpl.java
- added createServiceDescriptionFromDBCMap() method with ConfigurationContext parm
- make other createServiceDescriptionFromDBCMap() method delegate to the new one.
- create ServiceDescriptionImpl passing along the ConfigurationContext
DescriptionBuilderComposite.java
- add constructor with ConfigurationContext parm
- added details to toString()
- change call to construct WSDL4JWrapper - pass along ConfigurationContext
WSDL4JWrapper.java
- add constructors with ConfigurationContext parm, and change existing constructors to delegate to them
- added ConfiguationContext as member data. Not sure I like this. Could just store the memory parm settings instead....
- when constructing WSDLDefinitionWrapper, pass along ConfigurationContext
- added debug
axis2.xml
- added memory parms for test
DescriptionFactoryImplTests.java
- changed to call, passing null ConfigurationContext
DBCwithReduceWSDLMemoryParmsTests.java
- test case for this change.
- uses ReduceMemory parms from axis2.xml, contructs DescriptionBuilderComposite, checks to make sure WSDLWrapperReloadImpl.class is constructed
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Reopened: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle reopened AXIS2-2968:
-----------------------------------
reopening to assess new patch
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch-5.txt, patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Tom Seelbach (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tom Seelbach updated AXIS2-2968:
--------------------------------
Attachment: patch-5.txt
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch-5.txt, patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527526 ]
Ann Robinson commented on AXIS2-2968:
-------------------------------------
I have been working with the WSDL4J team on ways to reduce the memory footprint of the WSDL definition implementation.
For Axis2, I would like to propose using a wrapper on the WSDLDefinition
- to keep changes to the WSDL4J implementation from impacting users
(especially those components that expect to access a WSDLDefinition
from the parameter include list in the AxisService)
- to allow certain environments to take advantage of changes in WSDL4J,
(eg. new APIs, new steps, or catch exceptions) to reduce memory footprint
- to preserve current behavior
The difference in this solution from the previously proposed solution is that
- no resources will be released
- no need to try to reload the original WSDL (so we don't have to worry about
custom WSDL locators or ?WSDL support)
This wrapper on the WSDLDefinition would do the following:
- implement the wsdl definition interface and delegate the methods to the actual
WSDL4J wsdl definition implementation that is being wrapped
- provide tracing for debug situations
- perform new steps to memory footprint when needed for certain environments
- - this could be controlled via a configuration parameter so that the default
behavior is the same as current behavior
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513731 ]
Davanum Srinivas commented on AXIS2-2968:
-----------------------------------------
Ann,
Sorry. Definitely NO for 1.3 release. We can revisit this later. As Amila mentioned, this works fine with a self-contained wsdl. Won't work if the wsdl imports other wsdl's or xsd's. Too much of a change in between RC's.
thanks,
dims
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Fix For: 1.3
>
> Attachments: patch_01.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ann Robinson updated AXIS2-2968:
--------------------------------
Attachment: patch_03.txt
The patch patch_03.txt contains the updates for the WSDLDefintionWrapper.
The idea is to have a wrapper for the WSDL4J's wsdl Definition object so that the memory footprint can be reduced in certain environments.
Note that this is used for those wsdl Definition objects that are kept in memory as a Parameter on the AxisService object, since these objects can potentially be in memory for a long time.
The WSDLDefinitionWrapper has been split into a top-level class, which makes the decision on when and how to reduce the memory footprint, and some low-level implementation classes, each of which uses a different technique to reduce the memory footprint. The implementation classes include:
- a basic passthru implementation where no reduction is done, just invokes the underlying WSDL4J Definition object
- a serialization implementation where the WSDL4J Definition object is serialized/de-serialized (but note that some wsdl files fail to serialize with WSDL4J v1.6.2)
- a reload implementation that releases portions of the WSDL4J Definition object and reloads the wsdl if needed
WSDLDefinitionWrapper selects its implentation class is as follows:
- the default is the basic passthru, minimizing the overhead
- the default memory reduction is the serialization implementation, which
avoids the pitfalls of trying to reload the wsdl file
- checks for configuration settings in the axis2.xml file
The configuration setting in the axis2.xml file provides a way to easily turn on the memory reduction on the WSDL4J Definition objects, and
to select which technique to use. This is important since different environments require different techniques.
There is a separate issue being worked with the WSDL4J developers
to try to reduce the memory footprint within the WSDL4J implementation.
However, the timeframe for a resolution is uncertain, and their solution might require doing some extra steps (in which case, the WSDLDefinitionWrapper can do without impacting axis2 applications).
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ann Robinson updated AXIS2-2968:
--------------------------------
Attachment: patch_02_part1.txt
The attached patch, patch_02_part1.txt, contains the initial implementation of the light-weight wsdl definition wrapper and changes to various components to use the wrapper in cases where the WSDL4J wsdl definition is saved as a parameter on the AxisService object instance.
This initial implementation is intended to be used on the current Axis2 so it does not require any updates to the WSDL4J. In this case, the wsdl definition wrapper delegates the wsdl definition interface to the WSDL4J implementation.
What this gives us is a way to migrate to a new version of WSDL4J when the WSDL4J becomes available
- in a more transparent fashion to users of the wsdl definition
- only the wrapper needs to be updated to do the memory reduction steps in those environments that need it
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12569273#action_12569273 ]
Rich Scheuerle commented on AXIS2-2968:
---------------------------------------
Correcting some of the issues in the patch. I will have this committed in the next hour or so, after my final testing completes.
Thanks Tom for this submission,
Rich
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch-5.txt, patch_01.txt, patch_02_part1.txt, patch_03.txt, patchViaSVNdiff.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ann Robinson resolved AXIS2-2968.
---------------------------------
Resolution: Fixed
This has been committed in revision 584248.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12527568 ]
Ann Robinson commented on AXIS2-2968:
-------------------------------------
Another way to use the wsdl definition wrapper is:
- to have it serialize/de-serialize the wsdl definition in those environments where the memory footprint is critical
- for those wsdl definitions that can't be serialized, keep a flag indicating that the definition is not serializable
This is something that may need to be done in the current AXIS2 environment if the updates to the WSDL4J take longer than expected. Note that this may even need to be done even with the updates in the WSDL4J.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rich Scheuerle resolved AXIS2-2968.
-----------------------------------
Resolution: Fixed
Thanks Tom!
Revision is 628087
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch-5.txt, patch_01.txt, patch_02_part1.txt, patch_03.txt, patchViaSVNdiff.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ann Robinson reassigned AXIS2-2968:
-----------------------------------
Assignee: Rich Scheuerle (was: Ann Robinson)
Rich,
I was not able to add you to the watch list for this issue.
I have committed the fix in rev 584248.
Ann
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Rich Scheuerle
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, patch_03.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2968) Out-Of-Memory error on server side -
Use of wsdl4j WSDLDefinition
Posted by "Ann Robinson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2968?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530140 ]
Ann Robinson commented on AXIS2-2968:
-------------------------------------
I will post a patch with the proposed configuration parameter and updates to the wsdl definition wrapper for review.
> Out-Of-Memory error on server side - Use of wsdl4j WSDLDefinition
> -----------------------------------------------------------------
>
> Key: AXIS2-2968
> URL: https://issues.apache.org/jira/browse/AXIS2-2968
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: kernel
> Reporter: Ann Robinson
> Assignee: Ann Robinson
> Priority: Critical
> Attachments: patch_01.txt, patch_02_part1.txt, wsdlFromFileSystem.patch
>
>
> 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, one of the biggest consumers of the memory
> is with the wsdl4j WSDLDefinition objects. In the test scenario, the
> wsdl4j-related objects consumed about a quarter to a third of the entire heap.
>
> The WSDLDefinition object is a very heavy-weight object, much of which stems
> from its use of the xerces dom objects as underlying support, particularly
> for the schemas.
>
> One area to investigate is the saving of the WSDLDefinition as a Parameter
> in the AxisService's ParameterInclude list so that, if some component needs
> to utilize the WSDLDefinition object, it can be accessed via the AxisService
> object.
>
> Is it possible to reduce the utilization of the WSDLDefinition?
> Some ideas are:
> (a) releasing it when it is no longer needed
> - this might not be possible to determine
>
> (b) putting a wrapper on the WSDLDefinition
> - so that the WSDLDefinition,or a portion of the WSDLDefinition,
> can be released
> - but if the WSDLDefinition is accessed after it was released,
> the wrapper can reload the WSDLDefinition transparently to the
> user
>
> (c) create a layer for caching wsdl-related information
> - this would allow for releasing memory based on some algorithm
> and/or interface that could indicate what's no longer needed
>
--
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org