-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Neeraj,
On 4/4/14, 3:46 AM, Neeraj Sinha wrote: > On 3 April 2014 23:06, Christopher Schultz > <ch...@christopherschultz.net>wrote: > > Neeraj, > > On 4/2/14, 4:23 AM, Neeraj Sinha wrote: >>>> I am trying to start tomcat on linux and I am getting >>>> LifecycleException exception whose snippet is below: >>>> >>>> Apr 2, 2014 8:33:53 AM >>>> org.apache.catalina.core.AprLifecycleListener init INFO: The >>>> APR based Apache Tomcat Native library which allows optimal >>>> performance in production environments was not found on the >>>> java.library.path: >>>> > /usr/java/jdk1.6.0_38/jre/lib/amd64/server:/usr/java/jdk1.6.0_38/jre/lib/amd64:/usr/java/jdk1.6.0_38/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib >>>> >>>> > > Apr 2, 2014 8:33:53 AM org.apache.coyote.AbstractProtocol init >>>> INFO: Initializing ProtocolHandler ["http-bio-8080"] Apr 2, >>>> 2014 8:33:53 AM org.apache.coyote.AbstractProtocol init >>>> INFO: Initializing ProtocolHandler ["ajp-bio-8009"] Apr 2, >>>> 2014 8:33:53 AM org.apache.catalina.startup.Catalina load >>>> INFO: Initialization processed in 890 ms Apr 2, 2014 8:33:53 >>>> AM org.apache.catalina.startup.Catalina start SEVERE: >>>> Catalina.start: org.apache.catalina.LifecycleException: >>>> Failed to start component [StandardServer[8005]] at >>>> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) >>>> >>>> > >>>> at org.apache.catalina.startup.Catalina.start(Catalina.java:684) >>>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native >>>> Method) at >>>> > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) >>>> >>>> > > at >>>> > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) >>>> >>>> > > at java.lang.reflect.Method.invoke(Method.java:597) >>>> at >>>> org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:322) >>>> >>>> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:451) >>>> Caused by: java.lang.NoSuchMethodError: >>>> org.apache.naming.NamingContext.setExceptionOnFailedWrite(Z)V >>>> at >>>> > org.apache.catalina.core.NamingContextListener.lifecycleEvent(NamingContextListener.java:264) >>>> >>>> > > at >>>> > org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) >>>> >>>> > > at >>>> > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) >>>> >>>> > > at >>>> > org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:724) >>>> >>>> > > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) >>>> ... 7 more Apr 2, 2014 8:33:53 AM >>>> org.apache.catalina.startup.Catalina start INFO: Server >>>> startup in 6 ms >>>> >>>> One reason I could guess for this is that Tomcat jar may not >>>> be proper but I have checked that and that looks fine to me. >>>> >>>> Appreciated if somebody could help me. > >> What version of Tomcat are you trying to run? Have you modified >> your Tomcat installation other than changes to server.xml and >> adding web applications to it? Do any of your web applications >> have any Tomcat JAR files in them? > > Thanks. I am using version 7.0.34. I have not modified anything in > tomcat installation but I have added JBoss client jars in > /tomcat/lib which is required for web apps to access EJB > services. This is almost certainly the problem. Which JARs did you add? > Actually, I have this tomcat installed and running in few other > environments also without any problem. I am trying to setup this on > a new system where I copied the complete tomcat and apache files > from one of the environment and modified their configuration files > for domain and host configuration. Apart from this no other > changes. You really shouldn't mix libraries from other containers into Tomcat's lib/ directory. JBoss uses Tomcat internally as its servlet container, so mixing those libraries can seriously confuse things -- as you've seen. > Yesterday, I tried to install from a fresh tomcat build and I > started getting the earlier mentioned exceptions when I added the > required Jboss client jars. So, this means that Jboss jars might > have same class which catalina.jar have but I am wondering howcome > same setup is working fine for other environments. I'm just going to go ahead and say that this is "not a supported configuration" and leave it at that. It could take a while to figure out the exact combination of offending libraries and classes, but it's just not worth it: you need to change the way you deploy. If you need EJB and don't want to use JBoss, consider using TomEE: it uses Tomcat as its servlet container and provider DJB support using OpenEJB. So if you're looking for something lighter than JBoss, take a look at TomEE. - -chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBCAAGBQJTPsMZAAoJEBzwKT+lPKRYkWgP/Ai3ihS6qLiqRsXJWMosRgh/ aqRa6mzhKt6+31lmpgZyGvrthkmTzWCiomoYGDNI8bin55hfCaTahs0mOdzrVIKP EeGTaVT4T3XJGvI79iB/VfI8665h/qOTL+BU8qc1NLd2WMooqEb5KrgCqL6PGdni /lsTnahVk2/C/u9qCO11wd5JsY+AkFGCeWPUqVLQqsn9u3hw9Xm79kYkGJRSiIM4 JXKVzLHXyZFNkt0sTTzLQvhf/X1wPXDcVBnc1funAP8gm4xwqJrQrAk5IRp9pLzJ zz+mAnISMJATHEbDNqJHLQeLhgwbhpJ9qrzTW8tTCEH6MMOEu+hKBbWSN7EQMJWK M3duG8OVLFzMcsm7kJSfV5VXwmb6H2Ouio7kS/uK1Uh3hYPC3XHfpbhdrMQtYM1r yZdZAmwUckjBAWw+DW+ve31K74yIh5+6M9loDo967wneuwMpEdcypx+gywKdTJY8 LHFRgJ1J0LpdwQv1fsQEDrwupuooJcqfeRCtbnyzIwP4dZkB68cyxz+xI+NWtUKI WmkYgpmqDwuDh3ABcxO+fK7izgKerv4cgl23H6k6+PMl4raPGQI0s4E6DkV3Wv2q 3sCTOMNPQu9kuacRQNOPwrvvAgbV40DzanpcQrgSFLx3/Esx1kSDcO/nCxRnQGi/ EHBkMz93ovTY4ZjyZOqk =mDPn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
