cancel
Showing results for 
Search instead for 
Did you mean: 

ORA-12519 While running with jobExecutorActivate=true

vivverma
Champ in-the-making
Champ in-the-making
Hi All,
I have been trying to run Junit tests for a very simple scenario where a Wrapper Workflow with a call activity call a sub workflow with a Asynch task. Now the Test runs just fine when the JobExecutorActivate is not set to true (Offcourse the Asynch task is not executed) but it starts to fail as soon as i set the JobExecutorActivate = true. Even Test cases for Synch workflow starts to fail with the same below mentioned error.
Please find the error details below,  looks as if all the DB connection pool is being exhausted.
Is it a problem with activity or am i missing some configuration.
Request your valuable feedback.
Thanks

Spring config details are as below:-

    <bean id="processEngineConfiguration" class="org.activiti.spring.SpringProcessEngineConfiguration">
        <property name="databaseType" value="${db.type}" />
        <property name="dataSource" ref="dataSource"/>
        <property name="transactionManager" ref="txManager" />
        <property name="databaseSchemaUpdate" value="false" />
        <property name="historyLevel"  value="ACTIVITY"/>
        <property name="jobExecutorActivate" value="true"/>
        <property name="preParseListeners">
            <list>
                <bean class="com.abc.xyz.workflow.listeners.MYBpmnParseListener"/>
            </list>
        </property>
    </bean>
*************************************ERROR LOGS******************************************

### Error querying database. Cause: java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found The Connection descriptor used by the client was: localhost:1521:XE ### The error may exist in org/activiti/db/mapping/entity/ProcessDefinition.xml ### The error may involve org.activiti.engine.impl.persistence.entity.ProcessDefinitionEntity.selectLatestProcessDefinitionByKey ### The error occurred while executing a query ### SQL: select * from ACT_RE_PROCDEF where KEY_ = ? and VERSION_ = (select max(VERSION_) from ACT_RE_PROCDEF where KEY_ = ?) ### Cause: java.sql.SQLException: Listener refused the connection with the following error: ORA-12519, TNS:no appropriate service handler found The Connection descriptor used by the client was: localhost:1521:XE

org.apache.ibatis.exceptions.PersistenceException:
### Error querying database. Cause: java.sql.SQLException: Listener refused the connection with the following error:
ORA-12519, TNS:no appropriate service handler found
The Connection descriptor used by the client was:
localhost:1521:XE
1 REPLY 1

frederikherema1
Star Contributor
Star Contributor
Why not raise the limit of concurrent-connections allowed to your database or use better connection-pooling? The job-executor queries regularly to check for new jobs.