[
https://issues.apache.org/jira/browse/CHUKWA-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400240#comment-13400240
]
Eric Yang commented on CHUKWA-640:
----------------------------------
This patch is making registration of the adaptors async. This will cause data
loss, if the registration is never succeeded during the life cycle of the
running program. TestAdaptorController test cases are failing due to the
registration keeping the agent controlling port busy and new agent was unable
to bind to the same port due to race conditions between agent and parent
program. Given the reasons, I think we should not allow async adaptor
registration. Instead, it may be better to use SocketAppender with
SocketAdaptor, if you like to allow your program continue execution without
logging.
> JVM not terminating if agent is not started
> -------------------------------------------
>
> Key: CHUKWA-640
> URL: https://issues.apache.org/jira/browse/CHUKWA-640
> Project: Chukwa
> Issue Type: Bug
> Components: Data Collection
> Affects Versions: 0.5.0
> Reporter: Abhijit Dhar
> Assignee: Abhijit Dhar
> Attachments: patch2.txt
>
>
> I am seeing that if my agents are not up, it is preventing my program to
> terminate.
> I'm using ChukwaDailyRollingFileAppender.
> I debugged and found that ChukwaAgentController tries to retry and schedules
> to create a new adapter.
> Since it is not a daemon thread, my program just keeps waiting for all these
> retry scheduled threads to finish even after my main method finishes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
