[jboss-dev-forums] [Design of JCA on JBoss] - Re: JCA antipattern? Or not?

[adrian@jboss.org]

"timfox" wrote : 
  | For straight JMS the above would again be clearly an antipattern.
  | 
  | But what about JCA? It's my understanding that JCA does not cache jms consumers so every call to createConsumer() in the above is going to result in a new consumer being created on the jms provider. I.e. a heavyweight operation.
  | 

There would be nothing to stop the JMS rar caching the consumers
(like JDBC adapters can cache prepared statements).

But I doubt it would work in practice.

e.g. if the consumer is configured for read ahead
there would be messages sitting in limbo until somebody reuses the JCA connection
and "recreates" the same consumer.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4021151#4021151

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4021151