Uploaded image for project: 'Apache Avro'
  1. Apache Avro
  2. AVRO-754

NettyTransceiver: allow to provide custom ChannelFactory

Log workAgile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersWatch issueWatchersCreate sub-taskConvert to sub-taskMoveLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.5.0
    • 1.5.0
    • java
    • None

    Description

      The threads created by NettyTransceiver are non-daemon threads. The effect is that in client apps you need to properly call NettyTransceiver.close() or it will hang when done.

      In order to be able to control the kinds of threads (and thread pools) used, the attached patch allows to pass the ChannelFactory via the constructor. Alternatively, I'd also be happy with the ability to pass the ThreadFactory or the ExecutorService, or by making daemon threads the default.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            bruno Bruno Dumon Assign to me
            bruno Bruno Dumon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment