What's a sealing violation please?
From the log 2004-11-02 09:24:51 StandardContext[/servlets-examples]SessionListener: contextInitialized() 2004-11-02 09:25:52 StandardWrapperValve[putpr]: Servlet.service() for servlet putpr threw exception java.lang.SecurityException: sealing violation: can't seal package nu.xom: already loaded at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) Any help appreciated. Regards DaveP. snip here * -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: What's a sealing violation please?
It's part of the core java security model. If a package is sealed within a jar then packages of the same name cannot be defined in another jar, or elsewhere on the classpath. Within the manifest file of the jar file which is being loaded by your putpr servlet you'll probably have a couple of lines like: Name: nu/xom Sealed: true The XOM jar that I have (xom-1.0d8.jar) doesn't seal its packages. So, you need to find the jar which is sealing the nu.xom package and stop it doing so. (Or work out your xom dependencies) Regards, Jon Pawson, David wrote: From the log 2004-11-02 09:24:51 StandardContext[/servlets-examples]SessionListener: contextInitialized() 2004-11-02 09:25:52 StandardWrapperValve[putpr]: Servlet.service() for servlet putpr threw exception java.lang.SecurityException: sealing violation: can't seal package nu.xom: already loaded at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:55) at java.net.URLClassLoader$1.run(URLClassLoader.java:194) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:187) Any help appreciated. Regards DaveP. snip here * - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: What's a sealing violation please?
Thanks for the reply Jon. -Original Message- From: Jon Wingfield It's part of the core java security model. If a package is sealed within a jar then packages of the same name cannot be defined in another jar, or elsewhere on the classpath. Within the manifest file of the jar file which is being loaded by your putpr servlet you'll probably have a couple of lines like: Name: nu/xom Sealed: true The XOM jar that I have (xom-1.0d8.jar) doesn't seal its packages. So, you need to find the jar which is sealing the nu.xom package and stop it doing so. (Or work out your xom dependencies) I'm guessing its xercesImpl jar? Having removed it the error 'went'. I also got a clue, just import nu.xom.*; rather than individual ones? Unsure which one cleared the error, but its OK now. What the heck do I do if I want xom to validate? regard sDaveP -- DISCLAIMER: NOTICE: The information contained in this email and any attachments is confidential and may be privileged. If you are not the intended recipient you should not use, disclose, distribute or copy any of the content of it or of any attachment; you are requested to notify the sender immediately of your receipt of the email and then to delete it and any attachments from your system. RNIB endeavours to ensure that emails and any attachments generated by its staff are free from viruses or other contaminants. However, it cannot accept any responsibility for any such which are transmitted. We therefore recommend you scan all attachments. Please note that the statements and views expressed in this email and any attachments are those of the author and do not necessarily represent those of RNIB. RNIB Registered Charity Number: 226227 Website: http://www.rnib.org.uk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Sealing violation loading javax.security.auth.AuthPermission
Howdy, You probably have a mix of sealed and non-sealed jar in the same classloading repository. Where is the javax.security.auth package located? Yoav Shapira Millennium ChemInformatics -Original Message- From: Etienne Deleflie [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 25, 2003 1:46 AM To: [EMAIL PROTECTED] Subject: Sealing violation loading javax.security.auth.AuthPermission Hello all, I'm stumped! I'm getting a Sealing violation. and its got me beat. sealing violation trying to access javax.security.auth.AuthPermission . I cant find any reference to the same class in any other jar (eccept our own jars)... the problem does not exist on identical code that is not run with a servlet sandbox. java.lang.SecurityException: Sealing violation loading javax.security.auth.AuthPermission : Package javax.security.auth is sealed. at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappCl assL oader.java:1523) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoade r.ja va:852) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade r.ja va:1273) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoade r.ja va:1156) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310) at com.company.software.userdatabase.UserManager.init(UserManager.java:1 10) etienne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sealing violation loading javax.security.auth.AuthPermission
Hello all, I'm stumped! I'm getting a Sealing violation. and its got me beat. sealing violation trying to access javax.security.auth.AuthPermission . I cant find any reference to the same class in any other jar (eccept our own jars)... the problem does not exist on identical code that is not run with a servlet sandbox. java.lang.SecurityException: Sealing violation loading javax.security.auth.AuthPermission : Package javax.security.auth is sealed. at org.apache.catalina.loader.WebappClassLoader.findClassInternal(WebappClassLoader.java:1523) at org.apache.catalina.loader.WebappClassLoader.findClass(WebappClassLoader.java:852) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1273) at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1156) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:310) at com.company.software.userdatabase.UserManager.init(UserManager.java:110) etienne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Sealing Violation due to inclusion of LifeCycle?
I have been building classes inherited from the org.apache.catalina.realmbase package, and have been struggling with where to put them. One of the reason's I have been doing this is to expose TC's realm implementation within my web applications. The best solution I have found so far is to just drop the apache classes I need for my webapps into a .jar in the common/lib directory. I have been getting most of the functionality I want, but once I override the stop() method of RealmBase, I start getting a sealing violation due to the inclusion of LifeCycle, and LifeCycleException when tomcat starts up. I can see that once my hack gets deeper and deeper into TC code, I will windup with class loader issues, which I would like to avoid. Mostly, I am wondering (hoping) if there is a way to expose my custom user database (defined within GlobalNamingResource) within my webapps without having to worry so much about class loader issues, as I often find down in development that certian apache classes are not exposed within the class loader my web apps are using. I am hoping that the same class I can play with inside my applications, would be the same singleton instance that tomcat uses when it starts - but I haven't found an easy way to expose this. Does this violate some sort of MVC ideology? Randy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Sealing Violation due to inclusion of LifeCycle?
On Mon, 23 Dec 2002, Randy Secrist wrote: Date: Mon, 23 Dec 2002 11:25:51 -0700 From: Randy Secrist [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Sealing Violation due to inclusion of LifeCycle? I have been building classes inherited from the org.apache.catalina.realmbase package, and have been struggling with where to put them. One of the reason's I have been doing this is to expose TC's realm implementation within my web applications. The best solution I have found so far is to just drop the apache classes I need for my webapps into a .jar in the common/lib directory. I have been getting most of the functionality I want, but once I override the stop() method of RealmBase, I start getting a sealing violation due to the inclusion of LifeCycle, and LifeCycleException when tomcat starts up. I can see that once my hack gets deeper and deeper into TC code, I will windup with class loader issues, which I would like to avoid. Mostly, I am wondering (hoping) if there is a way to expose my custom user database (defined within GlobalNamingResource) within my webapps without having to worry so much about class loader issues, as I often find down in development that certian apache classes are not exposed within the class loader my web apps are using. I am hoping that the same class I can play with inside my applications, would be the same singleton instance that tomcat uses when it starts - but I haven't found an easy way to expose this. Does this violate some sort of MVC ideology? The fundamental documentation on how class loaders work in Tomcat is: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html If you look at the directory structure of a standard Tomcat distribution, you'll see that the org.apache.catalina.* classes (from catalina.jar) are loaded into the Catalina class loader, which is not visible to webapps. Therefore, any classes you write that need these APIs must also be stored in the Catalina class loader (putting them in the Common class loader won't help you, because they still wouldn't be able to see the base classes). The configuration option Tomcat supports for this is the privileged attribute on a Context element, which makes the the webapp's parent class loader be the Catalina loader instead of the Shared loader. This is the technique used by the admin and manager webapps that are shipped with Tomcat. WARNING: Use of this technique gives your webapp access to ***all*** of the internal objects of the servlet container, and is therefore very dangerous unless you are absolutely sure that your webapp cannot be abused by malicious users. Randy Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Sealing Violation due to inclusion of LifeCycle?
The fundamental documentation on how class loaders work in Tomcat is: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html If you look at the directory structure of a standard Tomcat distribution, you'll see that the org.apache.catalina.* classes (from catalina.jar) are loaded into the Catalina class loader, which is not visible to webapps. Therefore, any classes you write that need these APIs must also be stored in the Catalina class loader (putting them in the Common class loader won't help you, because they still wouldn't be able to see the base classes). The configuration option Tomcat supports for this is the privileged attribute on a Context element, which makes the the webapp's parent class loader be the Catalina loader instead of the Shared loader. This is the technique used by the admin and manager webapps that are shipped with Tomcat. WARNING: Use of this technique gives your webapp access to ***all*** of the internal objects of the servlet container, and is therefore very dangerous unless you are absolutely sure that your webapp cannot be abused by malicious users. Craig I didn't know about the privileged attribute at all. That could come in handy, but also dangerous. It appears (from the class loaders documentation) that objects from the shared class loader aren't available to the catalina loader as well, while objects created by the common loader are. When you make a context privileged, does that mean that it can still load a jar from the common loader, yet still have the visibility from the catalina, (instead of the external shared) loader? So basically if I make a context privileged, and still have objects in the shared loader, they won't be visible to the context. BUT - if I put everything in the common loader, and make the context privileged, I should be fine... - but possible open to security attacks depending on what I put in there? BTW - I want to thank you for doing this Craig. I have enjoyed using Tomcat and Struts for MVC models while studying at my local university... Randy -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Re: Sealing Violation due to inclusion of LifeCycle?
On Mon, 23 Dec 2002, Tomcat User wrote: Date: Mon, 23 Dec 2002 13:11:05 -0700 From: Tomcat User [EMAIL PROTECTED] Reply-To: Tomcat Users List [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Subject: Re: Sealing Violation due to inclusion of LifeCycle? The fundamental documentation on how class loaders work in Tomcat is: http://jakarta.apache.org/tomcat/tomcat-4.1-doc/class-loader-howto.html If you look at the directory structure of a standard Tomcat distribution, you'll see that the org.apache.catalina.* classes (from catalina.jar) are loaded into the Catalina class loader, which is not visible to webapps. Therefore, any classes you write that need these APIs must also be stored in the Catalina class loader (putting them in the Common class loader won't help you, because they still wouldn't be able to see the base classes). The configuration option Tomcat supports for this is the privileged attribute on a Context element, which makes the the webapp's parent class loader be the Catalina loader instead of the Shared loader. This is the technique used by the admin and manager webapps that are shipped with Tomcat. WARNING: Use of this technique gives your webapp access to ***all*** of the internal objects of the servlet container, and is therefore very dangerous unless you are absolutely sure that your webapp cannot be abused by malicious users. Craig I didn't know about the privileged attribute at all. That could come in handy, but also dangerous. It appears (from the class loaders documentation) that objects from the shared class loader aren't available to the catalina loader as well, while objects created by the common loader are. When you make a context privileged, does that mean that it can still load a jar from the common loader, yet still have the visibility from the catalina, (instead of the external shared) loader? Yes, classes loaded from the Common class loader can still be loaded from a privileged webapp. However, a class loaded from the Common class loader cannot depend on a class loaded from the Catalina class loader -- for example, you cannot put a subclass of org.apache.catalina.realm.RealmBase in the common class loader. That's because Java does not support links from a ClassLoader to its children -- only to its parent. So basically if I make a context privileged, and still have objects in the shared loader, they won't be visible to the context. BUT - if I put everything in the common loader, and make the context privileged, I should be fine... Almost ... see the issue raised above. - but possible open to security attacks depending on what I put in there? It's definitely possible to have security attacks. What that should do is cause you to re-examine whether your webapp itself really needs to update the internal object instances, or just the underlying data. For example, if JDBCRealm was sufficient to meet your needs but you wanted to support dynamically adding new users, it would be straightforward to simply write a non-privileged webapp that updated the same tables you told JDBCRealm to use -- any new user that is added that way becomes immediately allowed to log on. It's not clear from your problem description why you needed to extend RealmBase in the first place, but it is worth considering whether a strategy like this would help you. BTW - I want to thank you for doing this Craig. I have enjoyed using Tomcat and Struts for MVC models while studying at my local university... Randy Craig -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Sealing Violation
I've just installed jakarta-tomcat-4.0.4-b2-01. When I use the startup script to start tomcat, I get the Sealing Violation exception: catalina run Using CATALINA_BASE: c:\jakarta-tomcat-4.0.4-b2-01 Using CATALINA_HOME: c:\jakarta-tomcat-4.0.4-b2-01 Using CATALINA_TMPDIR: c:\jakarta-tomcat-4.0.4-b2-01\temp Using JAVA_HOME: C:\jdk1.3.1_01 Exception during startup processing java.lang.reflect.InvocationTargetException: javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated: java.lang.SecurityException: sealing violation at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:141) at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:224) at org.apache.catalina.startup.Catalina.start(Catalina.java:725) at org.apache.catalina.startup.Catalina.execute(Catalina.java:681) at org.apache.catalina.startup.Catalina.process(Catalina.java:179) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243) I have not mucked with classpaths in the script or moved any XML parser libraries. What's causing this, please? Walden Mathews -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Sealing Violation
I found a couple of messages in the archives about this, but not enough to understand what to do about it. I get the following exception when I try to start Catalina with the 'run' command. This is the 4.0.4.b2-01 package I downloaded last week, and which ran then but not now(??). catalina run Using CATALINA_BASE: c:\jakarta-tomcat-4.0.4-b2-01 Using CATALINA_HOME: c:\jakarta-tomcat-4.0.4-b2-01 Using CATALINA_TMPDIR: c:\jakarta-tomcat-4.0.4-b2-01\temp Using JAVA_HOME: C:\jdk1.3.1_01 Exception during startup processing java.lang.reflect.InvocationTargetException: javax.xml.parsers.FactoryConfigurationError: Provider o rg.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated: java.lang.SecurityException: s ealing violation at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:141) at org.apache.catalina.util.xml.XmlMapper.readXml(XmlMapper.java:224) at org.apache.catalina.startup.Catalina.start(Catalina.java:725) at org.apache.catalina.startup.Catalina.execute(Catalina.java:681) at org.apache.catalina.startup.Catalina.process(Catalina.java:179) at java.lang.reflect.Method.invoke(Native Method) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:243) I did a clean install from the zip file, and still the same problem. I am taking whatever XML parser libs provided in the package, without change. No clue as to what changed between last week and this. Does anyone know how to fix this? Walden Mathews ILX Systems -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Sealing violation Error
I get this Sealing violation error not only when I try to run tomcat but also when I try to execute a class: My Class Path is - C:\xerces\xerces.jar;C:\soap\lib\soap.jar;C:\wstk\wsdl4j\lib\wsdl4j.jar;C:\wstk\uddi4j\lib\uddi4j.jar;C:\wstk\lib\soapenc.jar;C:\wstk\lib\wstk.jar;C:\wstk\lib\xalan.jar;C:\wstk\lib \xss4j.jar;C:\jsse\lib\jsse.jar;C:\jsse\lib\jnet.jar;C:\jsse\lib\jcert.jar;C:\wstk\soap\lib\pop3.jar;C:\wstk\soap\lib\mail.jar;C:\wstk\soap\lib\mailapi.jar;C:\wstk\soap\lib\activat ion.jar;C:\wstk\soap\lib\smtp.jar;C:\soap\SOAPEnv\SOAPEnvelope.jar;c:\webservices\classes;.;C:\jsdk2 .1\server.jar;C:\jsdk2 .1\servlet.jar; c:\ant\lib\ant.jar;C:\Kawa4.1\kawaclasses.zip;c:\jdk1.3\lib\tools.jar;c:\jdk1.3\jre\lib\rt.jar;c:\jdk1.3\jre\lib\i18n.jar I get the error: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at org.apache.crimson.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(DocumentBuilderFactoryImpl.java:88) at com.ibm.uddi.client.UDDIProxy.send(UDDIProxy.java:1180) at com.ibm.uddi.client.UDDIProxy.find_business(UDDIProxy.java:192) at tutorial.UDDI1.main(UDDI1.java:78) java.lang.NullPointerException at com.ibm.uddi.request.FindBusiness.saveToXML(FindBusiness.java:194) at com.ibm.uddi.client.UDDIProxy.send(UDDIProxy.java:1186) at com.ibm.uddi.client.UDDIProxy.find_business(UDDIProxy.java:192) at tutorial.UDDI1.main(UDDI1.java:78) Exception in thread main Process Exit... When I try to run Tomcat: C:\ tomcat run FATAL: configuration error java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Class.java:120) at javax.xml.parsers.SAXParserFactory.newInstance(SAXParserFactory.java:92) at org.apache.tomcat.util.xml.XmlMapper.readXml(XmlMapper.java:210) at org.apache.tomcat.startup.Tomcat.execute(Tomcat.java:187) at org.apache.tomcat.startup.Tomcat.main(Tomcat.java:235) Tomcat classpath is: CLASSPATH=.;c:\jdk1.3\lib\rt.jar;jswdk-1.0.1\lib\jspengine.jar;C:\jsdk2 .1\server.jar;C:\jsdk2 .1\servlet.jar; c:\ant\lib\ant.jar;c:\xerces\xerces.jar;c:\soap\lib\soap.jar;c:\wstk\uddi4j\lib\uddi4j.jar;c:\wstk\wsdli4j\lib\wsdl4j.jar;c:\wstk\lib\wstk.jar;;c:\wstk\lib\xss4j.jar;c:\wstk\soap\l ib\smtp.jar;c:\wstk\soap\lib\mail.jar;c:\wstk\soap\lib\smtp.jar;c:\wstk\soap\lib\mailapi.jar;c:\wstk\soap\lib\activation.jar;c:\webservices\classes;c:\jsse\lib\jcert.jar;c:\jsse\li b\jnet.jar;c:\jsse\lib\jsse.jar;c:\tomcat\classes;c:\tomcat\lib\SERVLET.JAR;c:\tomcat\lib\PARSER.JAR;c:\tomcat\lib\JAXP.JAR;c:\tomcat\lib\ANT.JAR;c:\tomcat\lib\WEBSER~1.JAR;c:\tomc at\lib\JASPER.JAR;C:\jdk1.3\lib\tools.jar I am using tomcat_3_2,soap_2_2,jdk1.3 on Windows 98. I have tried palying with the Tomact configuration using Sun's Xml files instead of Tomact's etc but no success. Thanks all, Sanjay __ Do You Yahoo!? Find the one for you at Yahoo! Personals http://personals.yahoo.com -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
java.lang.SecurityException: sealing violation
Hi, I use tomcat 3.2 and try to read a xml file throught a servlet but i recieve this error : java.lang.Exception: Exception occurred: java.lang.SecurityException: sealing violation at lds.utils.XMLManager.loadXML(XMLManager.java:168) at lds.utils.XMLManager.loadXML(XMLManager.java:183) at lds.servlets.OdataControllerServlet.init(OdataControllerServlet.java:93) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.core.Handler.service(Handler.java:254) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code) at java.lang.Thread.run(Thread.java:479) any idee to help me Patrick PIERRA
Re: java.lang.SecurityException: sealing violation
I am not sure but I belive this is because you are using the JAXP 1.1 libraries from the sun download site, those files does not work with TC4, you must use the jaxp.jar and crimson.jar files included with TC4 (in the jasper directory). Mikael - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, September 26, 2001 10:22 AM Subject: java.lang.SecurityException: sealing violation Hi, I use tomcat 3.2 and try to read a xml file throught a servlet but i recieve this error : java.lang.Exception: Exception occurred: java.lang.SecurityException: sealing violation at lds.utils.XMLManager.loadXML(XMLManager.java:168) at lds.utils.XMLManager.loadXML(XMLManager.java:183) at lds.servlets.OdataControllerServlet.init(OdataControllerServlet.java:93) at javax.servlet.GenericServlet.init(GenericServlet.java:258) at org.apache.tomcat.core.ServletWrapper.doInit(ServletWrapper.java:317) at org.apache.tomcat.core.Handler.init(Handler.java:215) at org.apache.tomcat.core.ServletWrapper.init(ServletWrapper.java:296) at org.apache.tomcat.core.Handler.service(Handler.java:254) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code) at java.lang.Thread.run(Thread.java:479) any idee to help me Patrick PIERRA
tomcat4: sealing violation when reloading servlets
I am encountering sealing violation problems with tomcat 4.0 (nightly build 20010825). Whenever I recompile a servlet or change any .properties files that I use for i18n text messages press reload, it gives ServletException like this: Exception Report: javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:875) ... Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) ... As I have understood it can be avoided by not having conflicts between certain class libraries. I have plenty of them in jre/lib/ext directory... Is there any changes to the class loading mechanism in more current nightly builds? with best wishes, Taavi
Re: tomcat4: sealing violation when reloading servlets
I don't know for sure if this will help, but, if you have application specific .jar files that are stored somewhere other than under your WEB-INF/lib directory, you might want to try to move them there and see if that makes a difference. What I always try to do when resolving a problem like this is revert back to the basic installation, test out the sample programs, make sure that works, then, start adding things back one at a time until it breaks. Jon - Original Message - From: Taavi Tiirik [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, September 07, 2001 2:48 AM Subject: tomcat4: sealing violation when reloading servlets I am encountering sealing violation problems with tomcat 4.0 (nightly build 20010825). Whenever I recompile a servlet or change any .properties files that I use for i18n text messages press reload, it gives ServletException like this: Exception Report: javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:875) ... Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) ... As I have understood it can be avoided by not having conflicts between certain class libraries. I have plenty of them in jre/lib/ext directory... Is there any changes to the class loading mechanism in more current nightly builds? with best wishes, Taavi
Re: tomcat4: sealing violation when reloading servlets
On Fri, 7 Sep 2001, Taavi Tiirik wrote: Date: Fri, 7 Sep 2001 09:48:38 +0200 From: Taavi Tiirik [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: tomcat4: sealing violation when reloading servlets I am encountering sealing violation problems with tomcat 4.0 (nightly build 20010825). Whenever I recompile a servlet or change any .properties files that I use for i18n text messages press reload, it gives ServletException like this: Exception Report: javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:875) ... Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) ... As I have understood it can be avoided by not having conflicts between certain class libraries. I have plenty of them in jre/lib/ext directory... If you have a copy of the JAXP XML parser here ($JAVA_HOME/jre/lib/ext) you can pretty much give up. It won't work. See the release notes document in the Tomcat 4.0 release for information on how to deal with XML parsers in Tomcat 4. Is there any changes to the class loading mechanism in more current nightly builds? with best wishes, Taavi Craig
java.lang.SecurityException: sealing violation - jBuilder4
I have been using jBuilder to develope servlets since JServ through Tomcat 3.2 and now with Catalina. This problem has never come up before ;) It seems that I am having some classpath issues. My jBuilder required libs include: Catalina libs (all jars under catalina home), a DB2 lib (jdbc driver), and the Orielly package (cos.jar). They are defined individually in jBuilders Required Libraries dialog. The Tomcat mail list archives indicate that this is a common problem, but I haven't seen a posting that has helped me. Has anyone overcome this problem? How? message: -- javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3240) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278) at org.apache.catalina.core.StandardService.start(StandardService.java:368) at org.apache.catalina.core.StandardServer.start(StandardServer.java:473) at org.apache.catalina.startup.Catalina.start(Catalina.java:738) at org.apache.catalina.startup.Catalina.execute(Catalina.java:657) at org.apache.catalina.startup.Catalina.process(Catalina.java:178) at org.apache.catalina.startup.Catalina.main(Catalina.java:163) - Root Cause - java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:280) at java.net.URLClassLoader.access$100(URLClassLoader.java:60) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:234) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:670) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:1088) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml(TldLocationsCache.java:164) at org.apache.jasper.compiler.TldLocationsCache.init(TldLocationsCache.java:138) at org.apache.jasper.EmbededServletOptions.init(EmbededServletOptions.java:324) at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:265) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:833) at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:3240) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3350) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1123) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:278) at org.apache.catalina.core.StandardService.start(StandardService.java:368) at org.apache.catalina.core.StandardServer.start(StandardServer.java:473) at org.apache.catalina.startup.Catalina.start(Catalina.java:738) at org.apache.catalina.startup.Catalina.execute(Catalina.java:657) at org.apache.catalina.startup.Catalina.process(Catalina.java:178) at org.apache.catalina.startup.Catalina.main(Catalina.java:163) = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: java.lang.SecurityException: sealing violation - jBuilder4
Catalina's Classpath: D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; D:\jBuilder\jdk1.3\jre\lib\i18n.jar; D:\jBuilder\jdk1.3\jre\lib\jaws.jar; D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; D:\jBuilder\jdk1.3\lib\dt.jar; D:\jBuilder\jdk1.3\lib\tools.jar = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: java.lang.SecurityException: sealing violation - jBuilder4
Tomcat 4 doesn't use the CLASSPATH variable. So, all the .jar files that aren't in the jakarta-tomcat directory will be ignored AFAIK. I did notice one thing that looks odd also. servlet.jar is normally found in common\lib, not server\lib. Not sure if that would make a difference. Jon - Original Message - From: Raimee Stevens [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 06, 2001 1:01 PM Subject: Re: java.lang.SecurityException: sealing violation - jBuilder4 Catalina's Classpath: D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; D:\jBuilder\jdk1.3\jre\lib\i18n.jar; D:\jBuilder\jdk1.3\jre\lib\jaws.jar; D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; D:\jBuilder\jdk1.3\lib\dt.jar; D:\jBuilder\jdk1.3\lib\tools.jar = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Re: java.lang.SecurityException: sealing violation - jBuilder4
I changed the main class to the org.apache.catalina.startup class and my problem went away as abruptly as it appeared. Sorry, that wasn't what I ment to say.. org.apache.catalina.startup.BootStrap class is the correct class. Raimee wrote: That was - D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar - the api dist. not the one that ships with Tomcat. I took that one out believing that to be the cause of the name conflict. Apparently it wasn't. What was causing the problem was that I was loading Tomcat using the org.apache.catalina.startup.Catalina. I changed the main class to the org.apache.catalina.startup class and my problem went away as abruptly as it appeared. I really should have consulted the catalina.bat for the correct info, but I didn't. I had to learn the hard way :doRun if %2 == -security goto doRunSecure %_RUNJAVA% %CATALINA_OPTS% -Dcatalina.home=%CATALINA_HOME% org.apache.catalina.startup.Bootstrap %2 %3 %4 %5 %6 %7 %8 %9 start goto cleanup :doRunSecure %_RUNJAVA% %CATALINA_OPTS% -Djava.security.manager -Djava.security.policy==%CATALINA_HOME%/conf/catalina.policy -Dcatalina.home=%CATALINA_HOME% org.apache.catalina.startup.Bootstrap %3 %4 %5 %6 %7 %8 %9 start goto cleanup The org.apache.catalina.startup.Bootstrap Class name is glaring. Also, Catalina does indeed use a classpath. And also from catalina.bat : set _CLASSPATH=%CLASSPATH% set _CP=%CP% ... rem - Set Up The Runtime Classpath set CP=%CATALINA_HOME%\bin\bootstrap.jar;%JAVA_HOME%\lib\tools.jar set CLASSPATH=%CP%;G:\Tomcat\jakarta-tomcat-4.0-b7\lib\db2java.zip echo Using CLASSPATH: %CLASSPATH% Jonathan Eric Miller wrote: Tomcat 4 doesn't use the CLASSPATH variable. So, all the .jar files that aren't in the jakarta-tomcat directory will be ignored AFAIK. I did notice one thing that looks odd also. servlet.jar is normally found in common\lib, not server\lib. Not sure if that would make a difference. Jon - Original Message - From: Raimee Stevens [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, September 06, 2001 1:01 PM Subject: Re: java.lang.SecurityException: sealing violation - jBuilder4 Catalina's Classpath: D:\tomcat\jakarta-tomcat-4.0-b7\webapps\genNLV\WEB-INF\classes; D:\tomcat\jakarta-tomcat-4.0-b7\bin\bootstrap.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\catalina.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\warp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jakarta-regexp-1.2.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\server\lib\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\namingfactory.jar; D:\tomcat\jakarta-tomcat-4.0-b7\lib\jasper-runtime.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jaxp.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\jasper-compiler.jar; D:\tomcat\jakarta-tomcat-4.0-b7\jasper\crimson.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\jndi.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\naming.jar; D:\tomcat\jakarta-tomcat-4.0-b7\common\lib\resources.jar; D:\tomcat\jakarta-servletapi-4-b7\lib\servlet.jar; D:\SQLLIB\java\db2java.zip;D:\oreilly\lib\cos.jar; D:\jBuilder\jdk1.3\demo\jfc\Java2D\Java2Demo.jar; D:\jBuilder\jdk1.3\jre\lib\i18n.jar; D:\jBuilder\jdk1.3\jre\lib\jaws.jar; D:\jBuilder\jdk1.3\jre\lib\rt.jar;D:\jBuilder\jdk1.3\jre\lib\sunrsasign.jar; D:\jBuilder\jdk1.3\lib\dt.jar; D:\jBuilder\jdk1.3\lib\tools.jar = - Best Regards, Raimee Stevens __ Do You Yahoo!? Get email alerts NEW webcam video instant messaging with Yahoo! Messenger http://im.yahoo.com
Sealing Violation help
Ok, Ok.. You've heard it, written responses, and thought it was wrapped up and no one would ever have this problem again :) I'm trying to embed Tomcat 4 beta 6 into my application. I am also using Castor (http://castor.exolab.org), which requires Xerces. I'm getting the sealing violation after Castor starts and during the startup of Catalina. I have basically created a wrapper to invoke the main of the Bootstrap class for Tomcat. Anyone performed a similiar task? Most of the archives I see relate to deploying web apps, but I'm not able to launch Tomcat to even approach this. I tried copying the tomcat/jasper/jaxp.jar and crimson.jar over to my project's lib directory that the CLASSPATH references, and even moving jaxp, crimson, and xerces around in my classpath in combination. Any ideas? Please don't tell me to RTFM, as I have and still can't get past the issue. I've tried searching the mailing list archives, but most threads are related to web apps, as I mentioned earlier. I'm hoping someone who has done the same thing can give me a cookbook or lessons learned to assist in getting this to work. I've been using Tomcat 3.x for some time and really love the product, and want to try to get it deployed within my application's VM (rather than spawning a separate process). Regards, James DETAILS Here is my current CLASSPATH: LOCALCLASSPATH=3D./lib/activation.jar:./lib/castor-0.9.2-xml.jar:./lib/c= astor-0.9.2.jar:./lib/jaxp.jar:./lib/crimson.jar:./lib/xerces.jar:./class= es:./properties:... Here is the command line launcher: $JAVACMD -Dcatalina.home=3D./tomcat -classpath $LOCALCLASSPATH com.myproject.Boot $@ Here is a listing of my jars for byte sizes, just in case: -rw-r--r--1 jamesNone 295934 Jun 24 23:17 ant-1.3.jar -rw-r--r--1 jamesNone 241856 Jun 24 23:17 ant-optional.jar -rw-r--r--1 jamesNone 517501 Jun 24 23:17 castor-0.9.2-xml.jar -rw-r--r--1 jamesNone 1050741 Jun 24 23:17 castor-0.9.2.jar -rw-r--r--1 jamesNone 187246 Aug 9 22:08 crimson.jar -rw-r--r--1 jamesNone28466 Aug 9 22:08 jaxp.jar -rw-r--r--1 jamesNone 955716 Jun 24 23:18 xerces.jar /DETAILS
SecurityException sealing violation
Hi all, need some help here.. This is what i get as soon as a want to start Tomcat 3.2.2 on a Suse Linux 7.0 Distribution Fatal Configuration Error-SecurityException - sealing violation Sound terrible doesn't it? :-)) Any ideas? Help would be nice Regards Steve
RE: SecurityException sealing violation
Have you run the jvm in verbose mode so you know what class it is trying to load when the exception occurs. Or could you print the stack trace ?? Regards Scott -Original Message- From: Graham, Steve (GIC) [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 3:49 PM To: '[EMAIL PROTECTED]' Subject: SecurityException sealing violation Hi all, need some help here.. This is what i get as soon as a want to start Tomcat 3.2.2 on a Suse Linux 7.0 Distribution " Fatal Configuration Error-SecurityException - sealing violation" Sound terrible doesn't it? :-)) Any ideas? Help would be nice Regards Steve
RE: SecurityException sealing violation
well maybe this will help you: at java.net URLClassloader.defineClass(URLClassloader.java:228) at java.net URLClassloader.access$1(URLClassloader.java:208) at java.net URLClassloader$Classfinder.run(URLClassloader.java:497) at java.security.Accesscontroller.doPriveleged(NativeMethod) and so on and so on
Re: SecurityException sealing violation
grep $CATALINA_HOME/* for sealing, and search the mailing list archives as well. I'm pretty sure the list has gone over this before =) - r On Thu, 23 Aug 2001 15:49:26 +0200 [EMAIL PROTECTED] wrote: Hi all, need some help here.. This is what i get as soon as a want to start Tomcat 3.2.2 on a Suse Linux 7.0 Distribution Fatal Configuration Error -SecurityException - sealing violation Sound terrible doesn't it? :-)) Any ideas? Help would be nice Regards Steve
RE: SecurityException sealing violation
I think the problem is that you are trying to load one class from the standard the classpath, i.e. just a class and then you are trying to load another class from a sealed jar file, please check your classpath and confirm that there is no chance that this can occur. Then like I said earlier, start and run the jvm in verbose mode to obtain class loading info. Scott -Original Message- From: Graham, Steve (GIC) [mailto:[EMAIL PROTECTED]] Sent: Thursday, August 23, 2001 4:11 PM To: '[EMAIL PROTECTED]' Subject: RE: SecurityException sealing violation well maybe this will help you: " at java.net URLClassloader.defineClass(URLClassloader.java:228) " " at java.net URLClassloader.access$1(URLClassloader.java:208) " " at java.net URLClassloader$Classfinder.run(URLClassloader.java:497) " " at java.security.Accesscontroller.doPriveleged(NativeMethod)" and so on and so on
RE: SecurityException sealing violation
I'm not using Catalina
Re: SecurityException sealing violation
That doesn't prevent you from searching the archives at least ;) - r On Thu, 23 Aug 2001 16:21:53 +0200 [EMAIL PROTECTED] wrote: I'm not using Catalina
RE: SecurityException sealing violation
*smile, i didn't say i wouldn't thx
RE: java.lang.SecurityException: sealing violation?
I had the same problem...with the nightly build. The milestone build was fine, however. No changes in code. I'd recommend going with m5 until this is fixed (Craig?). -dan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] e.org]On Behalf Of [EMAIL PROTECTED] Sent: Friday, July 13, 2001 7:46 PM To: [EMAIL PROTECTED] Subject: java.lang.SecurityException: sealing violation? Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy
Re: java.lang.SecurityException: sealing violation?
Hi, Oh dear. TOMCAT IS A JAVA APPLICATION!!! The only time you should need to recompile it is if you want to use JSSE (For SSL) You might want to recompile mod_jk or the like, but thats completely different. You may be getting an error as you do not have the correct privileges to execute the commands in the script. (If it needs to access something from the JDK in Security) Why didn't tomcat work the first time??? Its all very well complaining about it but if you don't give precise details about OS/Tomcat/JDK versions and what happened then we can't help. Post exact details and I'll take a look. Adam. Adam Fowler Help Desk Live Project Information Services University of Wales, Aberystwyth Web guy+author on the TomcatBook Project http://tomcatbook.sourceforge.net e-mail: [EMAIL PROTECTED] On Friday 13 July 2001 18:45, you wrote: Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy
java.lang.SecurityException: sealing violation?
Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy
RE: java.lang.SecurityException: sealing violation?
as far as I know it means that you have a class name collision in two jars and one of them is sealed, I had a similar problem when using xml packages. Try to put jars foreign to tomcat in the begining of the classpath, or at the end... classpath reordering did it for me.. --V. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, July 13, 2001 11:46 AM To: [EMAIL PROTECTED] Subject: java.lang.SecurityException: sealing violation? Okay, I gave up on my tomcat installation. I wiped everything clean and then got all the source in the hopes that it might work better if I compiled vs. dropping binaries. So, there are many confusing aspects of the installation instructions regarding building the source. Seems like maybe the docs don't match up with the behavior of the current releases? Anyway, I plodded thru, I think I got everything straight. BUT, when I run startup.sh, I get the following: java.lang.SecurityException: sealing violation I followed the install instructions that came with the JSSE from Sun. Have no idea what this error means. Can anyone help? Thanks. - Jeremy *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. ***
Sealing violation with Catalina
I have a servlet that needs to invoke the class loader. This, of course, causes a SecurityException due to a sealing violation (trying to invoke arbitrary classes). Well, I've tried changing the Catalina security policy file, catalina.policy, so that it grants the appropriate permissions to the servlet. I've also tried granting all permissions to all code. Neither seems to work. Has anyone successfully overcome this problem with Catalina? I'm using yesterday's nightly build of Catalina, FWIW. Thanks. -dan -- Dan Kirkpatrick, Software Architect Blue Lotus Software+44 (0) 1224 575 985 [EMAIL PROTECTED] http://www.bluelotussoftware.com
RE: What's a sealing violation?
search through some of the tomcat archives.. basically their really annoying classloader problems.. when it tries to load a jar library and its already loaded. you can add a line to the manifest of the jar file.. but like i said search this archive.. theres heaps of stuff about them. regards, warren -Original Message- From: Stephen Coy [mailto:[EMAIL PROTECTED]] Sent: Thursday, 17 May 2001 4:31 PM To: [EMAIL PROTECTED] Subject: Re: What's a sealing violation? The release notes tell all... And it only took me a week to figure that out too :-) Stephen Coy On Thursday, May 17, 2001, at 02:53 PM, Kevin Newman wrote: Hi All, Hardware:IBM ThinkPad OS:Windows2000 Servlet Engine:Tomcat 4.0 B6-Dev Can anyone tell me what's a sealing violation (see stack trace below)? I'm using the nightly build of Tomcat and it works fine on my Desktop system with Struts in the webapps directory. But, for some reason I can't seem to get Struts to work on my laptop. There does not appear to be any difference in the environmental settings, but anything other than the Tomcat index page or the struts-documentation produces an exception. Has anyone else out there seen this problem?
RE: What's a sealing violation?
Thanks Stephen, Next time I'll RTFM. grin I should know better. peace, kln -Original Message- From: Stephen Coy [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 17, 2001 1:31 AM To: [EMAIL PROTECTED] Subject: Re: What's a sealing violation? The release notes tell all... And it only took me a week to figure that out too :-) Stephen Coy On Thursday, May 17, 2001, at 02:53 PM, Kevin Newman wrote: Hi All, Hardware:IBM ThinkPad OS:Windows2000 Servlet Engine:Tomcat 4.0 B6-Dev Can anyone tell me what's a sealing violation (see stack trace below)? I'm using the nightly build of Tomcat and it works fine on my Desktop system with Struts in the webapps directory. But, for some reason I can't seem to get Struts to work on my laptop. There does not appear to be any difference in the environmental settings, but anything other than the Tomcat index page or the struts-documentation produces an exception. Has anyone else out there seen this problem?
RE: What's a sealing violation?
Thanks Warren, Next time I'll RTFM. grin I should know better. peace, kln -Original Message- From: Warren Crossing [mailto:[EMAIL PROTECTED]] Sent: Thursday, May 17, 2001 2:57 AM To: '[EMAIL PROTECTED]' Subject: RE: What's a sealing violation? search through some of the tomcat archives.. basically their really annoying classloader problems.. when it tries to load a jar library and its already loaded. you can add a line to the manifest of the jar file.. but like i said search this archive.. theres heaps of stuff about them. regards, warren -Original Message- From: Stephen Coy [mailto:[EMAIL PROTECTED]] Sent: Thursday, 17 May 2001 4:31 PM To: [EMAIL PROTECTED] Subject: Re: What's a sealing violation? The release notes tell all... And it only took me a week to figure that out too :-) Stephen Coy On Thursday, May 17, 2001, at 02:53 PM, Kevin Newman wrote: Hi All, Hardware:IBM ThinkPad OS:Windows2000 Servlet Engine:Tomcat 4.0 B6-Dev Can anyone tell me what's a sealing violation (see stack trace below)? I'm using the nightly build of Tomcat and it works fine on my Desktop system with Struts in the webapps directory. But, for some reason I can't seem to get Struts to work on my laptop. There does not appear to be any difference in the environmental settings, but anything other than the Tomcat index page or the struts-documentation produces an exception. Has anyone else out there seen this problem?
What's a sealing violation?
Hi All, Hardware:IBM ThinkPad OS:Windows2000 Servlet Engine:Tomcat 4.0 B6-Dev Can anyone tell me what's a sealing violation (see stack trace below)? I'm using the nightly build of Tomcat and it works fine on my Desktop system with Struts in the webapps directory. But, for some reason I can't seem to get Struts to work on my laptop. There does not appear to be any difference in the environmental settings, but anything other than the Tomcat index page or the struts-documentation produces an exception. Has anyone else out there seen this problem? Thanks, Kevin Newman Stack Trace: A Servlet Exception Has Occurred Exception Report: javax.servlet.ServletException: Servlet.init() for servlet jsp threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:852) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:602) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:231) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:225) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2252) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164 ) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:446) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 64) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java :163) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java: 875) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:952) at java.lang.Thread.run(Thread.java:484) Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader .java:664) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader .java:1077) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader .java:976) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at org.apache.jasper.compiler.TldLocationsCache.processWebDotXml(TldLocationsCa che.java:163) at org.apache.jasper.compiler.TldLocationsCache.(TldLocationsCache.java:137) at org.apache.jasper.EmbededServletOptions.(EmbededServletOptions.java:324) at org.apache.jasper.servlet.JspServlet.init(JspServlet.java:263) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:833) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:602) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja va:231) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja va:225) at org.apache.catalina.core.StandardPipeline.invokeNext(StandardPipeline.java:5 66) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:472) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:943) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2252) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:164
Using embedded tomcat / Sealing violation (Tomcat 4.0)
Hi, I'm having some problems using Embedded tomcat (Tomcat 4.x) in my application. Whenever I try to acess a context added dynamically,I get a securityException (it reports Sealing violation). Running the Embedded::main method reports exactly the same error. I supose the error is related with my CLASSPATH env, because I include all the jars in the tomcat distr before executing. I understand that this isn't correct, as the bootstrap.jar should dynamically load all the necessary classes; But bootstrap.jar doesn't have the Embedded class, also it doesn't seems that Embedded does the required dynamic loading like the Bootstrap one. If this is really the problem, what CLASSPATH should I use for running/using the Embedded tomcat? Should I add Embedded to the bootstrap.jar? Thanks for all, Artur Matos ([EMAIL PROTECTED]) - Everyone should have http://www.freedom2surf.net/
sealing violation
Hello, I am trying to deploy Tomcat 4.0b3 with Java 1.3. When I do startup.sh, I get: ERROR reading /usr/local/conf/server.xml At Line 75 /Server/Service/Engine/ name=Standalone defaultHost=localhost debug=0 Catalina.start: java.lang.SecurityException: sealing violation java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) Searching the mail archive gave me a point, my jar files are symbolic links to the real ones. Also, they contains /../, which seems to be the problem(?). I have a very good reason to do it, so what I would like to do, is turn off this security feature. Can you please tell me how to do this? Thanks, Laszlo
RE: sealing violation
From what I have read on the list, this error is normally (99%) related to having mixed versions of the servlet jar's in your class path. Make sure that you are not sharing the servlet.jar from a previous version of the spec with the one distributed with tomcat. -Original Message- From: Boszormenyi GCS Laszlo [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Monday, April 23, 2001 5:44 AM To: [EMAIL PROTECTED] Subject: sealing violation Hello, I am trying to deploy Tomcat 4.0b3 with Java 1.3. When I do startup.sh, I get: ERROR reading /usr/local/conf/server.xml At Line 75 /Server/Service/Engine/ name=Standalone defaultHost=localhost debug=0 Catalina.start: java.lang.SecurityException: sealing violation java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) Searching the mail archive gave me a point, my jar files are symbolic links to the real ones. Also, they contains /../, which seems to be the problem(?). I have a very good reason to do it, so what I would like to do, is turn off this security feature. Can you please tell me how to do this? Thanks, Laszlo
Re: sealing violation
* CPC Livelink Admin [EMAIL PROTECTED] [010423 16:11]: From what I have read on the list, this error is normally (99%) related to having mixed versions of the servlet jar's in your class path. Make sure that you are not sharing the servlet.jar from a previous version of the spec with the one distributed with tomcat. The machine is just installed, so it is sure that there were not even a jdk. I was playing with the paths, and finaly I unset all of them. Then tried startup.sh again. It complained about JAVA_HOME and CATALINA_HOME. I set up to the real files, without symlinks: export JAVA_HOME=/usr/local/encap/jdk1.3.0_02 export CATALINA_HOME=/usr/local/encap/jakarta-tomcat-4.0b3 startup.sh gave me sealing violation again. The $CLASSPATH was empty for sure, I modified the startup.sh to do an echo on it, and I saw an empty line only this time. Anyway, Catalina/Tomcat reports: Using CLASSPATH: /usr/local/encap/jakarta-tomcat-4.0b3/bin/bootstrap.jar:/usr/local/encap/jdk1.3.0_02/lib/tools.jar Using CATALINA_HOME: /usr/local/encap/jakarta-tomcat-4.0b3 Is it ok? Anyway, I am going to throw in the towel... Absolutely no more idea. Bye, Laszlo
Request; was: sealing violation
Maybe the jars are too different versions for me. That is why I ask some people to send the output of ls -l $CATALINA_HOME/jasper $CATALINA_HOME/server/lib Thanks, Laszlo
sealing violation
What can I do to stop getting this when I try to install tomcat 3.2.1 as an NTSERVICE with jdk1.3? Thanks for your help Regards Warrell Harries
javax.servlet.ServletException: sealing violation
I just moved my server side java class to another directory and altered the classpaths to the new directory. I am getting follwoing exception while calling my jsp javax.servlet.ServletException: sealing violation at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:459) at jsp.dates._0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0._jspServic e(_0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0.java:91) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) Root cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at com.commerceroute.rosettanet.xml.template.BaseTemplate.(BaseTemplate.java:14 ) at com.commerceroute.rosettanet.xml.template.CRMsg.(CRMsg.java:26) at com.commerceroute.sxmsgr.MsgCreator.(MsgCreator.java:31) at jsp.dates._0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0._jspServic e(_0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0.java:62) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) Any idea why is this happening ? TIA Mandar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: javax.servlet.ServletException: sealing violation
Not sure if this is your case, but I had a similar problem when using JAXP 1.1. The problem is there's some sort of class name collision between jar files... I had to reorder the CLASSPATH for tomcat to get rid of this problem. Regards, VG. Mandar Joshi wrote: I just moved my server side java class to another directory and altered the classpaths to the new directory. I am getting follwoing exception while calling my jsp javax.servlet.ServletException: sealing violation at org.apache.jasper.runtime.PageContextImpl.handlePageException(PageContextImp l.java:459) at jsp.dates._0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0._jspServic e(_0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0.java:91) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) Root cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:297) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:286) at java.lang.ClassLoader.loadClass(ClassLoader.java:253) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at com.commerceroute.rosettanet.xml.template.BaseTemplate.(BaseTemplate.java:14 ) at com.commerceroute.rosettanet.xml.template.CRMsg.(CRMsg.java:26) at com.commerceroute.sxmsgr.MsgCreator.(MsgCreator.java:31) at jsp.dates._0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0._jspServic e(_0002fjsp_0002fdates_0002fnewdate_0002ejspnewdate_jsp_0.java:62) at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:119) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.jasper.servlet.JspServlet$JspServletWrapper.service(JspServlet.ja va:177) at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:318) at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:391) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:404) at org.apache.tomcat.core.Handler.service(Handler.java:286) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:210) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:498) at java.lang.Thread.run(Thread.java:484) Any idea why is this happening ? TIA Mandar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
TC 4.0 20010314: STILL HAS sealing violation BUG for JSP related to JAXP
Just a head up. I'm still getting the sealing violation BUG. Works fine with Servlets, but not JSP. TC 4.0 20010314 javax.servlet.SecurityException: sealing violation
sealing violation with Tomcat 4.0
I am attempting to run Tomcat 4.0, but when it tries to load my servlet, I get a sealing violation (see traceback below). Now I understand that a sealing violation is when a sealed jar file attempts to load a class in the same package that is not in the jar file. But in this case, I get the exception whether the classes are in jar files (not sealed), or as individual class files. The class that it is trying to instantiate when the exception is thrown is in the same package as the class it is contained in. Can anyone shed some light on what the problem is? Thanks, Chris Here is the exception: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoader.java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoader.java:906) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at com.choicehotels.webcauldron.Servlet.(Servlet.java:115) at java.lang.Class.newInstance0(Native Method) at java.lang.Class.newInstance(Class.java:237) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:740) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:227) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:196) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038) at org.apache.catalina.connector.warp.WarpContext.invoke(WarpContext.java:100) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:161) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.connector.warp.WarpHost.invoke(WarpHost.java:130) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:159) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.connector.warp.WarpEngine.invoke(WarpEngine.java:115) at org.apache.catalina.connector.warp.WarpRequestHandler.process(WarpRequestHandler.java:165) at org.apache.catalina.connector.warp.WarpHandler.run(WarpHandler.java:156) at java.lang.Thread.run(Thread.java:484) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: sealing violation in 4.0m5
Hi Bill. I believe a "sealing violation" is when a class which was loaded under one classloader tries to call a class loaded under a different classloader, in circumstances where this isn't allowed. I suggest that the problem is therefore something to do with classpaths, ie your classpath includes some files it shouldn't. The result is that tomcat is expecting code to be loaded by a particular classloader, but because it is in the classpath, it has already been loaded by the system class loader. Hope this helps, Simon -Original Message- From: Bill Pfeiffer [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, December 20, 2000 6:06 AM To: Tomcat Subject: sealing violation in 4.0m5 Trying to port my 3.2 app to 4.0. One simple page works, but the main page of my app yeilds the exception below. Any idea what a "sealing violation' is? Sounds like a security issue. Ideas? TIA, Bill Pfeiffer A Servlet Exception Has Occurred Exception Report: javax.servlet.ServletException: Servlet.init() for servlet OasisCommand threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:774) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544 ) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. ja va:227) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. ja va:196) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 61 ) at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va :159) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.jav a: 811) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:89 0) at java.lang.Thread.run(Thread.java:484) Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoad er .java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoad er .java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoad er .java:906) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at com.pdma.oasis.servlets.OasisCommandServlet.initCommands(OasisCommandServl et .java:94) at com.pdma.oasis.servlets.OasisCommandServlet.init(OasisCommandServlet.java: 27 ) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:755) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544 ) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. ja va:227) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. ja va:196) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 61 ) at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va :159) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.jav a: 811) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:89 0) at java.lang.Thread.run(Thread.java:484)
Re: sealing violation in 4.0m5
Classpath is not set (ie set to empty) when starting Tomcat. My web app does include some jars, none of which should clash with Tomcat. Any other ideas on what to start looking for in terms of a clash?. The class in question appears to be one of my own in the WEB-INF/class directory. Thanks, Bill Pfeiffer - Original Message - From: "Kitching Simon" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, December 20, 2000 6:06 AM Subject: RE: sealing violation in 4.0m5 Hi Bill. I believe a "sealing violation" is when a class which was loaded under one classloader tries to call a class loaded under a different classloader, in circumstances where this isn't allowed. I suggest that the problem is therefore something to do with classpaths, ie your classpath includes some files it shouldn't. The result is that tomcat is expecting code to be loaded by a particular classloader, but because it is in the classpath, it has already been loaded by the system class loader. Hope this helps, Simon -Original Message- From: Bill Pfeiffer [SMTP:[EMAIL PROTECTED]] Sent: Wednesday, December 20, 2000 6:06 AM To: Tomcat Subject: sealing violation in 4.0m5 Trying to port my 3.2 app to 4.0. One simple page works, but the main page of my app yeilds the exception below. Any idea what a "sealing violation' is? Sounds like a security issue. Ideas? TIA, Bill Pfeiffer A Servlet Exception Has Occurred Exception Report: javax.servlet.ServletException: Servlet.init() for servlet OasisCommand threw exception at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:774) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544 ) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. ja va:227) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. ja va:196) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 61 ) at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va :159) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.jav a: 811) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:89 0) at java.lang.Thread.run(Thread.java:484) Root Cause: java.lang.SecurityException: sealing violation at java.net.URLClassLoader.defineClass(URLClassLoader.java:234) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at org.apache.catalina.loader.StandardClassLoader.findClass(StandardClassLoad er .java:648) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoad er .java:987) at org.apache.catalina.loader.StandardClassLoader.loadClass(StandardClassLoad er .java:906) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:313) at com.pdma.oasis.servlets.OasisCommandServlet.initCommands(OasisCommandServl et .java:94) at com.pdma.oasis.servlets.OasisCommandServlet.init(OasisCommandServlet.java: 27 ) at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:755) at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:544 ) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve. ja va:227) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve. ja va:196) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:977) at org.apache.catalina.core.StandardContext.invoke(StandardContext.java:2038) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:1 61 ) at org.apache.catalina.valves.ValveBase.invokeNext(ValveBase.java:242) at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:414) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:975) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.ja va :159) at org.apache.catalina.core.ContainerBase.invo
Re: sealing violation in 4.0m5
Bill Pfeiffer wrote: Classpath is not set (ie set to empty) when starting Tomcat. With Tomcat 4.0 using standard startup scripts, this does not matter -- the user's CLASSPATH variable is totally ignored. My web app does include some jars, none of which should clash with Tomcat. My understanding is that a "sealing violation" is not caused by a conflict with Tomcat -- rather, it's caused when you try to load a class A in a particular package from one JAR, and class B from the same package from another JAR. I do not believe it matters whether it's the same class loader or not; the issue is that a sealed package should be completely loaded from a single JAR. But I'm not done doing my own research to understand this problem, either. Any other ideas on what to start looking for in terms of a clash?. The class in question appears to be one of my own in the WEB-INF/class directory. Do you by chance have some un-JAR'd classes under WEB-INF/classes, and some other classes in the same package found in a JAR file? Thanks, Bill Pfeiffer Craig McClanahan
Tomcat 4.0 m3, 4 sealing violation
Hi all, I get package sealing violations when I run my web app on Tomcat 4.0 m3 and m4. I never got these with previous releases, and it looks to me as if the cause is the addition of the sealed crimson.jar JAR file to the library. Problem is that my app uses JDOM b4, which is using Xerces 1.1.2, and Xerces contains a bunch of JAXP/DOM/SAX classes that also appear in crimson.jar (hence the sealing violation). Does anybody have any advice on how best to handle this situation? I guess that one way is to remove the duplicate classes from either crimson.jar or xerces_1_1_2.jar, but that seems less than ideal, and could easily lead to breakage. Maybe some solution involving loading the JARs with different class loaders? Thanks, Willie
Re: Tomcat 4.0 m3, 4 sealing violation
Willie Wheeler wrote: Hi all, I get package sealing violations when I run my web app on Tomcat 4.0 m3 and m4. I never got these with previous releases, and it looks to me as if the cause is the addition of the sealed crimson.jar JAR file to the library. Problem is that my app uses JDOM b4, which is using Xerces 1.1.2, and Xerces contains a bunch of JAXP/DOM/SAX classes that also appear in crimson.jar (hence the sealing violation). Does anybody have any advice on how best to handle this situation? I guess that one way is to remove the duplicate classes from either crimson.jar or xerces_1_1_2.jar, but that seems less than ideal, and could easily lead to breakage. Maybe some solution involving loading the JARs with different class loaders? Thanks, Willie Welcome to the wonderful world of classloaders :-). You're correct -- trying to remove classes from one or the other of the JAR files is not going to work at all. Each library will be depending on its own internal implementation of those classes. The crimson.jar file is placed in $CATALINA_HOME/lib (and therefore visible to web apps) because Jasper needs a JAXP-1.1 compatible parser. It would be technically feasible for Jasper to load its own XML parser in a private classloader, but this is not a trivial amount of work. Once Xerces is upgraded to JAXP-1.1 compatibility you will simply be able to use Xerces instead (and thus not have these conflicts). If your app does not need JSP, you could simply remove crimson.jar from $CATALINA_HOME/lib (you will want to comment out the JSP servlet in $CATALINA_HOME/conf/web.xml as well). If you do, I'm afraid there isn't much that can be done in the short run until all the parsers catch back up with JAXP compatibility again. Craig McClanahan
Re: Tomcat ... sealing violation - [Cool! Answered before I get my message echoed ;)]
"Craig R. McClanahan" wrote: Willie Wheeler wrote: Hi all,
