activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Gomes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging
Date Thu, 20 Sep 2007 15:45:23 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40153
] 

Jim Gomes commented on AMQNET-52:
---------------------------------

This issue is not a bug.  There is already a way of turning on logging by setting a parameter
in the broker URL.  To turn on logging, set the parameter in the broker URL as follows:

{{tcp://brokerhost:61612?transport.useLogging=true}}

The parameter *{{transport.userLogging=true}}* turns on logging for the transport.  I will
issue another patch to undo these changes.

> Enhance the IConnectionFactory to create a connection that uses logging
> -----------------------------------------------------------------------
>
>                 Key: AMQNET-52
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-52
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: ActiveMQ Client
>         Environment: Windows XP SP2, .NET 2.0
>            Reporter: Jim Gomes
>            Assignee: James Strachan
>            Priority: Minor
>   Original Estimate: 30 minutes
>  Remaining Estimate: 30 minutes
>
> The low-level TcpTransportFactory supports logging, but the upper level interfaces provide
no way of turning this on.  An overloaded version of the IConnectionFactory.CreateConnection()
function should be created that will pass a boolean flag down to the low-level transport that
will turn on logging for that connection.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message