{"action":"created","issue":{"url":"https://api.github.com/repos/wildfly/wildfly-core/issues/1140","labels_url":"https://api.github.com/repos/wildfly/wildfly-core/issues/1140/labels{/name}","comments_url":"https://api.github.com/repos/wildfly/wildfly-core/issues/1140/comments","events_url":"https://api.github.com/repos/wildfly/wildfly-core/issues/1140/events","html_url":"https://github.com/wildfly/wildfly-core/pull/1140","id":109409626,"number":1140,"title":"[WFCORE-1026] Upgrade jboss-logmanager from 2.0.0.Final to 2.0.2.Final","user":{"login":"jamezp","id":420065,"avatar_url":"https://avatars.githubusercontent.com/u/420065?v=3","gravatar_id":"","url":"https://api.github.com/users/jamezp","html_url":"https://github.com/jamezp","followers_url":"https://api.github.com/users/jamezp/followers","following_url":"https://api.github.com/users/jamezp/following{/other_user}","gists_url":"https://api.github.com/users/jamezp/gists{/gist_id}","starred_url":"https://api.github.com/users/jamezp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamezp/subscriptions","organizations_url":"https://api.github.com/users/jamezp/orgs","repos_url":"https://api.github.com/users/jamezp/repos","events_url":"https://api.github.com/users/jamezp/events{/privacy}","received_events_url":"https://api.github.com/users/jamezp/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/wildfly/wildfly-core/labels/hold","name":"hold","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":13,"created_at":"2015-10-02T00:27:24Z","updated_at":"2015-10-08T21:26:41Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/wildfly/wildfly-core/pulls/1140","html_url":"https://github.com/wildfly/wildfly-core/pull/1140","diff_url":"https://github.com/wildfly/wildfly-core/pull/1140.diff","patch_url":"https://github.com/wildfly/wildfly-core/pull/1140.patch"},"body":"Contains only a few minor changes. Two bug fixes and two performance changes. https://github.com/jboss-logging/jboss-logmanager/compare/2.0.0.Final...jamezp:2.0.2.Final"},"comment":{"url":"https://api.github.com/repos/wildfly/wildfly-core/issues/comments/146690747","html_url":"https://github.com/wildfly/wildfly-core/pull/1140#issuecomment-146690747","issue_url":"https://api.github.com/repos/wildfly/wildfly-core/issues/1140","id":146690747,"user":{"login":"jamezp","id":420065,"avatar_url":"https://avatars.githubusercontent.com/u/420065?v=3","gravatar_id":"","url":"https://api.github.com/users/jamezp","html_url":"https://github.com/jamezp","followers_url":"https://api.github.com/users/jamezp/followers","following_url":"https://api.github.com/users/jamezp/following{/other_user}","gists_url":"https://api.github.com/users/jamezp/gists{/gist_id}","starred_url":"https://api.github.com/users/jamezp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamezp/subscriptions","organizations_url":"https://api.github.com/users/jamezp/orgs","repos_url":"https://api.github.com/users/jamezp/repos","events_url":"https://api.github.com/users/jamezp/events{/privacy}","received_events_url":"https://api.github.com/users/jamezp/received_events","type":"User","site_admin":false},"created_at":"2015-10-08T21:26:41Z","updated_at":"2015-10-08T21:26:41Z","body":"Just making a general comment so that I remember the status.\r\n\r\nThere is an issue with the log manager where the reconnect thread will continue to attempt to reconnect even if the handler is closed. I'm reworking the logmanager a bit more which will lead to a 2.0.3.Final release and an upgrade for that.\r\n\r\nThere's still an underlying issue with the `SyslogAuditLogHandler`. There's potential for the internal handler to fail to set the custom output stream if the socket can't connect. This causes the default `TcpOutputStream` to be used which may attempt to reconnect if a write makes it through. The `SyslogAuditLogHandler` does it's own reconnect algorithm. Regardless a failure to properly construct the internal handler should cause the handler to close or not be usable.\r\n\r\nThere's still an underlying issue somewhere though with the internal handler writing to either the wrong socket or the `SimpleLogServer` isn't accepting the correct connection. This is what needs to be debugged to determine what the issue is."}}