[jira] Updated: (AMQNET-173) System.FormatExceptions due to parsing bug in StompHelper.cs

["Jim Gomes (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQNET-173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Gomes updated AMQNET-173:
-----------------------------

    Fix Version/s: 1.2.0

> System.FormatExceptions due to parsing bug in StompHelper.cs
> ------------------------------------------------------------
>
>                 Key: AMQNET-173
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-173
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: Stomp
>    Affects Versions: 1.1.0
>         Environment: Windows XP Pro SP3, Visual Studio Team System 2008 Architecture Edition SP1, NMS 1.1.0, StompConnect, OpenMQ 4.3
>            Reporter: David Morris
>            Assignee: Jim Gomes
>            Priority: Minor
>             Fix For: 1.2.0
>
>
> While developing a C# application using NMS to talk to an OpenMQ broker via StompConnect (which works beautifully, btw), I noticed a couple of System.FormatExceptions being reported in the VStudio console.  I traced the exceptions back to StompHelper.cs in lines 171 and 211.  Those lines are attempting to call Int32.Parse on a component of the message ID, specifically the last octet of the MAC address component which is immediately followed by a closing parenthesis.  The paren is apparently causing the exception.  The exception is caught and logged by the Tracer before the method exits, but several attributes of the "answer" object are being left uninitialized as a result.  Not a fatal bug to me yet because I'm not using those attributes, but it could be for others.  Plus the exception reports bug me.  ;)
> This JIRA entered per e-mail exchange with Jim Gomes:
> "Thanks for letting me know about this.  Yes, I agree that this should be cleaned up, but I would like to wait for either a patch release or include it in version 1.2.0.  If you enter a JIRA for this, I can more easily track it and get it fixed.  Thanks!"
> Bug exists in 1.1.0 RC2 as well as proposed official release currently up for vote.

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