This content has been marked as final.
Show 4 replies
-
1. Re: Producers/Consumers and managed jms connections
adrian.brock Nov 28, 2005 2:07 PM (in response to timfox)"timfox" wrote:
Although producer/consumer creation is lightweight compared to connection creation it still requires a jms server hit in jboss-messaging (I'm not sure whether it's handled locally in JBossMQ)
Yes it is handled locally/lazily in JBossMQ for producers.
It validates whether the destination really exists on the send.
For consumers you obviously need to go the server anyway to create the "subscription".
Which must be physically removed on logical close of the jms connection. Even if the
session/connection isn't physically closed. -
2. Re: Producers/Consumers and managed jms connections
timfox Nov 29, 2005 8:09 AM (in response to timfox)So we need to make sure we're caching producers for the session or performance is going to suck for jboss messaging.
BTW What is the use case for creating a consumer from an EJB using JCA? -
3. Re: Producers/Consumers and managed jms connections
adrian.brock Nov 29, 2005 2:07 PM (in response to timfox)"timfox" wrote:
So we need to make sure we're caching producers for the session or performance is going to suck for jboss messaging.
No you should look at optimizing your processing rather than expecting
some other layer to fix the problem.BTW What is the use case for creating a consumer from an EJB using JCA?
You can only use receive() methods according to the j2ee spec
see the example ejb on the WIKI provided by a user. -
4. Re: Producers/Consumers and managed jms connections
adrian.brock Nov 29, 2005 2:09 PM (in response to timfox)NOTE also. A JCA resource adapter can be used outside a J2EE appserver.
You supply your own connection manager to give it your own semantics
or hope the resource adapter has an internal implementation.