You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/04/26 11:48:00 UTC

[jira] [Work logged] (ARTEMIS-2323) NettyTransport should allow to send requests with void promises

     [ https://issues.apache.org/jira/browse/ARTEMIS-2323?focusedWorklogId=233462&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-233462 ]

ASF GitHub Bot logged work on ARTEMIS-2323:
-------------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Apr/19 11:47
            Start Date: 26/Apr/19 11:47
    Worklog Time Spent: 10m 
      Work Description: franz1981 commented on pull request #2647: ARTEMIS-2323 NettyTransport should also send requests with void promises
URL: https://github.com/apache/activemq-artemis/pull/2647
 
 
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 233462)
            Time Spent: 10m
    Remaining Estimate: 0h

> NettyTransport should allow to send requests with void promises
> ---------------------------------------------------------------
>
>                 Key: ARTEMIS-2323
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2323
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: AMQP, STOMP
>            Reporter: Francesco Nigro
>            Assignee: Justin Bertram
>            Priority: Minor
>             Fix For: 2.8.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> AmqpConnection is using NettyTransport::send without making use of ChannelFuture 
> return type, but NettyTcpTransport/NettyWSTransport always allocate a new ChannelPromise
> on each call.
> If such ChannelFuture isn't needed (like STOMP does) it would be better to avoid the ChannelPromise instantiation and enhance the API with a proper method.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)