{"action":"created","issue":{"url":"https://api.github.com/repos/elasticsearch/logstash/issues/2555","labels_url":"https://api.github.com/repos/elasticsearch/logstash/issues/2555/labels{/name}","comments_url":"https://api.github.com/repos/elasticsearch/logstash/issues/2555/comments","events_url":"https://api.github.com/repos/elasticsearch/logstash/issues/2555/events","html_url":"https://github.com/elasticsearch/logstash/issues/2555","id":57111145,"number":2555,"title":"Logstash 1.4.2/Windows 2012 R2/JDK java version \"1.7.0_71\" memory leak","user":{"login":"nabheet","id":1319809,"avatar_url":"https://avatars.githubusercontent.com/u/1319809?v=3","gravatar_id":"","url":"https://api.github.com/users/nabheet","html_url":"https://github.com/nabheet","followers_url":"https://api.github.com/users/nabheet/followers","following_url":"https://api.github.com/users/nabheet/following{/other_user}","gists_url":"https://api.github.com/users/nabheet/gists{/gist_id}","starred_url":"https://api.github.com/users/nabheet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nabheet/subscriptions","organizations_url":"https://api.github.com/users/nabheet/orgs","repos_url":"https://api.github.com/users/nabheet/repos","events_url":"https://api.github.com/users/nabheet/events{/privacy}","received_events_url":"https://api.github.com/users/nabheet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-02-10T00:13:36Z","updated_at":"2015-02-10T19:33:22Z","closed_at":null,"body":"Here is to hoping you guys can help with this:\r\n\r\nC:\\logstash>java -version\r\njava version \"1.7.0_71\"\r\nJava(TM) SE Runtime Environment (build 1.7.0_71-b14)\r\nJava HotSpot(TM) 64-Bit Server VM (build 24.71-b01, mixed mode)\r\n\r\nC:\\logstash>ver\r\nMicrosoft Windows [Version 6.3.9600]\r\n\r\nJRuby version:\r\n![image](https://cloud.githubusercontent.com/assets/1319809/6118920/f5f58cda-b07f-11e4-8468-1669f2042267.png)\r\n\r\n\r\nC:\\logstash>bin\\logstash agent --config conf.d\r\n←[33mUsing milestone 2 input plugin 'eventlog'. This plugin should be stable, bu\r\nt if you see strange behavior, please let us know! For more information on plugi\r\nn milestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:war\r\nn}←[0m\r\n←[33mUsing milestone 1 output plugin 'rabbitmq'. This plugin should work, but wo\r\nuld benefit from use by folks like you. Please let us know if you find bugs or h\r\nave suggestions on how to improve this plugin.  For more information on plugin m\r\nilestones, see http://logstash.net/docs/1.4.2/plugin-milestones {:level=>:warn}←\r\n[0m\r\n\r\ninput.Eventlog.conf:\r\ninput {\r\n&nbsp;&nbsp;eventlog {\r\n&nbsp;&nbsp;&nbsp;&nbsp;logfile  => \"System\"\r\n&nbsp;&nbsp;&nbsp;&nbsp;tags => [ \"system\", \"windows\", \"event_log\", \"system\"]\r\n&nbsp;&nbsp;&nbsp;&nbsp;type => \"system_windows_event_log_system\"\r\n&nbsp;&nbsp;}\r\n}\r\n\r\noutput.RabbitMq.conf\r\noutput {\r\n&nbsp;&nbsp;rabbitmq {\r\n&nbsp;&nbsp;&nbsp;&nbsp;durable => false\r\n&nbsp;&nbsp;&nbsp;&nbsp;exchange => \"my-exchange\"\r\n&nbsp;&nbsp;&nbsp;&nbsp;exchange_type => \"topic\"(required)\r\n&nbsp;&nbsp;&nbsp;&nbsp;host => \"my-server-name\"\r\n&nbsp;&nbsp;&nbsp;&nbsp;key => \"some-topic\"\r\n&nbsp;&nbsp;&nbsp;&nbsp;password => \"my-rabbit-password\"\r\n&nbsp;&nbsp;&nbsp;&nbsp;persistent => false\r\n&nbsp;&nbsp;&nbsp;&nbsp;user => \"my-rabbit-user\"\r\n&nbsp;&nbsp;}\r\n}\r\n\r\nAnd I set the LS_MAX_MEM to be 256m for debugging.\r\n\r\nNow the interesting bit is that as I keep this running for about two hours or so, logstash stops publishing and starts filling up the logfile with interesting errors and then eventually the JVM crashes.\r\n\r\nHere is a screenshot from VisualVM JVM profiler:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/1319809/6118760/401b5fa8-b07e-11e4-9835-ed5caeda7f1c.png)\r\n\r\nHere is the screenshot highlighting the memory leak:\r\n\r\n![image](https://cloud.githubusercontent.com/assets/1319809/6118780/870bf198-b07e-11e4-96b4-d1a19dd8f02a.png)\r\n\r\nReferring to the screenshot, please notice the number of threads called \"RMI TCP Connection (#number) - {IP_ADDRESS}\". This thread list keeps increasing and the \"Finished\" threads are never garbage collected. Eventually this just crashes the JVM.\r\n\r\nCan you please advise on how to further debug the issue? Or suggest how I could resolve the issue.\r\n\r\nThank you."},"comment":{"url":"https://api.github.com/repos/elasticsearch/logstash/issues/comments/73767008","html_url":"https://github.com/elasticsearch/logstash/issues/2555#issuecomment-73767008","issue_url":"https://api.github.com/repos/elasticsearch/logstash/issues/2555","id":73767008,"user":{"login":"nabheet","id":1319809,"avatar_url":"https://avatars.githubusercontent.com/u/1319809?v=3","gravatar_id":"","url":"https://api.github.com/users/nabheet","html_url":"https://github.com/nabheet","followers_url":"https://api.github.com/users/nabheet/followers","following_url":"https://api.github.com/users/nabheet/following{/other_user}","gists_url":"https://api.github.com/users/nabheet/gists{/gist_id}","starred_url":"https://api.github.com/users/nabheet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nabheet/subscriptions","organizations_url":"https://api.github.com/users/nabheet/orgs","repos_url":"https://api.github.com/users/nabheet/repos","events_url":"https://api.github.com/users/nabheet/events{/privacy}","received_events_url":"https://api.github.com/users/nabheet/received_events","type":"User","site_admin":false},"created_at":"2015-02-10T19:33:22Z","updated_at":"2015-02-10T19:33:22Z","body":"<gut_feeling>\r\nThere are some objects that are not getting garbage collected on the java/jruby/ruby side and are holding on to references to things on the Windows/WMI side and then eventually the windows interface guy says \"I can't give you any more things\" ... Kaboom ...\r\n</gut_feeling>"}}