Claus Ibsen-2 wrote:
>
>
> On Thu, Aug 20, 2009 at 8:09 PM, wbustraan wrote:
>>
>> I keep getting the following message in my log files:
>>
>>
>>
>> 08-20-09 11:38 [INFO]
>> org.apache.camel.component.jms.JmsMessage(JmsMessage.java:183) - The
>> jmsMessage is not set yet, call the super's createMessageId
>>
>>
>> Is there any way to get these to stop aside from specifically filtering
>> them
>> out in my logging config?
>>
>
> What version of Camel are you using? And do you see it for *every* jms
> message.
> And what JMS broker are you connecting to.
>
>
Yes, I see it twice for every message that goes through the route.
My route looks like this:
<camel:camelContext>
<camel:endpoint id="request" uri="jms:${queue.request}"/>
<camel:route id="req-customer" streamCaching="false">
<camel:from ref="request"/>
<camel:to
uri="log:com.gfs.mps.soa.customer?level=DEBUG"/>
<!-- Umarshal XML message to Java objects -->
<camel:unmarshal>
<camel:jaxb
contextPath="com.gfs.mps.soa.customer.msg"/>
</camel:unmarshal>
<!-- Main reqCustomer business logic -->
<camel:to uri="bean:requestCustomer"/>
<!-- Marshal the Java objects back to XML -->
<camel:marshal>
<camel:jaxb
contextPath="com.gfs.mps.soa.customer.msg"/>
</camel:marshal>
<!-- Fixup the XML entities -->
<camel:to uri="bean:decode-entities"/>
</camel:route>
</camel:camelContext>
I'm using Camel 1.6.1 (FUSE) inside ServiceMix 4 and IBM Websphere MQ 6
It appears to start happening after the bean processor.
--
View this message in context:
http://www.nabble.com/JmsMessage-log-messages-tp25067092p25068398.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
