Flex client can SEND but not RECEIVE messages from BlazeDS

Question

Hi there,
I built a sample chat application that should be able to send/receive messages from a JMS topic. However, I am only able to SEND messages, I am not able to receive them. Any advice/suggestions would be GREATLY appreciated as I am seriously stuck.
My setup:
- BlazeDS Turnkey
- FioranoMQ JMS provider on remote machine
What I know:
- My MXML code is good. I am able to use the exact same code and get both subscribing and publishing working when I use 'ActiveMQ' instead of 'FioranoMQ' as my JMS provider
- FioranoMQ JMS provider is working fine, my test Java clients can both subscribe and publish to the same JMS topic that the Flex app uses
- Publishing from my Flex app is working because my Java client is able to receive messages from the same topic whenever Flex messages are sent to FioranoMQ
- My Flex app is supposedly 'subscribed' to and 'connected' to the correct (streaming-amf) channel. I know this because the MXML 'Consumer' object's "subscribed" and "connected" properties are true and no fault events appear whenever I issue "consumer.subscribe()" in my Flex app.
Sample debug console log:
(I tried sending 8 JMS messages from my Java client code to the 'mytopic' topic that my Flex app is using. The end of the log shows that SOMETHING is happening after sending these messages, but notice the actual 'message' is never streamed even in the log!)
[BlazeDS] 01/27/2009 FlexSession created with id '72D3E6EED1364AD328F342F1AF59FF
69' for an Http-based client connection.
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Deserializing AMF/HTTP request
Version: 3
(Message #0 targetURI=null, responseURI=/1)
(Array #0)
[0] = (Typed Object #0 'flex.messaging.messages.CommandMessage')
operation = 5
correlationId = ""
clientId = null
timestamp = 0
body = (Object #1)
headers = (Object #2)
DSMessagingVersion = 1
DSId = "nil"
timeToLive = 0
destination = ""
messageId = "AECE3D84-789C-29B7-3413-197C7A48A7D2"
[BlazeDS] 01/27/2009 Serializing AMF/HTTP response
Version: 3
(Message #0 targetURI=/1/onResult, responseURI=)
(Externalizable Object #0 'DSK')
(Object #1)
DSMessagingVersion = 1.0
DSId = "ED38E721-2609-CF34-62A2-28D918C4BB8F"
1.233083202182E12
(Byte Array #2, Length 16)
(Byte Array #3, Length 16)
(Byte Array #4, Length 16)
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Endpoint with id 'flextest-streaming-amf' is streaming mess
age: Flex Message (flex.messaging.messages.AcknowledgeMessage)
clientId = null
correlationId = open
destination = null
messageId = ED38E793-E519-95BB-3E4C-1A7E8D716951
timestamp = 1233083202229
timeToLive = 0
body = ED38E793-E50A-2500-E2F5-7525401FD8CE
[BlazeDS] 01/27/2009 Number of streaming clients for FlexSession with id '72D3E6
EED1364AD328F342F1AF59FF69' is 1.
[BlazeDS] 01/27/2009 Number of streaming clients for endpoint with id 'flextest-
streaming-amf' is 1.
[BlazeDS] 01/27/2009 Channel endpoint flextest-streaming-amf received request.
[BlazeDS] 01/27/2009 Deserializing AMF/HTTP request
Version: 3
(Message #0 targetURI=null, responseURI=/2)
(Array #0)
[0] = (Typed Object #0 'flex.messaging.messages.CommandMessage')
operation = 0
correlationId = ""
clientId = null
timestamp = 0
body = (Object #1)
headers = (Object #2)
DSEndpoint = "flextest-streaming-amf"
DSId = "ED38E721-2609-CF34-62A2-28D918C4BB8F"
timeToLive = 0
destination = "flextest-message-destination"
messageId = "5ED8AAA4-BDA8-C8E4-D85B-197C7AC5E83A"
[BlazeDS] 01/27/2009 JMS consumer for JMS destination 'mytopic' is starting.
[BlazeDS] 01/27/2009 JMS consumer for JMS destination 'mytopic' is

Answer 1

Hi Alex, thanks for your advice. I tried reading the client-side logs, but it just physically shows what I was saying earlier - that the consumer is connected and subscribed, but no messages are coming through to it.
I've attached the output of the 'flashlog.txt' file. For the particular session shown, the flex application was sent 8 JMS messages, but as you can see nothing got through. I put a 'trace' message in the message handler function (for my consumer object), but it never gets called.
'E2513351-75DA-0837-7263-3807B91D9630' consumer set destination to 'flextest-message-destination'.
'7D784A40-DBBB-71F1-4029-3807B91D45E3' producer set destination to 'flextest-message-destination'.
'consumer' consumer subscribe.
'flextest-streaming-amf' channel endpoint set to http://localhost:8400/FLEXTEST/msgbroker/streaming-amf
'flextest-streaming-amf' channel settings are:
'flextest-streaming-amf' pinging endpoint.
'flextest-streaming-amf' channel is connected.
'flextest-streaming-amf' channel sending message:
(mx.messaging.messages::CommandMessage)
  body=(Object)#0
  clientId=(null)
  correlationId=""
  destination="flextest-message-destination"
  headers=(Object)#0
  messageId="8A592005-3C8A-4C6C-B074-380857710C00"
  operation="subscribe"
  timeToLive=0
  timestamp=0
'consumer' consumer connected.
'consumer' consumer acknowledge for subscribe. Client id '37CC5DED-A019-7110-3C89-A9926835103E' new timestamp 1233595684954
'consumer' consumer acknowledge of '8A592005-3C8A-4C6C-B074-380857710C00'.
Seems to me there can only be two explanations: either my BlazeDS configuration is incorrect (which is unlikely given that everything works if I use a ActiveMQ as my JMS provider with only trivial changes to my configuration), or there is some bug within BlazeDS that is preventing it from working properly with FioranoMQ. What do you think?