Hi Remsy
Hi. I resolved it bu setting transport.jms.Destination to
queue://MANAGER/MY_QUEUE instead of the property name defined in the
JNDI .bindings file (use the property value, not the name for the queue).
Cool..
However I still get:
2008-09-30 13:13:19,820 [7.28.130.231-WH24CU6052] [asyncDelivery0]
DEBUG JMSMessageReceiver Received JMS message to destination: null
Message ID : ID:c3e2d840d4d8c8f54040404040404040c31305af0d2b2940
Correlation ID : null
ReplyTo ID : null
2008-09-30 13:13:19,836 [7.28.130.231-WH24CU6052] [jms-Worker-1] DEBUG
BaseUtils Non SOAP/XML message received
but the messages get processed succesfully . Do you know how to get
rid of these ?
These are debug messages, and you can ignore them, or turn off debug
from the log4j.properties for the category. It seems like we still do
not resolve the correct destination quite right, after getting a message
(Received JMS message to destination: null). The "Non SOAP/XML message
received" message is because you have sent a plain text message - which
is supported by the ESB.. So anyway if the only issue is the log
messages above, you can safely ignore them
asankha
_______________________________________________
Esb-java-user mailing list
[email protected]
http://mailman.wso2.org/cgi-bin/mailman/listinfo/esb-java-user
