Activiti

[DbSqlSession] Log level set to SEVERE when performing dbSchema drop for ProcessEngineConfigurationImpl.DB_SCHEMA_UPDATE_DROP_CREATE update strategy

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Won't Fix
  • Affects Version/s: 5.9, 5.10
  • Fix Version/s: None
  • Component/s: Engine
  • Labels:
    None
  • Number of attachments :
    1

Description

If ProcessEngineConfigurationImpl.DB_SCHEMA_UPDATE_DROP_CREATE database update strategy is set first db schema drop is performed in DbSqlSession.performSchemaOperationsProcessEngineBuild():

try

{ dbSchemaDrop(); }

catch (RuntimeException e)

{ // ignore }

So exceptions are ignored but because db schema drop is performed by generic method DbSqlSession.executeSchemaResource(String operation, String component, String resourceName, InputStream inputStream) log level is set to SEVERE no matter if it's really important or not.

It is causing confusing messages in logs, in this case log level should be lower.

Activity

Hide
Permalink
Tom Baeyens added a comment -

I agree that a full stack trace is may too much info.

On the other hand it's vital that you clearly see problems in case you expect it to work. I don't think the stacktraces are a big problem in those situations that you describe. In this case I don't see how we can easily improve ensuring that the right emphasis is given to error situations that the user does not expect.

Show
Tom Baeyens added a comment - I agree that a full stack trace is may too much info. On the other hand it's vital that you clearly see problems in case you expect it to work. I don't think the stacktraces are a big problem in those situations that you describe. In this case I don't see how we can easily improve ensuring that the right emphasis is given to error situations that the user does not expect.

People

  • Assignee:
    Unassigned
    Reporter:
    Pawel Gadecki
Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: