nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

load testing connection pooling

luisalves00

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?

Find more posts tagged with

Comments

luisalves00

6 parallel requests…seem to work…

ronald_van_kuij

Activity 0.9 is not supported anymore

luisalves00

ronald.van.kuijk,

I'm using activiti-5.6 what is Activity 0.9?

luisalves00

Updates…

using code like this:

&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .setJdbcUrl("jdbc:mysql://localhost:3306/activiti?autoReconnect=true") <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .setJdbcDriver("com.mysql.jdbc.Driver") <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .setJdbcUsername("activiti") <br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; .setJdbcPassword("activiti")<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; //.setDataSource(bds) <- NOT USING THIS<br>

When using an external DS I need to add something like c3p0?

jbarrez

No, in this case Ibatis will be able to do the connection pooling. Check the userguide for the details on how you can configure these settings.
When you provide a datasource, you will need to do it yourself (eg with c3p0).

luisalves00

And how can I get ibatis to support autoCommit?

I'm getting org.apache.ibatis.transaction.TransactionException: Error configuring AutoCommit. Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: false. Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

jbarrez

why do you need autocommit? I wouldn't use it .. ever.

luisalves00

I do not know if I need it…but I'm getting that exception…and I don't know why.

I'm using Activiti 5.6.

ronald_van_kuij

look in jira for the dbid generator issue. That is probably where you run into.

luisalves00

is this fixed on 5.7?

ronald_van_kuij

I think it is in present in 5.7 but not fully tested and therefor not enabled by default and not documented

luisalves00

how to disable it?

I'm allways getting this exception:

29-09-2011 06:30:16 CommandContext [ERROR] Error while closing command context<br>org.apache.ibatis.transaction.TransactionException: Error configuring AutoCommit.&nbsp; Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: false.&nbsp; Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 86.321.988 milliseconds ago.&nbsp; The last packet sent successfully to the server was 86.321.988 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.<br> at org.apache.ibatis.transaction.jdbc.JdbcTransaction.setDesiredAutoCommit(JdbcTransaction.java:47)<br> at org.apache.ibatis.transaction.jdbc.JdbcTransaction.<init>(JdbcTransaction.java:15)<br> at org.apache.ibatis.transaction.jdbc.JdbcTransactionFactory.newTransaction(JdbcTransactionFactory.java:15)<br> at org.apache.ibatis.session.defaults.DefaultSqlSessionFactory.openSessionFromDataSource(DefaultSqlSessionFactory.java:77)<br> at org.apache.ibatis.session.defaults.DefaultSqlSessionFactory.openSession(DefaultSqlSessionFactory.java:32)<br> at org.activiti.engine.impl.db.DbSqlSession.<init>(DbSqlSession.java:84)<br> at org.activiti.engine.impl.db.DbSqlSessionFactory.openSession(DbSqlSessionFactory.java:77)<br> at org.activiti.engine.impl.interceptor.CommandContext.getSession(CommandContext.java:177)<br> at org.activiti.engine.impl.cfg.standalone.StandaloneMybatisTransactionContext.getDbSqlSession(StandaloneMybatisTransactionContext.java:77)<br> at org.activiti.engine.impl.cfg.standalone.StandaloneMybatisTransactionContext.commit(StandaloneMybatisTransactionContext.java:58)<br> at org.activiti.engine.impl.interceptor.CommandContext.close(CommandContext.java:112)<br> at org.activiti.engine.impl.interceptor.CommandContextInterceptor.execute(CommandContextInterceptor.java:49)<br> at org.activiti.engine.impl.interceptor.LogInterceptor.execute(LogInterceptor.java:33)<br> at org.activiti.engine.impl.IdentityServiceImpl.createUserQuery(IdentityServiceImpl.java:70)

Already got autoReconnect=true ….wait_timeout is set to mysql default (think its 8 hours)…

lichtin

http://jira.codehaus.org/browse/ACT-789?focusedCommentId=274693&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-274693

In your activiti.cfg.xml

<bean id="processEngineConfiguration" … >
…
<property name="idGenerator">
<bean class="org.activiti.engine.impl.persistence.StrongUuidGenerator" />
</property>

</bean>

luisalves00

lichtin,

I'm configuring my processEngine on java code…not in the xml.

Questions:

1. how to set this on the code?
2. is valid for 5.6 or only 5.7?

best regards,
la00

lichtin

1. how to set this on the code?
2. is valid for 5.6 or only 5.7?

1. Use the setter

setIdGenerator(IdGenerator idGenerator)

2. from 5.7 on

luisalves00

I'm looking ate http://activiti.org/javadocs/index.html and ProcessEngineConfiguration doesn't have that method…

I've updated to 5.7 and can't find it…

luisalves00

tried:

<br>ProcessEngineConfigurationImpl pec =&nbsp; (ProcessEngineConfigurationImpl) ProcessEngineConfiguration &hellip;..<br><br>pec.setIdGenerator(new org.activiti.engine.impl.persistence.StrongUuidGenerator());<br><br>ProcessEngine processEngine = (ProcessEngine) pec.buildProcessEngine();<br><br>

(new org.activiti.engine.impl.persistence.StrongUuidGenerator()); this throws an exception…
I think I can't do 'new' because StrongUuidGenerator must depend on some dependency injection…

Do you know any factory method?

marcus1

Which exception is thrown? Probably a ClassNotFoundException. StrongUuidGenerator needs the library java-uuid-generator-3.1.2.jar.

luisalves00

tks Marcus and lichtin

library java-uuid-generator-3.1.2.jar did the trick…

luisalves00

now I can't start any workflow….

java.lang.NumberFormatException: For input string: "d5d5dc0b-f005-11e0-8a7c-542ac8f06f0b"
        at java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
        at java.lang.Long.parseLong(Long.java:410)
        at java.lang.Long.valueOf(Long.java:525)

I'm doing: pa.setIdWorkflow(BigInteger.valueOf(Long.valueOf(execution.getProcessInstanceId())));
but now this is not a number…so I need to do some changes on my DB

this will fix this exception, right?:

29-09-2011 06:30:16 CommandContext [ERROR] Error while closing command context<br>org.apache.ibatis.transaction.TransactionException: Error configuring AutoCommit.&nbsp; Your driver may not support getAutoCommit() or setAutoCommit(). Requested setting: false.&nbsp; Cause: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: The last packet successfully received from the server was 86.321.988 milliseconds ago.&nbsp; The last packet sent successfully to the server was 86.321.988 milliseconds ago. is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.<br>&nbsp;&nbsp; at org.apache.ibatis.transaction.jdbc.JdbcTransaction.setDesiredAutoCommit(JdbcTransaction.java:47)

marcus1

Actually that exception does not look related to me. It seems like you have some old connections in your pool (i.e. they haven't been used for a long time). The exception message explains it pretty well:

"You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem."

In tomcat, testing connection validity is done as follows:

<br>&nbsp;&nbsp;&nbsp; <Resource name="&hellip;"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; auth="Container"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; type="javax.sql.DataSource"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; username="&hellip;"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; password="&hellip;"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; driverClassName="com.mysql.jdbc.Driver"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; url="jdbc:mysql://&hellip;"<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; testOnBorrow="true"&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <!&ndash; add this &ndash;><br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; validationQuery="SELECT 1+1"/>&nbsp; <!&ndash; and this &ndash;><br>

luisalves00

I'm setting the "resource" like this:

.setJdbcUrl(ApplicationConfig.getConfigParam("activiti.url"))
.setJdbcDriver(ApplicationConfig.getConfigParam("activiti.driverClassName"))
.setJdbcUsername(ApplicationConfig.getEncryptedConfigParamDecrypted("activiti.username"))
.setJdbcPassword(ApplicationConfig.getEncryptedConfigParamDecrypted("activiti.password"))

how to get that done in here?

pec.setJdbcPingQuery("SELECT 1+1");
pec.setJdbcPingEnabled(true);

will work?

marcus1

That's worth a try. Only one way to find out whether it will work