[
https://issues.apache.org/activemq/browse/AMQNET-29?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
james strachan moved AMQ-985 to AMQNET-29:
------------------------------------------
Fix Version/s: (was: 4.1.0)
1.0
Component/s: (was: NMS (C# client))
Affects Version/s: (was: 4.0.2)
Key: AMQNET-29 (was: AMQ-985)
Project: ActiveMQ .Net (was: ActiveMQ)
> TcpTransportFactory adds LoggingTransport after WireFormatNegotiator
> --------------------------------------------------------------------
>
> Key: AMQNET-29
> URL: https://issues.apache.org/activemq/browse/AMQNET-29
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Environment: Windows
> Reporter: Rob Lugt
> Assigned To: james strachan
> Priority: Minor
> Fix For: 1.0
>
>
> The TcpTransportFactory class will insert a LoggingTransport filter into the
> transport chain if the useLogging=true attribute is set. However, it
> currently adds the LoggingTransport after the WireFormatNegotiator, which
> means that the wire format negotiation packets are excluded from the log
> output. This can be simply rectified by adding the LoggingTransport
> immediately after the TcpTransport. e.g.
> public ITransport CreateTransport(Uri location)
> {
> // Console.WriteLine("Opening socket to: " + host + " on port: "
> + port);
> Socket socket = Connect(location.Host, location.Port);
> TcpTransport tcpTransport = new TcpTransport(socket);
> ITransport rc = tcpTransport;
> // At present the URI is parsed for options by the
> ConnectionFactory
> if (UseLogging)
> {
> rc = new LoggingTransport(rc);
> }
> rc = new WireFormatNegotiator(rc, tcpTransport.Wireformat);
> ...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
