AnsweredAssumed Answered

load testing connection pooling

Question asked by luisalves00 on Sep 9, 2011
Latest reply on Oct 6, 2011 by marcus1
Hello,

My load test seem to fail because of some kind of connection starvation (still not sure).

O configure the engine programmaticaly:


org.apache.commons.dbcp.BasicDataSource bds = new org.apache.commons.dbcp.BasicDataSource();
            bds.setDefaultAutoCommit(false); //FIXME: make me configurable
            bds.setUsername(ApplicationConfig.getEncryptedConfigParamDecrypted("activiti.username"));
            bds.setPassword(ApplicationConfig.getEncryptedConfigParamDecrypted("activiti.password"));
            bds.setDriverClassName(ApplicationConfig.getConfigParam("activiti.driverClassName"));
            bds.setUrl(ApplicationConfig.getConfigParam("activiti.url"));



            ProcessEngine processEngine = ProcessEngineConfiguration
                    .createStandaloneProcessEngineConfiguration()
                    .setDataSource(bds)
                    .setJdbcMaxActiveConnections(100)            
                    .setJdbcMaxIdleConnections(25)
                    .setDatabaseType(ApplicationConfig.getConfigParam("activiti.databaseType"))
                    .setDatabaseSchemaUpdate(ApplicationConfig.getConfigParam("activiti.databaseSchemaUpdate"))
                    .setHistory(ApplicationConfig.getConfigParam("activiti.history"))
                    .setProcessEngineName(ACTIVITI_ENGINE_NAME)
                    .setJobExecutorActivate(false) //FIXME: make me configurable
                    .buildProcessEngine();

            ProcessEngines.registerProcessEngine(processEngine);

only see 8 connections to the db, with 15 parallel request.

any idea?

Outcomes