You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2007/03/04 17:50:26 UTC
DO NOT REPLY [Bug 41759] New: - Migration from 5.5.20 to 6.0.10: parser issue on application deployment
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759
Summary: Migration from 5.5.20 to 6.0.10: parser issue on
application deployment
Product: Tomcat 6
Version: 6.0.7
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: Catalina
AssignedTo: tomcat-dev@jakarta.apache.org
ReportedBy: egiraudy@gmail.com
I'm facing a small issue when migrating a production server from 5.5.20 to
6.0.10 (see the exception below).
One of the web app running on that server includes xercesImpl.jar and use it
through modifying the system property javax.xml.parsers.SAXParserFactory.
This was not a problem in 5.5.x, but with 6.0.10, it seems that tomcat loads
its instance of the parser after web initializations. It is then affected by
the web app that modified the system property.
I've been able to 'fix' that by copying the xercesImpl.jar into tomcat lib
directory.
Shall this be considered as a regression as in that case tomcat configuration
is somehow altered by a web app?
GRAVE: Erreur lors du d�ploiement du r�pertoire portal de l'application web
javax.xml.parsers.FactoryConfigurationError: Provider
org.apache.xerces.jaxp.SAXParserFactoryImpl not found
at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:134)
at org.apache.tomcat.util.digester.Digester.getFactory(Digester.java:487)
at org.apache.tomcat.util.digester.Digester.getParser (Digester.java:692)
at org.apache.tomcat.util.digester.Digester.getXMLReader(Digester.java:900)
at org.apache.tomcat.util.digester.Digester.parse(Digester.java:1581)
at
org.apache.tomcat.util.modeler.modules.MbeansDescriptorsDigesterSource.execute
(MbeansDescriptorsDigesterSource.java:227)
at
org.apache.tomcat.util.modeler.modules.MbeansDescriptorsDigesterSource.loadDescriptors
(MbeansDescriptorsDigesterSource.java:210)
at org.apache.tomcat.util.modeler.Registry.load (Registry.java:753)
at org.apache.tomcat.util.modeler.Registry.loadDescriptors(Registry.java:865)
at org.apache.tomcat.util.modeler .Registry.loadDescriptors(Registry.java:843)
at org.apache.tomcat.util.modeler.Registry.findDescriptor (Registry.java:907)
at org.apache.tomcat.util.modeler.Registry.findManagedBean(Registry.java:627)
at org.apache.tomcat.util.modeler .Registry.findManagedBean(Registry.java:962)
at org.apache.tomcat.util.modeler.Registry.registerComponent (Registry.java:793)
at
org.apache.catalina.core.StandardWrapper.registerJMX(StandardWrapper.java:1801)
at
org.apache.catalina.core.StandardContext.registerJMX(StandardContext.java:5200)
at org.apache.catalina.core.StandardContext.start (StandardContext.java:4374)
at org.apache.catalina.core.ContainerBase.addChildInternal(
ContainerBase.java:761)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
at org.apache.catalina.core.StandardHost.addChild (StandardHost.java:525)
at org.apache.catalina.startup.HostConfig.deployDirectory( HostConfig.java:920)
at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:883)
at org.apache.catalina.startup.HostConfig.deployApps (HostConfig.java:492)
at org.apache.catalina.startup.HostConfig.start( HostConfig.java:1138)
at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:311)
at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent
(LifecycleSupport.java:120)
at org.apache.catalina.core .ContainerBase.start(ContainerBase.java:1023)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:719)
at org.apache.catalina.core.ContainerBase.start (ContainerBase.java:1015)
at org.apache.catalina.core .StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:448)
at org.apache.catalina.core.StandardServer.start (StandardServer.java:710)
at org.apache.catalina.startup .Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java
:39)
at sun.reflect.DelegatingMethodAcc
essorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288)
at org.apache.catalina.startup.Bootstrap.main( Bootstrap.java:413)
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 41759] - Migration from 5.5.20 to 6.0.10: parser issue on application deployment
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759
------- Additional Comments From egiraudy@gmail.com 2007-03-04 08:52 -------
Created an attachment (id=19661)
--> (http://issues.apache.org/bugzilla/attachment.cgi?id=19661&action=view)
Web app war fiel
war file to deploy as a test case.
on tomcat startup, it causes the javax.xml.parsers.FactoryConfigurationError
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 41759] - Migration from 5.5.20 to 6.0.10: parser issue on application deployment
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759
------- Additional Comments From william.barker@wilshire.com 2007-03-04 11:14 -------
(In reply to comment #2)
> Obviously invalid, but will look at it to see why it does it.
It is because Modeler in 5.5 uses DOM, and in 6.0 it uses SAX.
I agree that it is invalid, since a webapp shouldn't expect to be able to
change system properties.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 41759] - Migration from 5.5.20 to 6.0.10: parser issue on application deployment
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759
remm@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From remm@apache.org 2007-03-04 09:10 -------
Obviously invalid, but will look at it to see why it does it.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
DO NOT REPLY [Bug 41759] - Migration from 5.5.20 to 6.0.10: parser issue on application deployment
Posted by bu...@apache.org.
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=41759>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=41759
------- Additional Comments From remm@apache.org 2007-03-04 12:38 -------
I did look at it, and it does not work much better in 5.5. Random webapps will
fail (they will no longer be able to use the system XML parser), and some
components fail.
I found that the digester used by the registry was not reused (which causes the
JAXP call which fails). This is a minor optimization which I am going to commit.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org