You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2007/08/31 20:28:22 UTC

[jira] Created: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

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


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.


[jira] Resolved: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes resolved AMQNET-52.
-----------------------------

    Resolution: Won't Fix

Not a bug.

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


[jira] Issue Comment Edited: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/activemq/browse/AMQNET-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40153 ] 

semog edited comment on AMQNET-52 at 9/20/07 8:44 AM:
----------------------------------------------------------

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.useLogging=true}}* turns on logging for the transport.  I will issue another patch to undo these changes.

      was (Author: semog):
    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.


[jira] Closed: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes closed AMQNET-52.
---------------------------


> 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
>         Attachments: ConnectionFactory.cs.patch.txt, IConnectionFactory.cs.patch.txt, TcpTransportFactory.cs.patch.txt
>
>   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.


[jira] Commented: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
    [ 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.


[jira] Updated: (AMQNET-52) Enhance the IConnectionFactory to create a connection that uses logging

Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/activemq/browse/AMQNET-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes updated AMQNET-52:
----------------------------

    Attachment: IConnectionFactory.cs.patch.txt
                TcpTransportFactory.cs.patch.txt
                ConnectionFactory.cs.patch.txt

Patches to undo this particular change included in the Patch Collection issue.

> 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
>         Attachments: ConnectionFactory.cs.patch.txt, IConnectionFactory.cs.patch.txt, TcpTransportFactory.cs.patch.txt
>
>   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.