Problem: When I installed process bar file with bonita xp rest, it took long time and http 500 error code in tomcat log file.But sometimes it works to upload.
Submitted by zhangzhongmac on Wed, 01/08/2014 - 02:47
I does'not depend on the bar being deployed, sometimes it works to upload after I try several times.There is no stack trace, and my logger config as below:
# Definition of the Bonita logs handler
5bonita.org.apache.juli.FileHandler.level = FINE
5bonita.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
5bonita.org.apache.juli.FileHandler.prefix = bonita.
# By default for development it's a good idea to set the default level for all Bonita component to INFO.
# In production WARNING is a good choice.
org.ow2.bonita.level = INFO
org.bonitasoft.level = INFO
# Allow to follow process execution (forms server side)
org.bonitasoft.forms.server.api.impl.FormWorkflowAPIImpl.level = INFO
# The EventDispatcherThread class produce frequent log with INFO level. It's better to set the level to WARNING.
org.ow2.bonita.runtime.event.EventDispatcherThread.level = WARNING
org.ow2.bonita.facade.rest.provider.GenericObjectProvider.level = SEVERE
org.ow2.bonita.services.impl.LoggerRecorder.level = FINE
# Bonita 4 legacy, will not be used.
org.ow2.bonita.example.level = WARNING
# Hibernate is used by Bonita and very verbose in the log. Should stay with WARNING level except when debugging database access issues
org.hibernate.level = WARNING
Comments
Does this problem happen with the same process bar or does it depend on the bar being deployed? Do you have any stack trace in tomcat logs?
I does'not depend on the bar being deployed, sometimes it works to upload after I try several times.There is no stack trace, and my logger config as below:
# Definition of the Bonita logs handler
5bonita.org.apache.juli.FileHandler.level = FINE
5bonita.org.apache.juli.FileHandler.directory = ${catalina.base}/logs
5bonita.org.apache.juli.FileHandler.prefix = bonita.
# By default for development it's a good idea to set the default level for all Bonita component to INFO.
# In production WARNING is a good choice.
org.ow2.bonita.level = INFO
org.bonitasoft.level = INFO
# Allow to follow process execution (engine side). Verbose.
org.ow2.bonita.runtime.model.Execution.level = FINEST
org.ow2.bonita.runtime.model.ExecuteNode.level = FINEST
org.ow2.bonita.definition.activity.AbstractActivity.level = FINEST
org.ow2.bonita.runtime.TaskManager.level = FINEST
org.ow2.bonita.definition.activity.ConnectorExecutor.level = FINEST
# Allow to follow process execution (forms server side)
org.bonitasoft.forms.server.api.impl.FormWorkflowAPIImpl.level = INFO
# The EventDispatcherThread class produce frequent log with INFO level. It's better to set the level to WARNING.
org.ow2.bonita.runtime.event.EventDispatcherThread.level = WARNING
org.ow2.bonita.facade.rest.provider.GenericObjectProvider.level = SEVERE
org.ow2.bonita.services.impl.LoggerRecorder.level = FINE
# Bonita 4 legacy, will not be used.
org.ow2.bonita.example.level = WARNING
# Hibernate is used by Bonita and very verbose in the log. Should stay with WARNING level except when debugging database access issues
org.hibernate.level = WARNING
#
net.sf.ehcache.level = WARNING
Hi,
it seems a performance issue. Does your bar have a lot of depencencies? Which is it size (MB)?
Are Bonita Engine and Bonita User XP running in same server or in two separated servers? Maybe the problem occurs when the network is overload.