You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Martin Cekal (Created) (JIRA)" <ji...@apache.org> on 2012/01/12 11:34:39 UTC

[jira] [Created] (AMQ-3658) TransportListener is not notified on send operation

TransportListener is not notified on send operation
---------------------------------------------------

                 Key: AMQ-3658
                 URL: https://issues.apache.org/jira/browse/AMQ-3658
             Project: ActiveMQ
          Issue Type: Bug
          Components: JMS client, Transport
    Affects Versions: 5.5.1, 5.5.0
         Environment: all platforms
            Reporter: Martin Cekal


If you add/set TransportListener on connection/connectionfactory, the listener receives notification via onCommand(Object command) method for many events performed on the connection. You can use this feature for counting received messages  (DispatchMessage is sent to onCommand method), but there is no event signals to TransportListener that any producer sent out a message via the connection.



--
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

        

[jira] [Closed] (AMQ-3658) TransportListener is not notified on send operation

Posted by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3658.
-----------------------------

    Resolution: Not A Problem

The transport listener is not meant to listen to messages on the outbound path via onCommand, this callback is used for incoming messages only.  
                
> TransportListener is not notified on send operation
> ---------------------------------------------------
>
>                 Key: AMQ-3658
>                 URL: https://issues.apache.org/jira/browse/AMQ-3658
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client, Transport
>    Affects Versions: 5.5.0, 5.5.1
>         Environment: all platforms
>            Reporter: Martin Cekal
>            Priority: Minor
>
> If you add/set TransportListener on connection/connectionfactory, the listener receives notification via onCommand(Object command) method for many events performed on the connection. You can use this feature for counting received messages  (DispatchMessage is sent to onCommand method), but there is no event signals to TransportListener that any producer sent out a message via the connection.

--
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

        

[jira] [Updated] (AMQ-3658) TransportListener is not notified on send operation

Posted by "Martin Cekal (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AMQ-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Cekal updated AMQ-3658:
------------------------------

    Priority: Minor  (was: Major)
    
> TransportListener is not notified on send operation
> ---------------------------------------------------
>
>                 Key: AMQ-3658
>                 URL: https://issues.apache.org/jira/browse/AMQ-3658
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client, Transport
>    Affects Versions: 5.5.0, 5.5.1
>         Environment: all platforms
>            Reporter: Martin Cekal
>            Priority: Minor
>
> If you add/set TransportListener on connection/connectionfactory, the listener receives notification via onCommand(Object command) method for many events performed on the connection. You can use this feature for counting received messages  (DispatchMessage is sent to onCommand method), but there is no event signals to TransportListener that any producer sent out a message via the connection.

--
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

        

[jira] [Commented] (AMQ-3658) TransportListener is not notified on send operation

Posted by "Martin Cekal (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AMQ-3658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13185649#comment-13185649 ] 

Martin Cekal commented on AMQ-3658:
-----------------------------------

Thank You for info, is this documented somewhere? Not clear to me why inbound messages are and outbound are not events for TransportListener. Is there any nice way how to monitor sent messages and avoid wrapping/proxy of Producers on a client? Thanks
                
> TransportListener is not notified on send operation
> ---------------------------------------------------
>
>                 Key: AMQ-3658
>                 URL: https://issues.apache.org/jira/browse/AMQ-3658
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: JMS client, Transport
>    Affects Versions: 5.5.0, 5.5.1
>         Environment: all platforms
>            Reporter: Martin Cekal
>            Priority: Minor
>
> If you add/set TransportListener on connection/connectionfactory, the listener receives notification via onCommand(Object command) method for many events performed on the connection. You can use this feature for counting received messages  (DispatchMessage is sent to onCommand method), but there is no event signals to TransportListener that any producer sent out a message via the connection.

--
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