Posted: Thu Nov 29, 2007 6:17 am Post subject: MQ-JMS: TopicConnectionFactory transport type
Novice
Joined: 21 Nov 2007 Posts: 17
I need one info (appreciate your help): Is it necessary to set the Transport type as BIND for the TopicConnectionFactory when the client program uses bindings file for JNDI lookup?
My problem is:
Whether I make the TCF transport type as BIND or CLIENT using the JMSAdmin tool and use the client program that uses bindings file for JNDI lookups, if a publisher puts a jms TextMessage into the the topic, the subscriber receives a jms BytesMessage. Why? How to correct this?
Because the ByteMessage/TextMessage issue sounds a lot like where that thread ended. What have you tried since? How have you recoded the TCF? What does the manual say about transport type? _________________ Honesty is the best policy.
Insanity is the best defence.
Transport types have nothing to do with the .bindings file but for the fact that the definition of the qcf/tcf in the .bindings file will determine the transport type.
Furthermore you should not have anything to do with the transport type as you are given a fully initialized qcf/tcf from the JNDI lookup....
Enjoy
Maybe you should read up on how JMS works with JNDI ? _________________ MQ & Broker admin
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum