Skip to main content

How can I read the log files of my BOC Management Office product?

  • Updated

Where can I find my log files?

Log files can only be read out by yourself, if you run your BOC Management Office product on premise. For the exact paths, please read: How can I create a log package manually?

Breakdown of log files

The log files of your BOC Management Office product can basically be divided into two components:

  • aserver_files

Which represents actions performed on database level, stored in the logs folder of the BOC product installation path.

  • webserver_files

Which represents actions performed directly in the webclient, stored in the logs from the tomcat installation path.

Entries in the aserver_files logs are usually structured in the following way:

  • Date and Time - When an action has been performed
  • Thread ID(aserver) - The ID of the thread handling the request
  • Session ID - The ID which gets assigned to users working in the webclient
  • Request id - Unique ID for the specific request
  • Log-Level - Represents what the log-message is about (INFO/WARNING/ERROR)
  • Log-Message - Contains the actual information what the log-entry is about.

Entries in webserver_files are usually structured the following way:

  • Date and Time - When an action has been performed
  • Log-Level - Represents what the log-message is about (INFO/WARNING/ERROR)
  • Tomcat Thread ID (webserver) - The ID of the thread handling the request
  • Session ID - The ID which gets assigned to users working in the webclient
  • Request ID - Unique ID for the specific request. If those appear to be in the wrong order or some are missing, this usually indicates a connectivity issue in your network infrastructure.
  • Log Message - Contains the actual information what the log-Entry is about.

Since the log-messages contain most of the useful information, we will explain common entries in the following section:

Breakdown of Log-Messages

WEBMETHOD START:/WEBMETHOD END:

Most performed actions start and end with these, often including a [duration: x ms] information in the end, indicating how long that action took.

 

MULTIPLE CLIENT HANDLES for this session. This most likely implies multiple tab usage!

Indicates, the user is using several tabs in the browser within the same user session, which is usually not recommended and can lead to several problems and errors.

 

The available host-physical-memory is below the warning threshold of

Indicates your environment is almost running out of memory.

 

Exception while initializing web application (java.lang.OutOfMemoryError)
OutOfMemoryError: Java heap space

Indicates, your Tomcat-Installation does not have enough memory allocated.

 

[WARN] Performance issue: ....

Indicates there is a potential database performance issue.

 

Your request could not be processed because of problems with the connection between your
client and the web server.

Usually indicates a connectivity issue between your webclient and your webserver (tomcat)

 

[ODBC Driver 17 for SQL Server][SQL Server]Login failed for user 'ADOxx/ADOXX_BOOT

Indicates, the password for the ADOxx/ADOXX_BOOT users in the ODBC-Connection does not match with the one stored in the database.

 

[FATAL] [boc.adoxx.fulltext.JNIIndexWriter] Could not open index (C:\windows\TEMP\FTS..
[WARN] [Index Updater] Error during index update, returned code UnexpectedError

Indicates the FTS Index got corrupted and needs to be rebuilt and/or needs to be moved to a different location.

For more information on rebuilding the FTS Index, please visit How can i rebuild my FTS Index?

 

An error occurred while sending mail
javax.mail.AuthenticationFailedException: 535 5.7.3 Authentication unsuccessful

The error code 535 5.7.3 suggests a configuration issue on the associated MS Exchange.

 

 

 

 

 

Related articles