Otto Chrons created AMQNET-492:
----------------------------------
Summary: MessageId assumed to be a number
Key: AMQNET-492
URL: https://issues.apache.org/jira/browse/AMQNET-492
Project: ActiveMQ .Net
Issue Type: Bug
Components: NMS, Stomp
Affects Versions: 1.5.4
Environment: Windows8, VisualStudio Express 2013
Reporter: Otto Chrons
Assignee: Jim Gomes
When NMS.Stomp receives a message with a messageId containing something else
than a number, it will throw an exception:
{noformat}
Unhandled Exception: Apache.NMS.NMSException: Input string was not in a correct
format. ---> System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options,
NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt64(String value, NumberStyles options,
NumberFormatInfo numfmt)
at Apache.NMS.Stomp.Commands.MessageId.SetValue(String messageKey)
at Apache.NMS.Stomp.Protocol.StompWireFormat.ReadMessage(StompFrame frame)
at Apache.NMS.Stomp.Protocol.StompWireFormat.CreateCommand(StompFrame frame)
at Apache.NMS.Stomp.Protocol.StompWireFormat.Unmarshal(BinaryReader dataIn)
at Apache.NMS.Stomp.Transport.Tcp.TcpTransport.ReadLoop()
--- End of inner exception stack trace ---
at Apache.NMS.Stomp.MessageConsumer.Dequeue(TimeSpan timeout)
at Apache.NMS.Stomp.MessageConsumer.Receive(TimeSpan timeout)
{noformat}
Message headers (according to Apollo web UI)
content-length 50652
correlation-id 5e3b57eae6af6d54e0426dae4ef14732
destination /queue/OCRRequest
message-id ID:default-3ec-17
receipt 18
persistent true
transformation TEXT
reply-to
/queue/temp.default.default-3ec.d1b799a4-b165-422f-b5cc-dd2cb4ff5442
According to the specification the messageId is a string and doesn't
necessarily contain a valid number following the semicolon.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)