[
https://issues.apache.org/jira/browse/KNOX-459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14190024#comment-14190024
]
Larry McCay commented on KNOX-459:
----------------------------------
Hi [~jritte] - Could I bother you for a little more info?
It would be really helpful if you could post your knox topology file and maybe
a gateway.log file that includes an interaction that leaks.
If you change the log level in conf/gateway-log4j.properties to DEBUG for the
following loggers - that would give us a bit more info too:
log4j.logger.org.apache.http.client
log4j.logger.org.apache.shiro
You should be able to just uncomment them out in the file.
Please scrub the files that you attach of any internal hostnames and the like
before posting them.
The topology will give us an idea of your LDAP configuration and the new
details from the loggers should cover the creation of sockets for
authenticating incoming requests and the dispatches to the backend services.
It would also be good to know the JDK that you are using - are you using an IBM
JVM?
> Apache knox appears to be leaking sockets
> -----------------------------------------
>
> Key: KNOX-459
> URL: https://issues.apache.org/jira/browse/KNOX-459
> Project: Apache Knox
> Issue Type: Bug
> Components: Release, Server
> Affects Versions: 0.4.0
> Environment: RHEL 6.4 on IBM x3650 hardware. Running Hortonworks HDP
> 2.1.3 product.
> Reporter: Josh Ritter
>
> Sockets are left open each time a call to rest api is initiated. Tried
> updating timeout value in config, no affect.
> [root@hdptestsrv01 knox]# ps -ef|grep knox
> root 9310 6431 0 14:42 pts/0 00:00:00 su - knox
> knox 9311 9310 0 14:42 pts/0 00:00:00 -bash
> knox 13813 1 1 14:46 pts/0 00:00:30 /usr/java/latest/bin/java -Xmx4G -jar
> /usr/lib/knox/bin/gateway.jar
> root 20252 6499 0 15:11 pts/1 00:00:00 grep knox
> [root@hdptestsrv01 knox]# lsof -p 13813|grep "sock"|wc -l
> 2290
> [root@hdptestsrv01 knox]# lsof -p 13813|grep "sock"
> java 13813 knox 149u sock 0,6 0t0 52410 can't identify protocol
> java 13813 knox 150u sock 0,6 0t0 52411 can't identify protocol
> java 13813 knox 151u sock 0,6 0t0 52412 can't identify protocol
> java 13813 knox 152u sock 0,6 0t0 52413 can't identify protocol
> java 13813 knox 153u sock 0,6 0t0 52414 can't identify protocol
> java 13813 knox 154u sock 0,6 0t0 52415 can't identify protocol
> java 13813 knox 155u sock 0,6 0t0 52416 can't identify protocol
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
