Claus:
Using tracer, I could figure out where the problem is. It seems like these
unsafe headers are coming from the JMSDestination header deserialization:
JMSDestination=Sun Java System MQ Destination
getName(): DeliveryChannel0Q
Class: com.sun.messaging.BasicQueue
getVERSION(): 3.0
isReadonly(): false
getProperties(): {imqDestinationName=DeliveryChannel0Q,
imqDestinationDescription=A Description for the Destination Object},
routerRoute=http://host:xxxx/spot-datapush-callback/CallbackServlet/harinair,
JMSRedelivered=false, JMSExpiration=0,
JMSMessageID=ID:126-207.88.152.31(b0:bc:6b:e1:9e:82)-43857-1243375247716,
JMSDeliveryMode=2, JMSCorrelationID=null, JMSPriority=4}
However I am unable to remove the JMSDestination header using the
message.removeHeader(). Any reasons?
Hari Gangadharan
Architect
Globalstar
http://www.harinair.com
Claus Ibsen-2 wrote:
>
> Have you checked Exchange properties?
>
> Anyway attaching a debugger to your code in the prcessor, then you can
> inspect the exchange.
>
> The tracer is also suitable to log the message how they are routed in
> Camel.
> You can control how much it should log etc.
> http://camel.apache.org/tracer.html
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Open Source Integration: http://fusesource.com
> Blog: http://davsclaus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
>
--
View this message in context:
http://www.nabble.com/Unsafe-Headers-present-in-HTTP-Component-tp23661949p23732341.html
Sent from the Camel - Users mailing list archive at Nabble.com.
