Pushing p2p TemporaryQueues

[Mark Herschberg]

I posted a problem here. But I think the root of the problem is that I'm using pull instead of using push. The listeners on the EJB server, that is, the Queues which I created through WebLogic, with Message Driven Bean listeners seem have the Queue's messages pushed to them (or else WebLogic is polling under the covers).
For the TemporaryQueue I created by the client, and listened to by the client, it's not happening. How do I get WebLogic to make the TemporaryQueue's push, instead of pull.
--Mark
[ December 30, 2002: Message edited by: Mark Herschberg ]

[Mark Herschberg]

Oh son of a *&%#! The problem was that I forgot to call start() on the QueueConnection. Boy is WebLogic unhelpful!
--Mark

[Chris Mathews]

Originally posted by Mark Herschberg:
The listeners on the EJB server, that is, the Queues which I created through WebLogic, with Message Driven Bean listeners seem have the Queue's messages pushed to them (or else WebLogic is polling under the covers).

JMS allows for both synchronous polling and an asynchronous push for the receivers. Since MDBs implement the MessageListener interface they are asynchronous receivers that get messages pushed to them. They do poll the connection occasionally to make sure it is live but that is about it for the polling. This polling period is configurable. The docs are here.

Originally posted by Mark Herschberg:
Oh son of a *&%#! The problem was that I forgot to call start() on the QueueConnection. Boy is WebLogic unhelpful!

Don't worry, this happens to the best of us. Recently, I wasted an hour on a very similar problem. I was using JMX Timers to schedule jobs in WebLogic and I couldn't get the Timer to actually fire... then I noticed that I never told the to start.
[ December 30, 2002: Message edited by: Chris Mathews ]

[Mark Herschberg]

Originally posted by Chris Mathews:

JMS allows for both synchronous polling and an asynchronous push for the receivers. Since MDBs implement the MessageListener interface they are asynchronous receivers that get messages pushed to them. They do poll the connection occasionally to make sure it is live but that is about it for the polling. This polling period is configurable. The docs are here.

I read about that, but it said that this wasn't required by the vendor. I didn't see anything in either the JMS API or in the WebLogic documents about where to set this property.
--Mark