This discussion is archived
1 Reply Latest reply: Nov 8, 2012 5:35 AM by Charles Lamb RSS

Connection Pooling

741394 Newbie
Currently Being Moderated
Hi,

Is there a need for a connection pool when managing the connections with the nosql database?

At the moment we are creating a store insisde the constructor of a LocalSessionBean. That means we have one store per bean and the beans are pooled.
    @Stateless
    public CustomerDAO {

         private transient KVStore store;

  
         @EJB // EJB Singleton
         private CustinerStoreFactory tokenStoreFactory;


         @PostConstruct
         public void initialize() {
               store = getStoreFactory().buildStore();
        ......
         }

    }
      
Is our approach ok or shoueld we be using some form of connection pooling like a traditional RDBMS?

Should we use JCA?

Tim
  • 1. Re: Connection Pooling
    Charles Lamb Pro
    Currently Being Moderated
    user6641759 wrote:
    Hi,

    Is there a need for a connection pool when managing the connections with the nosql database?

    At the moment we are creating a store insisde the constructor of a LocalSessionBean. That means we have one store per bean and the beans are pooled.
    @Stateless
    public CustomerDAO {
    
    private transient KVStore store;
    
    
    @EJB // EJB Singleton
    private CustinerStoreFactory tokenStoreFactory;
    
    
    @PostConstruct
    public void initialize() {
    store = getStoreFactory().buildStore();
    ......
    }
    
    }
    Is our approach ok or shoueld we be using some form of connection pooling like a traditional RDBMS?
    This should be ok. Can you tell me approximately how many connections/beans you will have?

    Charles

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points