Hi, I am bootstrapping camunda using osgi (inside eclipse) and there is a ton of logging messages showing up in the eclipse console. I would like to disable or reduce this. I am using sl4j for my application but the corresponding log settings in the log4j.xml seem to have no effect. What must I do?
Hi here are some examples of what I want to get rid of:
…
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] INFO parser - ENGINE-01003 Process with id ‘ART_OrderSamplePart’ has no attribute isExecutable. Better set the attribute explicitly, especially to be compatible with future engine versions which might change the default behavior.
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG parser - ENGINE-01001 Parsing element from type ‘process’ with id ‘ART_OrderSamplePart’
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG parser - ENGINE-01001 Parsing element from type ‘activity’ with id ‘request’
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG parser - ENGINE-01001 Parsing element from type ‘activity’ with id ‘handleRequest’
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG parser - ENGINE-01001 Parsing element from type ‘activity’ with id ‘theEnd1’
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG efinitionByKeyAndTenantId - ==> Preparing: select * from ACT_RE_PROCDEF where KEY_ = ? and TENANT_ID_ = ? and VERSION_ = ( select max(VERSION_) from ACT_RE_PROCDEF where KEY_ = ? and TENANT_ID_ = ?)
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG efinitionByKeyAndTenantId - ==> Parameters: checkGAPReminder(String), INA(String), checkGAPReminder(String), INA(String)
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG efinitionByKeyAndTenantId - <== Total: 1
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG selectJobsByConfiguration - ==> Preparing: select * from ACT_RU_JOB where HANDLER_TYPE_ = ? and TENANT_ID_ = ? and (HANDLER_CFG_ = ? or HANDLER_CFG_ = ? )
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG selectJobsByConfiguration - ==> Parameters: timer-start-event(String), INA(String), checkGAPReminder(String), checkGAPReminder$followUpJobCreated(String)
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG selectJobsByConfiguration - <== Total: 0
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG scriptionsByConfiguration - ==> Preparing: select * from ACT_RU_EVENT_SUBSCR where (EVENT_TYPE_ = ?) and (CONFIGURATION_ = ?)
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG scriptionsByConfiguration - ==> Parameters: message(String), checkGAPReminder:37:9512(String)
28.06.16,13:46:06 [16-1aa7-b670e8b6848c] DEBUG scriptionsByConfiguration - <== Total: 0
…
current versions of Camunda use SLF4J as logging framework. You can read more about that in the user guide. You have to provide a SLF4J backend and configure it, this depends on the backend you choose.