You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Marnie McCormack (JIRA)" <qp...@incubator.apache.org> on 2007/02/01 13:33:06 UTC
[jira] Updated: (QPID-336) .NET client support for field table
types requires extension (interop issue)
[ https://issues.apache.org/jira/browse/QPID-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marnie McCormack updated QPID-336:
----------------------------------
Description:
If you send a message from a Java client and then consume from a .NET client there's an error:
A first chance exception of type 'Qpid.Framing.AMQFrameDecodingException' occurred in qpid.common.dll
Additional information: Unsupported field table type: 'x' charcode120
In the .NET case, this kills the connection to the broker as well, which would seem to be a little extreme.
.NET client needs to support the same set of field table types as Java client.
was:
If you send a message from a Java client and then consume from a .NET client there's an error:
A first chance exception of type 'Qpid.Framing.AMQFrameDecodingException' occurred in qpid.common.dll
Additional information: Unsupported field table type: 'x' charcode120
In the .NET case, this kills the connection to the broker as well, which would seem to be a little extreme.
.NET client needs to support the set set of field table types as Java client.
> .NET client support for field table types requires extension (interop issue)
> ----------------------------------------------------------------------------
>
> Key: QPID-336
> URL: https://issues.apache.org/jira/browse/QPID-336
> Project: Qpid
> Issue Type: Bug
> Components: Dot Net Client
> Affects Versions: M1
> Reporter: Marnie McCormack
>
> If you send a message from a Java client and then consume from a .NET client there's an error:
> A first chance exception of type 'Qpid.Framing.AMQFrameDecodingException' occurred in qpid.common.dll
> Additional information: Unsupported field table type: 'x' charcode120
> In the .NET case, this kills the connection to the broker as well, which would seem to be a little extreme.
> .NET client needs to support the same set of field table types as Java client.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.