Too many open file Descriptors in Wildfly-18.

[Kati Babu]

Hello,

In the application code deployed in wildfly10, if the fileinputstream is not closed programatically (its a miss in the code), during the GC (G1GC) cycle, the orphan references of the opened file input streams are closed, so the number of open file descriptor is not growing.

 However, after the upgrade of the wildfly10 to wildfly18, the file input streams which are not closed programatically are not getting closed during the GC (G1GC) cycle due to which the number of open file descriptors are growing.

 We agree that the input streams have to be closed programatically in the application code which we did now, but would like to understand the reason behind this behavior change in wildfly18.

Thanks,

Manas

[MRP]

Hello All,

Any one can help me on below issues:

Too many open file Descriptors in Wildfly-18

--
You received this message because you are subscribed to a topic in the Google Groups "WildFly" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wildfly/S-3DVKLr0CA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wildfly+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/wildfly/c303ad85-0b9b-4f30-b5ee-72ae5438ae71n%40googlegroups.com.

--

Regards,

Manas
+919886723462

[MRP]

Hello All,

Please help me on the below issue if you have any inputs.

Too many open file Descriptors in Wildfly-18

In the application code deployed in wildfly10, if the fileinputstream is not closed programatically (its a miss in the code), during the GC (G1GC) cycle, the orphan references of the opened file input streams are closed, so the number of open file descriptor is not growing.

 However, after the upgrade of the wildfly10 to wildfly18, the file input streams which are not closed programatically are not getting closed during the GC (G1GC) cycle due to which the number of open file descriptors are growing.

 We agree that the input streams have to be closed programatically in the application code which we did now, but would like to understand the reason behind this behavior change in wildfly18.

Thanks,

Manas

--

Regards,

Manas
+919886723462

[Scott Marlow]

Hello,

If I hit this problem, I would try to see which files are open and consider if there might be a leak of non-application input streams not being closed.  One way might be to examine the instances of input streams with the Eclipse Memory analyzer or your favorite memory tool (the JDK has some as well).  If you do find leaks, you might check if the same behavior occurs with the latest WildFly version. 

Scott