[jboss-jira] [JBoss JIRA] (WFLY-8160) Webservice response File Descriptor leak

Tomaz Cerar (JIRA) issues at jboss.org
Fri Mar 24 04:49:00 EDT 2017


    [ https://issues.jboss.org/browse/WFLY-8160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13383510#comment-13383510 ] 

Tomaz Cerar commented on WFLY-8160:
-----------------------------------

Well, then the trace you provided doesn't include everything.

You can also configure the leak detector agent to dump only non-closed descriptors, this way it is easier to find culprit.

> Webservice response File Descriptor leak
> ----------------------------------------
>
>                 Key: WFLY-8160
>                 URL: https://issues.jboss.org/browse/WFLY-8160
>             Project: WildFly
>          Issue Type: Bug
>          Components: Web Services
>    Affects Versions: 9.0.0.Final, 9.0.2.Final, 10.1.0.Final
>         Environment: JDK: jdk1.8.0_121, jdk1.8.0_66
> WilfFly : wildfly-10.1.0.Final,  wildfly-9.0.2.Final , wildfly-9.0.0.Final
> OS: Red Hat Enterprise Linux Server release 7.1 (Maipo)
> Hardware: 64 bit 4 core
>            Reporter: Mahesh Reddy
>            Assignee: Alessio Soldano
>         Attachments: BioMatcherWebserviceImpl.java, SOAP_REQUEST.txt, SOAP_RESPONSE.txt, file-leak-detector_output.txt
>
>
> We are getting File descriptor leak when wildfly responds to webservice call.
> I think this happens if the webresvice response is huge complex structure, 
> I confirmed by adding the sleep just before the returning from the webservice method and  checking lsof -p <pid>, And again checking it after client receives the response,.
> I notice for each webservice call, 2 file descriptors are open and never closed.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jboss-jira mailing list