[jboss-jira] [JBoss JIRA] Commented: (JBESB-391) sometimes the parser is not found when doing a parameter reload.

Kurt Stam (JIRA) jira-events at jboss.com
Thu Jan 25 08:29:57 EST 2007


    [ http://jira.jboss.com/jira/browse/JBESB-391?page=comments#action_12351624 ] 
            
Kurt Stam commented on JBESB-391:
---------------------------------

Well it is intermittend if reading the configuration fails, however as I stated in later this is more of a general issue with reloading the sar and it can fail anywhere, so I don't think this should be marked as optional. Maybe we should rename this issue.

Kev says:

"I am in the middle of rewriting how the gateways/listeners are
initialised/tracked etc.  This will have an effect on any redeployment
of the services."

> sometimes the parser is not found when doing a parameter reload.
> ----------------------------------------------------------------
>
>                 Key: JBESB-391
>                 URL: http://jira.jboss.com/jira/browse/JBESB-391
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Rosetta
>    Affects Versions: 4.0
>         Environment: any
>            Reporter: Kurt Stam
>         Assigned To: Kevin Conner
>            Priority: Optional
>             Fix For: 4.0
>
>
> When running the deployToSar task of the hello world quickstart on a running jboss, the timestamp on the jbossesb.xml changes and the parameters are reloaded. When this happens sometimes see the following stacktrace:
> 15:18:25,687 INFO  [Server] JBoss (MX MicroKernel) [4.0.5.GA (build: CVSTag=Branch_4_0 date=200610162339)] Started in 40s:875ms
> 15:18:47,296 ERROR [STDERR] Exception in thread "Thread-6" 
> 15:18:47,296 ERROR [STDERR] org.apache.xerces.parsers.ObjectFactory$ConfigurationError: Provider org.apache.xerces.parsers.XIncludeAwareParserConfiguration could not be instantiated: java.lang.NullPointerException
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.parsers.ObjectFactory.newInstance(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.parsers.ObjectFactory.createObject(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.parsers.DOMParser.<init>(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.jaxp.DocumentBuilderImpl.<init>(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown Source)
> 15:18:47,296 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.config.XmlValidatorImpl.validate(XmlValidatorImpl.java:160)
> 15:18:47,296 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.config.ConfigurationController.processConfiguration(ConfigurationController.java:176)
> 15:18:47,296 ERROR [STDERR] 	at org.jboss.soa.esb.listeners.config.ConfigurationController.run(ConfigurationController.java:113)
> 15:18:47,296 ERROR [STDERR] 	at java.lang.Thread.run(Thread.java:595)
> 15:19:12,515 ERROR [STDERR] Exception in thread "Thread-15" 
> which is thrown from the line 160 in the XmlValidatorImpl:
> parser = builderFactory.newDocumentBuilder();
> The issue seems to fix it self, as it seems to be successful 5 seconds later.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list