org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException

There are no available Samebug tips for this exception. Do you have an idea how to solve this issue? A short tip would help users who saw this issue last week.

  • It appears that selectors and concurrency are mutually exclusive in certain cases. For example using: <endpoint input-channel="drinks" handler-ref="hotHandlerChain1"> <selector ref="hotStuffSelector" /> <concurrency core="1" max="1" /> </endpoint> Assuming that hotHandlerChain1 is a valid handler and hotStuffSelector is a valid selector this gives the following exception (stacktrace reduced): >> Exception in thread "main" org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 33 in XML document from class path resource [cafeDemo.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'concurrency'. One of '{"http://www.springframework.org/schema/integration":selector, "http://www.springframework.org/schema/integration":handler}' is expected. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) ... Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'concurrency'. One of '{"http://www.springframework.org/schema/integration":selector, "http://www.springframework.org/schema/integration":handler}' is expected. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) << But when the rejection limit is reached the hint is to increase concurrency in the handler. This is contradictory, so it leads to believe it is unintentional behavior. Suggested fix is to support both concurrency and selector together.
    via by Iwein Fuld,
  • It appears that selectors and concurrency are mutually exclusive in certain cases. For example using: <endpoint input-channel="drinks" handler-ref="hotHandlerChain1"> <selector ref="hotStuffSelector" /> <concurrency core="1" max="1" /> </endpoint> Assuming that hotHandlerChain1 is a valid handler and hotStuffSelector is a valid selector this gives the following exception (stacktrace reduced): >> Exception in thread "main" org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 33 in XML document from class path resource [cafeDemo.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'concurrency'. One of '{"http://www.springframework.org/schema/integration":selector, "http://www.springframework.org/schema/integration":handler}' is expected. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390) ... Caused by: org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'concurrency'. One of '{"http://www.springframework.org/schema/integration":selector, "http://www.springframework.org/schema/integration":handler}' is expected. at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236) << But when the rejection limit is reached the hint is to increase concurrency in the handler. This is contradictory, so it leads to believe it is unintentional behavior. Suggested fix is to support both concurrency and selector together.
    via by Iwein Fuld,
  • how can i access css and images in spring mvc
    via Stack Overflow by bablu
    ,
  • Java Spring Batch - executing from a jar
    via Stack Overflow by Anand Kumar
    ,
    • org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 33 in XML document from class path resource [cafeDemo.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'concurrency'. One of '{"http://www.springframework.org/schema/integration":selector, "http://www.springframework.org/schema/integration":handler}' is expected. at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:390)

    Users with the same issue

    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    marcbouvierdav
    38 times, last one,
    Unknown visitor1 times, last one,
    Kawada
    11 times, last one,
    11 more bugmates