You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Matias Urbieta (JIRA)" <ji...@apache.org> on 2011/01/04 19:12:47 UTC

[jira] Created: (SMXCOMP-838) file descriptors leak with new http provider endpoint when having a wrong provider's target url

file descriptors leak with new http provider endpoint when having a wrong provider's target url
-----------------------------------------------------------------------------------------------

                 Key: SMXCOMP-838
                 URL: https://issues.apache.org/jira/browse/SMXCOMP-838
             Project: ServiceMix Components
          Issue Type: Bug
          Components: servicemix-http
    Affects Versions: servicemix-http-2010.01, servicemix-http-2009.02, servicemix-http-2009.01
         Environment: Linux  2.6.35-23-generic-pae #41-Ubuntu SMP i686 GNU/Linux
SMX- web app distribution
jboss 4.3 

            Reporter: Matias Urbieta


Hi all! i have been facing a connection leak when using new http provider endpoints.
The component consumes linux kernel's file descriptors when provider endpoint points to non existing URL.
To test it, i have attached a single http proxy that consumes requests that are sent thro a http provider with a wrong target URL. it can be consumed using the following line:

wget **serviceURL** --post-data="<msg>amsg</msg>"

Each time a request is done, a file descriptor is consumed but released. It can be detected by counting consumed file descriptor:

ps aux |grep java # helps to determine which SMX process id 

lsof -p **smxProcessId** | wc -l #counts smx file descriptors

As long requests are done, last command line will show an increasing usage fd count. Then maximum allowed file descriptor is reached, SMX stop working because it cant open any kind of connection.
Regards

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


[jira] Updated: (SMXCOMP-838) file descriptors leak with new http provider endpoint when having a wrong provider's target url

Posted by "Matias Urbieta (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SMXCOMP-838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matias Urbieta updated SMXCOMP-838:
-----------------------------------

    Attachment: FDIssueExample.tgz

Example that shows how file descriptors are consumed but released.

> file descriptors leak with new http provider endpoint when having a wrong provider's target url
> -----------------------------------------------------------------------------------------------
>
>                 Key: SMXCOMP-838
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-838
>             Project: ServiceMix Components
>          Issue Type: Bug
>          Components: servicemix-http
>    Affects Versions: servicemix-http-2009.01, servicemix-http-2009.02, servicemix-http-2010.01
>         Environment: Linux  2.6.35-23-generic-pae #41-Ubuntu SMP i686 GNU/Linux
> SMX- web app distribution
> jboss 4.3 
>            Reporter: Matias Urbieta
>         Attachments: FDIssueExample.tgz
>
>
> Hi all! i have been facing a connection leak when using new http provider endpoints.
> The component consumes linux kernel's file descriptors when provider endpoint points to non existing URL.
> To test it, i have attached a single http proxy that consumes requests that are sent thro a http provider with a wrong target URL. it can be consumed using the following line:
> wget **serviceURL** --post-data="<msg>amsg</msg>"
> Each time a request is done, a file descriptor is consumed but released. It can be detected by counting consumed file descriptor:
> ps aux |grep java # helps to determine which SMX process id 
> lsof -p **smxProcessId** | wc -l #counts smx file descriptors
> As long requests are done, last command line will show an increasing usage fd count. Then maximum allowed file descriptor is reached, SMX stop working because it cant open any kind of connection.
> Regards

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