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/09/11 00:59:22 UTC
[jira] Created: (AMQNET-58) Exception parsing MessageId return from
TIBCO EMS connected via STOMPConnect
Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
----------------------------------------------------------------------------
Key: AMQNET-58
URL: https://issues.apache.org/activemq/browse/AMQNET-58
Project: ActiveMQ .Net
Issue Type: Bug
Components: Stomp
Environment: Windows XP SP2
.NET 2.0
STOMPConnect 1.0
TIBCO EMS 4.2.0
Reporter: Jim Gomes
Assignee: James Strachan
Priority: Blocker
Attachments: stomphelper.cs.patch.txt
Some message brokers do not return message headers in the format that NMS expects. For instance, the TIBCO EMS broker returns the following for the "message-id" header field:
"ID:EMS-SERVER.56C46A795A6FE1:48"
The StompHelper.ToMessageId() function expects to parse this field as if there were 32-bit integers delimited by colons. For example:
"ID:<Producer Sequence Id 32-bit int>:<Broker Sequence Id 32-bit int>"
However, the TIBCO EMS server is returning a non-integer Producer Sequence Id in the second record. The parsing code in StompHelper.ToMessageId() throws an exception when attempting to parse the Producer Sequence Id portion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQNET-58) Exception parsing MessageId return
from TIBCO EMS connected via STOMPConnect
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes resolved AMQNET-58.
-----------------------------
Resolution: Fixed
> Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
> ----------------------------------------------------------------------------
>
> Key: AMQNET-58
> URL: https://issues.apache.org/activemq/browse/AMQNET-58
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Environment: Windows XP SP2
> .NET 2.0
> STOMPConnect 1.0
> TIBCO EMS 4.2.0
> Reporter: Jim Gomes
> Assignee: James Strachan
> Priority: Blocker
> Attachments: StompHelper.cs.patch.txt
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Some message brokers do not return message headers in the format that NMS expects. For instance, the TIBCO EMS broker returns the following for the "message-id" header field:
> "ID:EMS-SERVER.56C46A795A6FE1:48"
> The StompHelper.ToMessageId() function expects to parse this field as if there were 32-bit integers delimited by colons. For example:
> "ID:<Producer Sequence Id 32-bit int>:<Broker Sequence Id 32-bit int>"
> However, the TIBCO EMS server is returning a non-integer Producer Sequence Id in the second record. The parsing code in StompHelper.ToMessageId() throws an exception when attempting to parse the Producer Sequence Id portion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (AMQNET-58) Exception parsing MessageId return from
TIBCO EMS connected via STOMPConnect
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes closed AMQNET-58.
---------------------------
> Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
> ----------------------------------------------------------------------------
>
> Key: AMQNET-58
> URL: https://issues.apache.org/activemq/browse/AMQNET-58
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Environment: Windows XP SP2
> .NET 2.0
> STOMPConnect 1.0
> TIBCO EMS 4.2.0
> Reporter: Jim Gomes
> Assignee: James Strachan
> Priority: Blocker
> Attachments: StompHelper.cs.patch.txt
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Some message brokers do not return message headers in the format that NMS expects. For instance, the TIBCO EMS broker returns the following for the "message-id" header field:
> "ID:EMS-SERVER.56C46A795A6FE1:48"
> The StompHelper.ToMessageId() function expects to parse this field as if there were 32-bit integers delimited by colons. For example:
> "ID:<Producer Sequence Id 32-bit int>:<Broker Sequence Id 32-bit int>"
> However, the TIBCO EMS server is returning a non-integer Producer Sequence Id in the second record. The parsing code in StompHelper.ToMessageId() throws an exception when attempting to parse the Producer Sequence Id portion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-58) Exception parsing MessageId return from
TIBCO EMS connected via STOMPConnect
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-58:
----------------------------
Attachment: (was: stomphelper.cs.patch.txt)
> Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
> ----------------------------------------------------------------------------
>
> Key: AMQNET-58
> URL: https://issues.apache.org/activemq/browse/AMQNET-58
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Environment: Windows XP SP2
> .NET 2.0
> STOMPConnect 1.0
> TIBCO EMS 4.2.0
> Reporter: Jim Gomes
> Assignee: James Strachan
> Priority: Blocker
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Some message brokers do not return message headers in the format that NMS expects. For instance, the TIBCO EMS broker returns the following for the "message-id" header field:
> "ID:EMS-SERVER.56C46A795A6FE1:48"
> The StompHelper.ToMessageId() function expects to parse this field as if there were 32-bit integers delimited by colons. For example:
> "ID:<Producer Sequence Id 32-bit int>:<Broker Sequence Id 32-bit int>"
> However, the TIBCO EMS server is returning a non-integer Producer Sequence Id in the second record. The parsing code in StompHelper.ToMessageId() throws an exception when attempting to parse the Producer Sequence Id portion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQNET-58) Exception parsing MessageId return from
TIBCO EMS connected via STOMPConnect
Posted by "Jim Gomes (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQNET-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-58:
----------------------------
Attachment: StompHelper.cs.patch.txt
Updated the patch to recreate the message-id when sending back ACK message.
> Exception parsing MessageId return from TIBCO EMS connected via STOMPConnect
> ----------------------------------------------------------------------------
>
> Key: AMQNET-58
> URL: https://issues.apache.org/activemq/browse/AMQNET-58
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Environment: Windows XP SP2
> .NET 2.0
> STOMPConnect 1.0
> TIBCO EMS 4.2.0
> Reporter: Jim Gomes
> Assignee: James Strachan
> Priority: Blocker
> Attachments: StompHelper.cs.patch.txt
>
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> Some message brokers do not return message headers in the format that NMS expects. For instance, the TIBCO EMS broker returns the following for the "message-id" header field:
> "ID:EMS-SERVER.56C46A795A6FE1:48"
> The StompHelper.ToMessageId() function expects to parse this field as if there were 32-bit integers delimited by colons. For example:
> "ID:<Producer Sequence Id 32-bit int>:<Broker Sequence Id 32-bit int>"
> However, the TIBCO EMS server is returning a non-integer Producer Sequence Id in the second record. The parsing code in StompHelper.ToMessageId() throws an exception when attempting to parse the Producer Sequence Id portion.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.