Issue

• While performing load testing , the following exception can be seen in server log.

[DEBUG] [org.drools.persistence.jta.JtaTransactionManager.findTransactionManager(106)] No JTA TransactionManager found at fallback JNDI location [java:appserver/TransactionManager]
javax.naming.NameNotFoundException: While trying to look up /appserver/TransactionManager in /appserver/ejb/<jar>.jar/#JBPMUtil.; remaining name '/appserver/TransactionManager'

• The code behind JBPMUtil is just trying to create ksession and fire rules as shown below.

...
@Singleton

@Resource
  private UserTransaction userTrans;

public StatefulKnowledgeSession createKnowledgeSession(EntityManager eManager, UserTransaction userTrans, String processName) throws Exception {
        Environment environment = KnowledgeBaseFactory.newEnvironment();
        environment.set(EnvironmentName.ENTITY_MANAGER_FACTORY, eManager.getEntityManagerFactory());
        environment.set(EnvironmentName.TRANSACTION, userTrans);
        StatefulKnowledgeSession ksession = JPAKnowledgeService.newStatefulKnowledgeSession(readKnowledgeBase(processName), null, environment);
        final AgendaEventListener agendaEventListener = new DefaultAgendaEventListener() {
            @Override
            public void afterRuleFlowGroupActivated(RuleFlowGroupActivatedEvent event, WorkingMemory workingMemory) {
                workingMemory.fireAllRules();
            }
        } ;

        ((StatefulKnowledgeSessionImpl)  ((KnowledgeCommandContext) ((CommandBasedStatefulKnowledgeSession) ksession)
            .getCommandService().getContext()).getStatefulKnowledgesession() )
            .session.addEventListener(agendaEventListener) ;
        ...          
        return ksession;
    }
...

• Is it safe to ignore the DEBUG message?