truncated message

[Glennstar]

Hi,
I'm not sure if this issue has already been raised or not so apologies
if I'm covering old ground here.
I have an issue where one of my processing is pushing the size of the
message over 4K. These messages are intermittently truncated. They are
text only so I am not making any use of message length processing of
any kind.
Interestingly this is intermittent and the original, in tact, message
is delivered properly once in 5 or 6 attempts. When checking the frame
header the correct message length is reported and does not match the
message body length.

Any feedback welcome.

Glenn

[David Snopek]

Hrm. In our application at my old employer we sent messages that were
in the 100s of Kb or even a few Mb (they were images Base64 encoded).
We didn't encounter this problem. And I can tell you that there is no
limit in the MQ itself.

It has to be coming from something else in the stack. Could be a bug
in a dependency of the MQ? Or, due to the intermittent nature of it,
I'm inclined to suspect something on the network. A lot of our
problems stemmed from something on the network killing connections.
Although, that really should cause a failure not send the message
truncated.

Non-deterministic problems are the worst!

Regards,
David.

2011/3/29 Glennstar <goo...@destar.co.uk>:

> --
> You received this message because you are subscribed to the Google Groups "PoCo::MQ" group.
> To post to this group, send email to poc...@googlegroups.com.
> To unsubscribe from this group, send email to pocomq+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pocomq?hl=en.
>
>

--
Blog: http://www.linguatrek.com
Product: http://www.bibliobird.com

[Glennstar]

David,
Thanks for coming back to me so quickly!
I have checked a number of things including the versions of code
running on the MQ server. This does nothing other than run PoCo::MQ so
it was quite straight forward. Unfortunately everything appears to be
up to date. I then connected our test server to the live MQ and notice
that the message was always passed correctly - which is why the code
passed its tests and was released into the wild.

Further analysis showed a difference in the Net::Stomp libraries. I
have subsequently updated the version of Net::Stomp on the live server
and it appears to have corrected the problem. The previous version was
0.38 and it now on 0.40.

Thanks for your time and I hope this helps anyone else who may have
this issue.

Glenn

> > For more options, visit this group athttp://groups.google.com/group/pocomq?hl=en.

[Kevin Esteb]

What version of POE::Filter::Stomp are you running? What is creating the messages?

[Glennstar]

Kevin,
POE::Filter::Stomp is version 0.04.
The message is being created by a Perl CGI script using Net::Stomp. I
am sure it is nothing to do with the creation of the message as it is
being intermittently returned correctly so must be to do with the
receipt of the message rather than the write.

Glenn

> > For more options, visit this group athttp://groups.google.com/group/pocomq?hl=en.