You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jesse Sightler <js...@gmail.com> on 2006/02/01 17:01:23 UTC
Status w/r/t memory leaks...
I've seen several issues in JIRA relating to memory leaks on the server-side
of Axis recently.
Specifically, I've noticed:
http://issues.apache.org/jira/browse/AXIS-2278
https://issues.apache.org/jira/browse/AXIS-2266
https://issues.apache.org/jira/browse/AXIS-2185
What are peoples current experiences with memory leaks in Axis1? Is the CVS
version significantly more stable than the current release version? Is a
1.4 release forthcoming to resolve the issues?
Thanks,
Jess
Re: Status w/r/t memory leaks...
Posted by Jesse Sightler <js...@gmail.com>.
Much better... I was able to throw about .5 million requests at the new
version with no increase in memory usage.
Thanks for the tip,
Jess
On 2/2/06, Jesse Sightler <js...@gmail.com> wrote:
>
> Never mind... I figured it out. We were (incorrectly) trying to use
> method overloading in a web service.
>
> I'm running the memory leak tests for this now.
>
> Thanks,
> Jess
>
>
> On 2/2/06, Jesse Sightler <js...@gmail.com> wrote:
> >
> > Have there been significant changes on the trunk related to .jws files?
> > My calls to one are now failing with:
> >
> > Caused by: java.lang.ArrayIndexOutOfBoundsException
> > at org.apache.axis.providers.java.RPCProvider.processMessage (
> > RPCProvider.java:129)
> > at org.apache.axis.providers.java.JavaProvider.invoke(
> > JavaProvider.java:327)
> > at org.apache.axis.strategies.InvocationStrategy.visit(
> > InvocationStrategy.java:32)
> > at org.apache.axis.SimpleChain.doVisiting (SimpleChain.java:118)
> > at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> > at org.apache.axis.handlers.soap.SOAPService.invoke(
> > SOAPService.java:454)
> > at org.apache.axis.server.AxisServer.invokeService (
> > AxisServer.java:239)
> > at org.apache.axis.server.AxisServer.invoke(AxisServer.java:380)
> > at org.apache.axis.transport.http.AxisServlet.doPost(
> > AxisServlet.java:699)
> > at javax.servlet.http.HttpServlet.service (HttpServlet.java:717)
> > at org.apache.axis.transport.http.AxisServletBase.service(
> > AxisServletBase.java:327)
> > at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (
> > ApplicationFilterChain.java:252)
> > at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> > ApplicationFilterChain.java:173)
> > at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(
> > ReplyHeaderFilter.java :81)
> > at
> > org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> > ApplicationFilterChain.java:202)
> > at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> > ApplicationFilterChain.java:173)
> > at org.apache.catalina.core.StandardWrapperValve.invoke(
> > StandardWrapperValve.java:213)
> > at org.apache.catalina.core.StandardContextValve.invoke(
> > StandardContextValve.java:178)
> > at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke (
> > CustomPrincipalValve.java:39)
> > at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke
> > (SecurityAssociationValve.java:159)
> > at org.jboss.web.tomcat.security.JaccContextValve.invoke(
> > JaccContextValve.java :59)
> > at org.apache.catalina.core.StandardHostValve.invoke(
> > StandardHostValve.java:126)
> > at org.apache.catalina.valves.ErrorReportValve.invoke(
> > ErrorReportValve.java:105)
> > at org.apache.catalina.valves.FastCommonAccessLogValve.invoke (
> > FastCommonAccessLogValve.java:481)
> > at org.apache.catalina.core.StandardEngineValve.invoke(
> > StandardEngineValve.java:107)
> > at org.apache.catalina.connector.CoyoteAdapter.service(
> > CoyoteAdapter.java:148)
> > at org.apache.coyote.http11.Http11Processor.process(
> > Http11Processor.java:856)
> > at
> > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
> > (Http11Protocol.java:744)
> > at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
> > PoolTcpEndpoint.java:527)
> > at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(
> > MasterSlaveWorkerThread.java:112)
> > at java.lang.Thread.run ()V(Unknown Source)
> >
> >
> > However, this had worked perfectly with the 1.3 binaries.
> >
> > Thanks,
> > Jess
> >
> >
> > On 2/1/06, Davanum Srinivas < davanum@gmail.com> wrote:
> > >
> > > plz use the trunk.
> > >
> > > On 2/1/06, Jared Klett < jklett@gmail.com> wrote:
> > > > hi Dims,
> > > >
> > > > ok, the SVN checkout is proceeding - I'm looking in the branches/
> > > > subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> > > > should I be in the trunk, or something else? thanks!
> > > >
> > > > cheers,
> > > >
> > > > - Jared
> > > >
> > > > On 2/1/06, Davanum Srinivas < davanum@gmail.com> wrote:
> > > > > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
> > > > >
> > > > > -- dims
> > > > >
> > > > > On 2/1/06, Jared Klett < jklett@gmail.com> wrote:
> > > > > > greetings all,
> > > > > >
> > > > > > That's funny, I was just working on composing a long message
> > > > > > describing the memory issue I'm having with Axis+Tomcat that I
> > > haven't
> > > > > > been able to solve by tweaking JVM memory or GC parameters or by
> > > > > > upgrading to Axis 1.3.
> > > > > >
> > > > > > So Dims, you're saying to do a checkout of the latest CVS
> > > according to
> > > > > > this page:
> > > > > >
> > > > > > http://ws.apache.org/axis/cvs.html
> > > > > >
> > > > > > and do our own build, which will give us 1.3 + the 3 fixes
> > > detailed in JIRA?
> > > > > >
> > > > > > just want to confirm... thanks!
> > > > > >
> > > > > > cheers,
> > > > > >
> > > > > > - Jared
> > > > > >
> > > > > > On 2/1/06, Davanum Srinivas < davanum@gmail.com> wrote:
> > > > > > > All 3 are fixed in latest SVN.
> > > > > > >
> > > > > > > thanks,
> > > > > > > dims
> > > > > > >
> > > > > > > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > > > > > > I've seen several issues in JIRA relating to memory leaks on
> > > the server-side
> > > > > > > > of Axis recently.
> > > > > > > >
> > > > > > > > Specifically, I've noticed:
> > > > > > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > > > > > https://issues.apache.org/jira/browse/AXIS-2266
> > > > > > > > https://issues.apache.org/jira/browse/AXIS-2185
> > > > > > > >
> > > > > > > > What are peoples current experiences with memory leaks in
> > > Axis1? Is the CVS
> > > > > > > > version significantly more stable than the current release
> > > version? Is a
> > > > > > > > 1.4 release forthcoming to resolve the issues?
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > Jess
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Davanum Srinivas : http://wso2.com/blogs/
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Davanum Srinivas : http://wso2.com/blogs/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> >
> >
>
Re: Status w/r/t memory leaks...
Posted by Jesse Sightler <js...@gmail.com>.
Never mind... I figured it out. We were (incorrectly) trying to use method
overloading in a web service.
I'm running the memory leak tests for this now.
Thanks,
Jess
On 2/2/06, Jesse Sightler <js...@gmail.com> wrote:
>
> Have there been significant changes on the trunk related to .jws files?
> My calls to one are now failing with:
>
> Caused by: java.lang.ArrayIndexOutOfBoundsException
> at org.apache.axis.providers.java.RPCProvider.processMessage (
> RPCProvider.java:129)
> at org.apache.axis.providers.java.JavaProvider.invoke(
> JavaProvider.java:327)
> at org.apache.axis.strategies.InvocationStrategy.visit(
> InvocationStrategy.java:32)
> at org.apache.axis.SimpleChain.doVisiting (SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at org.apache.axis.handlers.soap.SOAPService.invoke(
> SOAPService.java:454)
> at org.apache.axis.server.AxisServer.invokeService (
> AxisServer.java:239)
> at org.apache.axis.server.AxisServer.invoke(AxisServer.java:380)
> at org.apache.axis.transport.http.AxisServlet.doPost(
> AxisServlet.java:699)
> at javax.servlet.http.HttpServlet.service (HttpServlet.java:717)
> at org.apache.axis.transport.http.AxisServletBase.service(
> AxisServletBase.java:327)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter (
> ApplicationFilterChain.java:252)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:173)
> at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(
> ReplyHeaderFilter.java :81)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
> ApplicationFilterChain.java:202)
> at org.apache.catalina.core.ApplicationFilterChain.doFilter(
> ApplicationFilterChain.java:173)
> at org.apache.catalina.core.StandardWrapperValve.invoke(
> StandardWrapperValve.java:213)
> at org.apache.catalina.core.StandardContextValve.invoke(
> StandardContextValve.java:178)
> at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke (
> CustomPrincipalValve.java:39)
> at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(
> SecurityAssociationValve.java:159)
> at org.jboss.web.tomcat.security.JaccContextValve.invoke(
> JaccContextValve.java :59)
> at org.apache.catalina.core.StandardHostValve.invoke(
> StandardHostValve.java:126)
> at org.apache.catalina.valves.ErrorReportValve.invoke(
> ErrorReportValve.java:105)
> at org.apache.catalina.valves.FastCommonAccessLogValve.invoke (
> FastCommonAccessLogValve.java:481)
> at org.apache.catalina.core.StandardEngineValve.invoke(
> StandardEngineValve.java:107)
> at org.apache.catalina.connector.CoyoteAdapter.service(
> CoyoteAdapter.java:148)
> at org.apache.coyote.http11.Http11Processor.process(
> Http11Processor.java:856)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
> (Http11Protocol.java:744)
> at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
> PoolTcpEndpoint.java:527)
> at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(
> MasterSlaveWorkerThread.java:112)
> at java.lang.Thread.run()V(Unknown Source)
>
>
> However, this had worked perfectly with the 1.3 binaries.
>
> Thanks,
> Jess
>
>
> On 2/1/06, Davanum Srinivas < davanum@gmail.com> wrote:
> >
> > plz use the trunk.
> >
> > On 2/1/06, Jared Klett < jklett@gmail.com> wrote:
> > > hi Dims,
> > >
> > > ok, the SVN checkout is proceeding - I'm looking in the branches/
> > > subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> > > should I be in the trunk, or something else? thanks!
> > >
> > > cheers,
> > >
> > > - Jared
> > >
> > > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > > > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
> > > >
> > > > -- dims
> > > >
> > > > On 2/1/06, Jared Klett < jklett@gmail.com> wrote:
> > > > > greetings all,
> > > > >
> > > > > That's funny, I was just working on composing a long message
> > > > > describing the memory issue I'm having with Axis+Tomcat that I
> > haven't
> > > > > been able to solve by tweaking JVM memory or GC parameters or by
> > > > > upgrading to Axis 1.3.
> > > > >
> > > > > So Dims, you're saying to do a checkout of the latest CVS
> > according to
> > > > > this page:
> > > > >
> > > > > http://ws.apache.org/axis/cvs.html
> > > > >
> > > > > and do our own build, which will give us 1.3 + the 3 fixes
> > detailed in JIRA?
> > > > >
> > > > > just want to confirm... thanks!
> > > > >
> > > > > cheers,
> > > > >
> > > > > - Jared
> > > > >
> > > > > On 2/1/06, Davanum Srinivas < davanum@gmail.com> wrote:
> > > > > > All 3 are fixed in latest SVN.
> > > > > >
> > > > > > thanks,
> > > > > > dims
> > > > > >
> > > > > > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > > > > > I've seen several issues in JIRA relating to memory leaks on
> > the server-side
> > > > > > > of Axis recently.
> > > > > > >
> > > > > > > Specifically, I've noticed:
> > > > > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > > > > https://issues.apache.org/jira/browse/AXIS-2266
> > > > > > > https://issues.apache.org/jira/browse/AXIS-2185
> > > > > > >
> > > > > > > What are peoples current experiences with memory leaks in
> > Axis1? Is the CVS
> > > > > > > version significantly more stable than the current release
> > version? Is a
> > > > > > > 1.4 release forthcoming to resolve the issues?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Jess
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Davanum Srinivas : http://wso2.com/blogs/
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Davanum Srinivas : http://wso2.com/blogs/
> > > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
>
Re: Status w/r/t memory leaks...
Posted by Jesse Sightler <js...@gmail.com>.
Have there been significant changes on the trunk related to .jws files? My
calls to one are now failing with:
Caused by: java.lang.ArrayIndexOutOfBoundsException
at org.apache.axis.providers.java.RPCProvider.processMessage(
RPCProvider.java:129)
at org.apache.axis.providers.java.JavaProvider.invoke(
JavaProvider.java:327)
at org.apache.axis.strategies.InvocationStrategy.visit(
InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.handlers.soap.SOAPService.invoke(SOAPService.java
:454)
at org.apache.axis.server.AxisServer.invokeService(AxisServer.java
:239)
at org.apache.axis.server.AxisServer.invoke(AxisServer.java:380)
at org.apache.axis.transport.http.AxisServlet.doPost(
AxisServlet.java:699)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.axis.transport.http.AxisServletBase.service(
AxisServletBase.java:327)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(
ReplyHeaderFilter.java:81)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(
ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(
ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke(
StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke(
StandardContextValve.java:178)
at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(
CustomPrincipalValve.java:39)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(
SecurityAssociationValve.java:159)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(
JaccContextValve.java:59)
at org.apache.catalina.core.StandardHostValve.invoke(
StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke(
ErrorReportValve.java:105)
at org.apache.catalina.valves.FastCommonAccessLogValve.invoke(
FastCommonAccessLogValve.java:481)
at org.apache.catalina.core.StandardEngineValve.invoke(
StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service(
CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process(
Http11Processor.java:856)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection
(Http11Protocol.java:744)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(
PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(
MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run()V(Unknown Source)
However, this had worked perfectly with the 1.3 binaries.
Thanks,
Jess
On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
>
> plz use the trunk.
>
> On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> > hi Dims,
> >
> > ok, the SVN checkout is proceeding - I'm looking in the branches/
> > subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> > should I be in the trunk, or something else? thanks!
> >
> > cheers,
> >
> > - Jared
> >
> > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
> > >
> > > -- dims
> > >
> > > On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> > > > greetings all,
> > > >
> > > > That's funny, I was just working on composing a long message
> > > > describing the memory issue I'm having with Axis+Tomcat that I
> haven't
> > > > been able to solve by tweaking JVM memory or GC parameters or by
> > > > upgrading to Axis 1.3.
> > > >
> > > > So Dims, you're saying to do a checkout of the latest CVS according
> to
> > > > this page:
> > > >
> > > > http://ws.apache.org/axis/cvs.html
> > > >
> > > > and do our own build, which will give us 1.3 + the 3 fixes detailed
> in JIRA?
> > > >
> > > > just want to confirm... thanks!
> > > >
> > > > cheers,
> > > >
> > > > - Jared
> > > >
> > > > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > > > > All 3 are fixed in latest SVN.
> > > > >
> > > > > thanks,
> > > > > dims
> > > > >
> > > > > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > > > > I've seen several issues in JIRA relating to memory leaks on the
> server-side
> > > > > > of Axis recently.
> > > > > >
> > > > > > Specifically, I've noticed:
> > > > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > > > https://issues.apache.org/jira/browse/AXIS-2266
> > > > > > https://issues.apache.org/jira/browse/AXIS-2185
> > > > > >
> > > > > > What are peoples current experiences with memory leaks in
> Axis1? Is the CVS
> > > > > > version significantly more stable than the current release
> version? Is a
> > > > > > 1.4 release forthcoming to resolve the issues?
> > > > > >
> > > > > > Thanks,
> > > > > > Jess
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Davanum Srinivas : http://wso2.com/blogs/
> > > > >
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: Status w/r/t memory leaks...
Posted by Davanum Srinivas <da...@gmail.com>.
plz use the trunk.
On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> hi Dims,
>
> ok, the SVN checkout is proceeding - I'm looking in the branches/
> subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
> should I be in the trunk, or something else? thanks!
>
> cheers,
>
> - Jared
>
> On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
> >
> > -- dims
> >
> > On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> > > greetings all,
> > >
> > > That's funny, I was just working on composing a long message
> > > describing the memory issue I'm having with Axis+Tomcat that I haven't
> > > been able to solve by tweaking JVM memory or GC parameters or by
> > > upgrading to Axis 1.3.
> > >
> > > So Dims, you're saying to do a checkout of the latest CVS according to
> > > this page:
> > >
> > > http://ws.apache.org/axis/cvs.html
> > >
> > > and do our own build, which will give us 1.3 + the 3 fixes detailed in JIRA?
> > >
> > > just want to confirm... thanks!
> > >
> > > cheers,
> > >
> > > - Jared
> > >
> > > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > > > All 3 are fixed in latest SVN.
> > > >
> > > > thanks,
> > > > dims
> > > >
> > > > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > > > I've seen several issues in JIRA relating to memory leaks on the server-side
> > > > > of Axis recently.
> > > > >
> > > > > Specifically, I've noticed:
> > > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > > https://issues.apache.org/jira/browse/AXIS-2266
> > > > > https://issues.apache.org/jira/browse/AXIS-2185
> > > > >
> > > > > What are peoples current experiences with memory leaks in Axis1? Is the CVS
> > > > > version significantly more stable than the current release version? Is a
> > > > > 1.4 release forthcoming to resolve the issues?
> > > > >
> > > > > Thanks,
> > > > > Jess
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Davanum Srinivas : http://wso2.com/blogs/
> > > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Status w/r/t memory leaks...
Posted by Jared Klett <jk...@gmail.com>.
hi Dims,
ok, the SVN checkout is proceeding - I'm looking in the branches/
subdir - should I build "AXIS_1_4_FINAL" to get those 3 fixes, or
should I be in the trunk, or something else? thanks!
cheers,
- Jared
On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> "svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
>
> -- dims
>
> On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> > greetings all,
> >
> > That's funny, I was just working on composing a long message
> > describing the memory issue I'm having with Axis+Tomcat that I haven't
> > been able to solve by tweaking JVM memory or GC parameters or by
> > upgrading to Axis 1.3.
> >
> > So Dims, you're saying to do a checkout of the latest CVS according to
> > this page:
> >
> > http://ws.apache.org/axis/cvs.html
> >
> > and do our own build, which will give us 1.3 + the 3 fixes detailed in JIRA?
> >
> > just want to confirm... thanks!
> >
> > cheers,
> >
> > - Jared
> >
> > On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > > All 3 are fixed in latest SVN.
> > >
> > > thanks,
> > > dims
> > >
> > > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > > I've seen several issues in JIRA relating to memory leaks on the server-side
> > > > of Axis recently.
> > > >
> > > > Specifically, I've noticed:
> > > > http://issues.apache.org/jira/browse/AXIS-2278
> > > > https://issues.apache.org/jira/browse/AXIS-2266
> > > > https://issues.apache.org/jira/browse/AXIS-2185
> > > >
> > > > What are peoples current experiences with memory leaks in Axis1? Is the CVS
> > > > version significantly more stable than the current release version? Is a
> > > > 1.4 release forthcoming to resolve the issues?
> > > >
> > > > Thanks,
> > > > Jess
> > > >
> > > >
> > >
> > >
> > > --
> > > Davanum Srinivas : http://wso2.com/blogs/
> > >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: Status w/r/t memory leaks...
Posted by Davanum Srinivas <da...@gmail.com>.
"svn co http://svn.apache.org/repos/asf/webservices/axis/ axis"
-- dims
On 2/1/06, Jared Klett <jk...@gmail.com> wrote:
> greetings all,
>
> That's funny, I was just working on composing a long message
> describing the memory issue I'm having with Axis+Tomcat that I haven't
> been able to solve by tweaking JVM memory or GC parameters or by
> upgrading to Axis 1.3.
>
> So Dims, you're saying to do a checkout of the latest CVS according to
> this page:
>
> http://ws.apache.org/axis/cvs.html
>
> and do our own build, which will give us 1.3 + the 3 fixes detailed in JIRA?
>
> just want to confirm... thanks!
>
> cheers,
>
> - Jared
>
> On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> > All 3 are fixed in latest SVN.
> >
> > thanks,
> > dims
> >
> > On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > > I've seen several issues in JIRA relating to memory leaks on the server-side
> > > of Axis recently.
> > >
> > > Specifically, I've noticed:
> > > http://issues.apache.org/jira/browse/AXIS-2278
> > > https://issues.apache.org/jira/browse/AXIS-2266
> > > https://issues.apache.org/jira/browse/AXIS-2185
> > >
> > > What are peoples current experiences with memory leaks in Axis1? Is the CVS
> > > version significantly more stable than the current release version? Is a
> > > 1.4 release forthcoming to resolve the issues?
> > >
> > > Thanks,
> > > Jess
> > >
> > >
> >
> >
> > --
> > Davanum Srinivas : http://wso2.com/blogs/
> >
>
--
Davanum Srinivas : http://wso2.com/blogs/
Re: Status w/r/t memory leaks...
Posted by Jared Klett <jk...@gmail.com>.
greetings all,
That's funny, I was just working on composing a long message
describing the memory issue I'm having with Axis+Tomcat that I haven't
been able to solve by tweaking JVM memory or GC parameters or by
upgrading to Axis 1.3.
So Dims, you're saying to do a checkout of the latest CVS according to
this page:
http://ws.apache.org/axis/cvs.html
and do our own build, which will give us 1.3 + the 3 fixes detailed in JIRA?
just want to confirm... thanks!
cheers,
- Jared
On 2/1/06, Davanum Srinivas <da...@gmail.com> wrote:
> All 3 are fixed in latest SVN.
>
> thanks,
> dims
>
> On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> > I've seen several issues in JIRA relating to memory leaks on the server-side
> > of Axis recently.
> >
> > Specifically, I've noticed:
> > http://issues.apache.org/jira/browse/AXIS-2278
> > https://issues.apache.org/jira/browse/AXIS-2266
> > https://issues.apache.org/jira/browse/AXIS-2185
> >
> > What are peoples current experiences with memory leaks in Axis1? Is the CVS
> > version significantly more stable than the current release version? Is a
> > 1.4 release forthcoming to resolve the issues?
> >
> > Thanks,
> > Jess
> >
> >
>
>
> --
> Davanum Srinivas : http://wso2.com/blogs/
>
Re: Status w/r/t memory leaks...
Posted by Davanum Srinivas <da...@gmail.com>.
All 3 are fixed in latest SVN.
thanks,
dims
On 2/1/06, Jesse Sightler <js...@gmail.com> wrote:
> I've seen several issues in JIRA relating to memory leaks on the server-side
> of Axis recently.
>
> Specifically, I've noticed:
> http://issues.apache.org/jira/browse/AXIS-2278
> https://issues.apache.org/jira/browse/AXIS-2266
> https://issues.apache.org/jira/browse/AXIS-2185
>
> What are peoples current experiences with memory leaks in Axis1? Is the CVS
> version significantly more stable than the current release version? Is a
> 1.4 release forthcoming to resolve the issues?
>
> Thanks,
> Jess
>
>
--
Davanum Srinivas : http://wso2.com/blogs/