JMS: Truely asynchronize?

I quoted following text from website:

My questions is how to get truely asynchronize call? When receiving message, JMS seems to use one thread to keep asking whether message is arrived or not?

18.4.2. Synchronous Receiving

While JMS is typically associated with asynchronous processing, it is possible to consume messages synchronously. The overloaded receive methods provide this functionality. During a synchronous receive the calling thread blocks until a message becomes available. This can be a dangerous operation since the calling thread can potentially be blocked indefinitely. The property receiveTimeout specifies how long the receiver should wait before giving up waiting for a message.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JMS can be completely asynchronous. The 'other end' doesn't even need to be connected all the time and you can't get more asynchronous than that
Mick BarryJava DeveloperCommented:
>  JMS seems to use one thread to keep asking whether message is arrived or not?

That doesn't make it synchronous, that technique wcould still process message asynchronously.
And how it handles receiving the message is dependent on the server implementation, not JMS itself.
Not disagreeing with the 2 statements above, but I think both are not addressing your specific question.

JMS is just another messaging service. In virtual all messaging services (from low level sockets to MQ Series) the differentiation from syncrhonous to asynchronous messaging model has to do with:

1) polling/looping/explicitly checking for messages (syncrhonous)
2) registering a listener and a callback mechanism (asynchonous)

We are discussing asynchronous in terms of receiving the message, not handling the message. Either model can asynchronously _handle_ the method, but that is outside the JMS model at that point.

The point to be clear on is the URL you refer to is a classic synchronous polling method, not a callback method.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amazon Web Services

Are you thinking about creating an Amazon Web Services account for your business? Not sure where to start? In this course you’ll get an overview of the history of AWS and take a tour of their user interface.

JianJunShenAuthor Commented:
Refer to mrjoltcola message, where is tutorial for 2) registering a listener and a callback mechanism (asynchonous)?
I believe the book "Spring into Action" also has a good section on it, but my book is at the office so I cannot verify. I recommend buying the book if you are using Spring in your projects. It covers many useful things.

Mick BarryJava DeveloperCommented:

Thats a bit out of date btw
Do you specifically need to use 1.2?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.