• Post Reply Bookmark Topic Watch Topic
  • New Topic

Using JMS in websphere  RSS feed

ananthakrishnan krishnan
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While using JMS with the websphere we need to do two things:
1. do a jndi lookup to get the name of context factory of the destination (queue/topic) from which we obtain the connection and the session
2. do a jndi lookup to get the actual destination of the queue
So assume we have myQueueFactory and myQueue as the 2 aliases bound to jndi which I use in the sender and the receiver.
Now my question is, why do we need to provide the context factory alias, why cannot we use something like a common queue factory alias with which we manage all the queues. Why is this alias name for the factory essential at all, is it not enough if we do all our manipulations using a commonly provided context factory alias and our application specific destination (queue/topic) alias?
I have one more question, can someone point out to where I can find the JMS server implementation. I am interested in knowing the way the JMS server manages the sender sending messages, how it manages delegating these messages to the receivers and how it keeps adding new instances of the receivers to itself. I wanted to know the model used to achieve this, threads or some kind of polling mechanism or soemthing like that? If someone knows this can they let me in on this?
Thanks in advance,
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!