Project

General

Profile

Actions

bug #5774

closed

cdmserver misses to detect some errors in failed instances

Added by Andreas Kohlbecker almost 7 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Priority14
Category:
cdmserver
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
major
Found in Version:

Description

The following error was missed, the cdmserver kept on reporting that the instance is 'started' even if it completely had failed:

2016-05-06 13:27:00,075 INFO [eu.etaxonomy.cdm.database.PersistentTermInitializer] - PersistentTermInitializer initialize start ...
2016-05-06 13:27:00,075 INFO [eu.etaxonomy.cdm.database.PersistentTermInitializer] - PersistentTermInitializer.omit == false, initializing 45 term classes
2016-05-06 13:27:00,137 INFO [eu.etaxonomy.cdm.database.PersistentTermInitializer] - Start new ... 
2016-05-06 13:27:00,233 INFO [eu.etaxonomy.cdm.database.PersistentTermInitializer] - Create missing terms ... 
2016-05-06 13:27:05,997 WARN [org.springframework.web.context.support.XmlWebApplicationContext] - Exception encountered during context initialization - cancelling refresh attempt: org.sprin
gframework.beans.factory.BeanCreationException: Error creating bean with name 'persistentTermInitializer': Invocation of init method failed; nested exception is java.lang.NoSuchMethodError:
 eu.etaxonomy.cdm.model.common.IdentifiableEntity.hasEmptyTitleCache()Z
2016-05-06 13:27:06,008 WARN [eu.etaxonomy.cdm.persistence.hibernate.CdmListenerIntegrator] - Disintegrate ListenerIntegrator not yet implemented
2016-05-06 13:27:06,014 ERROR [org.springframework.web.context.ContextLoader] - Context initialization failed
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'persistentTermInitializer': Invocation of init method failed; nested exception is java.lang.NoSuchMet
hodError: eu.etaxonomy.cdm.model.common.IdentifiableEntity.hasEmptyTitleCache()Z
        at org.springframework.beans.factory.annotation.InitDestroyAnnotationBeanPostProcessor.postProcessBeforeInitialization(InitDestroyAnnotationBeanPostProcessor.java:136)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyBeanPostProcessorsBeforeInitialization(AbstractAutowireCapableBeanFactory.java:408)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1570)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:545)
        at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:482)
        at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:306)
        at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
        at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:302)
        at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:772)
        at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:839)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:538)
        at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:446)
        at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:328)
        at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:107)
        at org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:800)
        at org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:444)
        at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:791)
        at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:294)
        at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1349)

has duplicate #5773


Related issues

Related to EDIT - feature request #7725: Implement server availability checkNewAndreas Kohlbecker

Actions
Has duplicate EDIT - bug #5773: Exceptions during CDM Server startup are not caught correcltyDuplicateAndreas Kohlbecker

Actions
Actions #1

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.1 to Release 4.2
Actions #2

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.2 to Release 4.3
Actions #3

Updated by Andreas Müller over 6 years ago

  • Has duplicate bug #5773: Exceptions during CDM Server startup are not caught correclty added
Actions #4

Updated by Andreas Müller over 6 years ago

  • Target version changed from Release 4.3 to Release 4.4
Actions #5

Updated by Andreas Müller about 6 years ago

  • Target version changed from Release 4.4 to Release 4.5
Actions #6

Updated by Andreas Müller about 6 years ago

  • Target version changed from Release 4.5 to Release 4.6
Actions #7

Updated by Andreas Müller almost 6 years ago

  • Target version changed from Release 4.6 to Release 4.7
Actions #8

Updated by Andreas Müller almost 6 years ago

  • Target version changed from Release 4.7 to Release 4.8
Actions #9

Updated by Andreas Müller over 5 years ago

  • Target version changed from Release 4.8 to Release 4.9
Actions #10

Updated by Andreas Müller over 5 years ago

  • Target version changed from Release 4.9 to Release 4.10
Actions #11

Updated by Andreas Müller over 5 years ago

  • Target version changed from Release 4.10 to Release 4.11
Actions #12

Updated by Andreas Müller over 5 years ago

  • Target version changed from Release 4.11 to Release 4.12
Actions #13

Updated by Andreas Müller about 5 years ago

  • Target version changed from Release 4.12 to Release 4.13
Actions #14

Updated by Andreas Müller about 5 years ago

  • Target version changed from Release 4.13 to Release 4.14
Actions #15

Updated by Andreas Müller almost 5 years ago

  • Target version changed from Release 4.14 to Release 5.0
Actions #16

Updated by Andreas Kohlbecker almost 5 years ago

  • Description updated (diff)
  • Private changed from Yes to No
Actions #17

Updated by Andreas Kohlbecker over 4 years ago

  • Target version changed from Release 5.0 to Release 5.1
Actions #18

Updated by Andreas Müller over 4 years ago

  • Target version changed from Release 5.1 to Release 5.2
Actions #19

Updated by Andreas Kohlbecker over 4 years ago

  • Target version changed from Release 5.2 to Release 5.3
Actions #20

Updated by Andreas Kohlbecker over 4 years ago

  • Target version changed from Release 5.3 to Release 5.4
Actions #21

Updated by Andreas Müller over 4 years ago

Actions #22

Updated by Andreas Kohlbecker over 4 years ago

  • Target version changed from Release 5.4 to Release 5.5
Actions #23

Updated by Andreas Kohlbecker about 4 years ago

  • Target version changed from Release 5.5 to Release 5.6
Actions #24

Updated by Andreas Kohlbecker almost 4 years ago

  • Priority changed from Priority14 to Priority12
  • Target version changed from Release 5.6 to Reviewed Next Major Release
Actions #25

Updated by Andreas Müller almost 4 years ago

hmm, I consider this a very anoying and dagerous bug as one may not realize that some instances do work (we do not have any other tests for checking). Do you really think we should lower priority to 12?

Actions #26

Updated by Andreas Kohlbecker almost 4 years ago

  • Priority changed from Priority12 to Priority14

I guess you are right. I was lowering the priority that much because the issue has not been reported for 2 years, but there is a duplicate issue and you are also right by saying that this bug can be very confusing.

Actions #27

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from New to In Progress
  • Target version changed from Reviewed Next Major Release to Release 5.8
Actions #28

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 0 to 50
Actions #29

Updated by Andreas Kohlbecker over 3 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100

It occurred again in the demo1 server.

Problem fixed.

Since it is quite time consuming to do do all the testing and breaking things required for a full review I will just close this issue. Future will show in case it is not really 100% fixed.

Actions

Also available in: Atom PDF