You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Robert Godfrey <ro...@gmail.com> on 2007/12/19 14:32:42 UTC
Re: [java] Issue receiving messages
Hi Arnaud,
never seen that message before, an we do a lot of development /
testing on Windows (XP SP1 / 2).
have you got any way to trace what you are sending over the wire...
Are you using the string "payload-message" anywhere in your code?
-- Rob
On 19/12/2007, Arnaud Simon <ar...@orange.fr> wrote:
> Hi,
>
> I am seeing that when receiving messages:
>
> org.apache.qpid.AMQException: Unsupport MIME type of oad-message
> paylaod-mess
> at
> org.apache.qpid.client.message.MessageFactoryRegistry.createMessage(MessageF
> actoryRegistry.java:115)
> at
> org.apache.qpid.client.BasicMessageConsumer_0_8.createJMSMessageFromUnproces
> sedMessage(BasicMessageConsumer_0_8.java:84)
> at
> org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsum
> er.java:568)
> at
> org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java
> :2570)
> at
> org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:2493)
>
>
> Has anybody already seen that? This is when using a M2 broker and a trunk
> client though. It also only happens when the consumer is running on my
> Windows box. I have tested the following:
>
> Consumer Producer Broker Issue
> W W W Yes
> W W Linux Yes
> W Linux Linux Yes
> Linux W Linux No
> Linux Linux Linux No
>
> I am using the trunk on Windows and on Linux when running the clients
> (revision: 605528). So before investigating further I would like to know if
> you guys know about a potential Windows issue.
>
> Arnaud
>
>
>
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.503 / Virus Database: 269.17.4/1189 - Release Date: 18/12/2007
> 21:40
>
>
Re: [java] Issue receiving messages
Posted by Robert Greig <ro...@gmail.com>.
On 19/12/2007, Robert Godfrey <ro...@gmail.com> wrote:
> Given we've never seen anything like this in M2 -> M2 -> M2 setups, my
> first guess would be an issue in the encoder / decoder in the 0-10
> client...
Yup. My further guess would be around partial frames coming in off the
network, i.e. cumulative protocol decoder equivalent.
RG
Re: [java] Issue receiving messages
Posted by Robert Godfrey <ro...@gmail.com>.
On 19/12/2007, Arnaud Simon <as...@redhat.com> wrote:
>
> On Wed, 2007-12-19 at 13:32 +0000, Robert Godfrey wrote:
> > Hi Arnaud,
> >
> > never seen that message before, an we do a lot of development /
> > testing on Windows (XP SP1 / 2).
> >
> > have you got any way to trace what you are sending over the wire...
> >
> > Are you using the string "payload-message" anywhere in your code?
>
>
> The test is using a byte message which content is set from the string
> "-message payload-message paylaod-message payload-message paylaod". I'll
> investigate further, that may be an issue with my Windows client or with
> my network. Strangely enough I have seen such an issue with the 0.10
> client. I'll try with a real M2 client first.
>
> Thanks
>
> Arnaud
>
Given we've never seen anything like this in M2 -> M2 -> M2 setups, my
first guess would be an issue in the encoder / decoder in the 0-10
client...
-- Rob
Re: [java] Issue receiving messages
Posted by Arnaud Simon <as...@redhat.com>.
On Wed, 2007-12-19 at 13:32 +0000, Robert Godfrey wrote:
> Hi Arnaud,
>
> never seen that message before, an we do a lot of development /
> testing on Windows (XP SP1 / 2).
>
> have you got any way to trace what you are sending over the wire...
>
> Are you using the string "payload-message" anywhere in your code?
The test is using a byte message which content is set from the string
"-message payload-message paylaod-message payload-message paylaod". I'll
investigate further, that may be an issue with my Windows client or with
my network. Strangely enough I have seen such an issue with the 0.10
client. I'll try with a real M2 client first.
Thanks
Arnaud
>
> On 19/12/2007, Arnaud Simon <ar...@orange.fr> wrote:
> > Hi,
> >
> > I am seeing that when receiving messages:
> >
> > org.apache.qpid.AMQException: Unsupport MIME type of oad-message
> > paylaod-mess
> > at
> > org.apache.qpid.client.message.MessageFactoryRegistry.createMessage(MessageF
> > actoryRegistry.java:115)
> > at
> > org.apache.qpid.client.BasicMessageConsumer_0_8.createJMSMessageFromUnproces
> > sedMessage(BasicMessageConsumer_0_8.java:84)
> > at
> > org.apache.qpid.client.BasicMessageConsumer.notifyMessage(BasicMessageConsum
> > er.java:568)
> > at
> > org.apache.qpid.client.AMQSession$Dispatcher.dispatchMessage(AMQSession.java
> > :2570)
> > at
> > org.apache.qpid.client.AMQSession$Dispatcher.run(AMQSession.java:2493)
> >
> >
> > Has anybody already seen that? This is when using a M2 broker and a trunk
> > client though. It also only happens when the consumer is running on my
> > Windows box. I have tested the following:
> >
> > Consumer Producer Broker Issue
> > W W W Yes
> > W W Linux Yes
> > W Linux Linux Yes
> > Linux W Linux No
> > Linux Linux Linux No
> >
> > I am using the trunk on Windows and on Linux when running the clients
> > (revision: 605528). So before investigating further I would like to know if
> > you guys know about a potential Windows issue.
> >
> > Arnaud
> >
> >
> >
> > No virus found in this outgoing message.
> > Checked by AVG Free Edition.
> > Version: 7.5.503 / Virus Database: 269.17.4/1189 - Release Date: 18/12/2007
> > 21:40
> >
> >