Project

General

Profile

Actions
Copy link

bug #6245

open

Servlet context reports error after automatic update has run

Added by Andreas Kohlbecker over 6 years ago. Updated over 1 year ago.

Status:
Resolved
Priority:
New
Assignee:
Andreas Müller
Category:
cdmserver
Target version:
Unassigned CDM tickets
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

This phenomenon occurs always on the production server. On the first run of a new version of the cdmserver the databases are updated automatically but even if the update was successful the ServletContext reports errors and is stopped:

2016-12-06 12:01:23,489 INFO [eu.etaxonomy.cdm.common.monitor.DefaultProgressMonitor] -  Next Task: Update hibernate sequences
2016-12-06 12:01:23,493 INFO [eu.etaxonomy.cdm.common.monitor.DefaultProgressMonitor] - 100.0% done (Completed Task: Update hibernate sequences)
2016-12-06 12:01:23,493 INFO [eu.etaxonomy.cdm.common.monitor.DefaultProgressMonitor] -  Next Task: Update finished successfully
2016-12-06 12:01:23,493 INFO [eu.etaxonomy.cdm.common.monitor.DefaultProgressMonitor] - Update to schema version 4.1.0.0.201607300000 and to term version 4.1.0.0.201607300000...Done
2016-12-06 12:01:23,493 INFO [eu.etaxonomy.cdm.database.update.CdmUpdater] - Update finished successfully
2016-12-06 12:01:24,395 INFO [eu.etaxonomy.cdm.server.instance.CdmInstance] - lifeCycleStarted
2016-12-06 12:01:24,396 WARN [eu.etaxonomy.cdm.server.instance.CdmInstance] - Stopping context 'rl_moose' due to errors reported in ServletContext
2016-12-06 12:01:24,396 INFO [eu.etaxonomy.cdm.server.instance.CdmInstance] - lifeCycleStopping
2016-12-06 12:01:24,569 WARN [eu.etaxonomy.cdm.persistence.hibernate.CdmListenerIntegrator] - Disintegrate ListenerIntegrator not yet implemented
2016-12-06 12:01:24,572 INFO [eu.etaxonomy.cdm.server.instance.CdmInstance] - lifeCycleStopped
2016-12-06 12:01:24,572 INFO [eu.etaxonomy.cdm.server.instance.CdmInstance] - lifeCycleStarting
Actions
Copy link
 #1

Updated by Andreas Müller over 1 year ago

  • Subject changed from servlet context reports error after automatic update has run to Servlet context reports error after automatic update has run
  • Status changed from New to Resolved

Does this error still exist?

Actions
Copy link
 #2

Updated by Andreas Kohlbecker over 1 year ago

please check the log files on the production server:

egrep 'errors\s*ServletContext' /var/log/cdmserver/cdmserver.log
Actions
Copy link
 #3

Updated by Andreas Kohlbecker over 1 year ago

  • Assignee changed from Andreas Kohlbecker to Andreas Müller
Actions
Copy link

Also available in: Atom PDF