Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse Process Manager (Stardust) » Sporadic NPEs thrown while parsing Camel Spring configuration during server startup
Sporadic NPEs thrown while parsing Camel Spring configuration during server startup [message #938994] Wed, 10 October 2012 06:31 Go to next message
Srinivasan Iyer is currently offline Srinivasan Iyer
Messages: 35
Registered: October 2011
Member
In a Stardust 7.0.1 RAD environment with Tomcat 6.0 on server startup a NPE is seen sopradically. The output looks as follows:
10:17:51 ERROR [main      ] ContextLoader             - Context initialization failed
org.springframework.beans.factory.BeanDefinitionStoreException: Unexpected exception parsing XML document from ServletContext resource [/WEB-INF/config/ipp/spring/camel-context.xml]; nested exception is java.lang.NullPointerException
                at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:412)
                at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:334)
                at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:302)

Quite often (~70% of the cases), the exception disappears after cleaning up both the project and the server. Sometimes, however, even this doesn't help so that the user is required to close/reopen the project and delete/recreate the server.
Re: Sporadic NPEs thrown while parsing Camel Spring configuration during server startup [message #938997 is a reply to message #938994] Wed, 10 October 2012 06:35 Go to previous message
Srinivasan Iyer is currently offline Srinivasan Iyer
Messages: 35
Registered: October 2011
Member
This issue is apparently caused by a JAXB bug that has already been identified and fixed. More details are available at:
http://camel.465427.n5.nabble.com/null-pointer-exception-td5537826.html

Replacing the jaxb-impl.jar jar in the Stardust web application with a more recent one (2.2.5 or later as per JAXB ticket information) should resolve the issue.
Previous Topic:Accessing Configuration Variables in a Java class
Next Topic:Passing partition ID info via WS-A addressing
Goto Forum:
  


Current Time: Wed Jul 30 15:21:56 EDT 2014

Powered by FUDForum. Page generated in 0.02277 seconds