[AMQNET-442] Clients with cultures where decimalpoint separator is other than "." fails to connect because version no is parsed as float/Single

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 1.5.3
• Fix Version/s: 1.6.0
• Component/s: Stomp
• Assignee: Jim Gomes
• Reporter: Roy Müller
• Created: 19/Sep/13 10:25
• Updated: 19/Sep/13 10:35
• Resolved: 19/Sep/13 10:35

Description

Client connecting with STOMP fails with System.FormatException: Input string was not in a correct format. This happens on computers with a culture that has eg. "," as decimal separator instead of ".".

DEBUG: Exception received in the Inactivity Monitor: System.FormatException: Input string was not in a correct format.
at System.Number.ParseSingle(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Single.Parse(String s)
at Apache.NMS.Stomp.Protocol.StompWireFormat.ReadConnected(StompFrame frame) in c:\dev\NMS.Stomp\src\main\csharp\Protocol\StompWireFormat.cs:line 199
at Apache.NMS.Stomp.Protocol.StompWireFormat.CreateCommand(StompFrame frame) in c:\dev\NMS.Stomp\src\main\csharp\Protocol\StompWireFormat.cs:line 153
at Apache.NMS.Stomp.Protocol.StompWireFormat.Unmarshal(BinaryReader dataIn) in c:\dev\NMS.Stomp\src\main\csharp\Protocol\StompWireFormat.cs:line 123
at Apache.NMS.Stomp.Transport.Tcp.TcpTransport.ReadLoop() in c:\dev\NMS.Stomp\src\main\csharp\Transport\Tcp\TcpTransport.cs:line 285

Issue Links

• duplicates: AMQNET-411 NMS.Stomp: System.FormatException in the Inactivity Monitor on Windows 8 with a non US (European) Current Culture