You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@servicemix.apache.org by Soumya <so...@yahoo.co.in> on 2009/11/03 10:46:54 UTC
Servicemix Http component memory leak issue
Hi all,
I am having an issue with using Servicemix 3.2.1 Http component, which apparently seems to be of memory leak.
I have a servicemix deployed on machine A, which only holds a Http component Service Assembly deployed in it. This Servicemix listens to ActiveMQ running alongside Servicemix on machine B as say failover:tcp://${MachineBIP}:${61616}. Idea is we send a https request to machine A and then that xml is forwarded over ActiveMQ to a LWC component deployed on Machine B.
This is the xbean.xml deployed in the http component -
<beans
xmlns:http="http://servicemix.apache.org/http/1.0"
xmlns:lfc="http://www.lifecycle-software.com/bpms">
<http:endpoint service="abc:XYZRequestReceiver" endpoint="XYZLocal" role="consumer"
locationURI="https://192.168.X.Y:443/Service/XYZService"
defaultMep="http://www.w3.org/2004/08/wsdl/in-out">
<http:ssl>
<http:sslParameters keyStore="classpath:MyKeystore.jks"
keyStorePassword="changeit"/>
</http:ssl>
</http:endpoint>
</beans>
There is a DNS mapping of https://xyz.ws.com/Service/XYZService to machine A http component that receives the message.
Kindly note there is no instance of Timeout or Message response not delivered.
It starts with memory consumption of say 98MB and steadily increases over a couple of days to 600 - 700 mb and reaches max memory allocation of 768 mb and hangs up.
Hence I am assuming it is due to soem memory leak in 3.2.1 Http component code.
Please can someone help and point to any suggestions.
Much appreciated.
Regards,
Soumya
Connect more, do more and share more with Yahoo! India Mail. Learn more. http://in.overview.mail.yahoo.com/
Re: Servicemix Http component memory leak issue
Posted by Freeman Fang <fr...@gmail.com>.
Hi,
I think this issue already get resolved by SMXCOMP-319.
Could you please test your project with latest SMX release?
[1]https://issues.apache.org/activemq/browse/SMXCOMP-319
Freeman
On 2010-1-11, at 下午7:18, allgo wrote:
>
> Well was able to solve this issue sometime back.
> Thought of sharing with you all.
> Apparently our client was sending a very very huge xml by mistake(by
> huge I
> mean huge was having records for 36000 entries!). Now Http component
> was
> successfully forwarding it to the LWC component on the other
> machine. The
> LWC component was using XMLbeans to parse that cml which was taking
> more
> than 3 minutes and anyways rejecting the request as we allo max of 100
> entries at a time. hence our backend was safe from being battered.
> But the
> Http thread was timing out due to the delay and seems was giving
> rise to
> memory leak.
>
> Btw just an q - is this a bug and if so has this been fixed in future
> versions? We use servicemix 3.2.1.
>
> Cheers,
> allgo
>
> --
> View this message in context: http://old.nabble.com/Servicemix-Http-component-memory-leak-issue-tp26177254p27108996.html
> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>
--
Freeman Fang
------------------------
Open Source SOA: http://fusesource.com
Re: Servicemix Http component memory leak issue
Posted by allgo <so...@yahoo.co.in>.
Well was able to solve this issue sometime back.
Thought of sharing with you all.
Apparently our client was sending a very very huge xml by mistake(by huge I
mean huge was having records for 36000 entries!). Now Http component was
successfully forwarding it to the LWC component on the other machine. The
LWC component was using XMLbeans to parse that cml which was taking more
than 3 minutes and anyways rejecting the request as we allo max of 100
entries at a time. hence our backend was safe from being battered. But the
Http thread was timing out due to the delay and seems was giving rise to
memory leak.
Btw just an q - is this a bug and if so has this been fixed in future
versions? We use servicemix 3.2.1.
Cheers,
allgo
--
View this message in context: http://old.nabble.com/Servicemix-Http-component-memory-leak-issue-tp26177254p27108996.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
Re: Servicemix Http component memory leak issue
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi,
could you make a try using the new HTTP endpoints ?
Regards
JB
Soumya wrote:
> Hi all,
>
> I am having an issue with using Servicemix 3.2.1 Http component, which apparently seems to be of memory leak.
>
> I have a servicemix deployed on machine A, which only holds a Http component Service Assembly deployed in it. This Servicemix listens to ActiveMQ running alongside Servicemix on machine B as say failover:tcp://${MachineBIP}:${61616}. Idea is we send a https request to machine A and then that xml is forwarded over ActiveMQ to a LWC component deployed on Machine B.
>
> This is the xbean.xml deployed in the http component -
>
> <beans
> xmlns:http="http://servicemix.apache.org/http/1.0"
> xmlns:lfc="http://www.lifecycle-software.com/bpms">
>
> <http:endpoint service="abc:XYZRequestReceiver" endpoint="XYZLocal" role="consumer"
> locationURI="https://192.168.X.Y:443/Service/XYZService"
> defaultMep="http://www.w3.org/2004/08/wsdl/in-out">
> <http:ssl>
> <http:sslParameters keyStore="classpath:MyKeystore.jks"
> keyStorePassword="changeit"/>
> </http:ssl>
> </http:endpoint>
>
> </beans>
>
>
> There is a DNS mapping of https://xyz.ws.com/Service/XYZService to machine A http component that receives the message.
>
> Kindly note there is no instance of Timeout or Message response not delivered.
> It starts with memory consumption of say 98MB and steadily increases over a couple of days to 600 - 700 mb and reaches max memory allocation of 768 mb and hangs up.
>
> Hence I am assuming it is due to soem memory leak in 3.2.1 Http component code.
> Please can someone help and point to any suggestions.
>
> Much appreciated.
>
> Regards,
> Soumya
>
>
>
>
> Connect more, do more and share more with Yahoo! India Mail. Learn more. http://in.overview.mail.yahoo.com/