Return-Path: X-Original-To: apmail-tomcat-users-archive@www.apache.org Delivered-To: apmail-tomcat-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9495918167 for ; Thu, 3 Sep 2015 11:31:05 +0000 (UTC) Received: (qmail 59812 invoked by uid 500); 3 Sep 2015 11:31:02 -0000 Delivered-To: apmail-tomcat-users-archive@tomcat.apache.org Received: (qmail 59755 invoked by uid 500); 3 Sep 2015 11:31:02 -0000 Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Users List" Delivered-To: mailing list users@tomcat.apache.org Received: (qmail 59744 invoked by uid 99); 3 Sep 2015 11:31:01 -0000 Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Sep 2015 11:31:01 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 7ED4E182200 for ; Thu, 3 Sep 2015 11:31:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-us-east.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 169ru2Akbzk8 for ; Thu, 3 Sep 2015 11:30:49 +0000 (UTC) Received: from mail-vk0-f47.google.com (mail-vk0-f47.google.com [209.85.213.47]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id E588B42B46 for ; Thu, 3 Sep 2015 11:30:48 +0000 (UTC) Received: by vkhf67 with SMTP id f67so22497519vkh.1 for ; Thu, 03 Sep 2015 04:30:48 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=XtdwW8WTpbXLP+gz2CZka/jue1opPFPzYyZqT0GSHA0=; b=Z5O14dzdXmNXhBrwQD9GNxFnr2LC5xN8HXJWxBoTUfzxkNjIQHvWmWgizWy87a7EOL B4uUom3De9Mlif6Xr99vEtHU4QNYfV/AtMIxLfufoxYWcGcB4Y98wNiKXH/WMYePI4lB jAkKrXXfl6cejSHFlyr0pCbXQFlrjWArTj/qvsRBuWrSqyo/ZFde66GZTshEJM2Tg79w lGkp8zPsWIQbHYN8/UZExubu/KUwxfI9jauVCowqtSP8DqkYEsoSFV9XvI146pM8o9Y6 uV1NzRaD5vzGTriCsupZSFmAlMWLpxLMEfhTo1q1bvWUaAlzo89PFHU6/Chi358V0wH/ QCvQ== X-Gm-Message-State: ALoCoQlt98kaIak+G5ONe3l90CG+E2WWiSr7t/7HS0+RtzeIEABZBVcu887PTQSbbfD/8LwSa248 MIME-Version: 1.0 X-Received: by 10.52.74.104 with SMTP id s8mr21598774vdv.6.1441279848470; Thu, 03 Sep 2015 04:30:48 -0700 (PDT) Received: by 10.103.91.139 with HTTP; Thu, 3 Sep 2015 04:30:48 -0700 (PDT) In-Reply-To: References: Date: Thu, 3 Sep 2015 17:00:48 +0530 Message-ID: Subject: Re: Grails war file not starting on Tomcat 7.0.64 From: Ashish Gupta To: Tomcat Users List Content-Type: multipart/alternative; boundary=20cf307f34ce63f2d9051ed61d66 --20cf307f34ce63f2d9051ed61d66 Content-Type: text/plain; charset=UTF-8 > Hi , > > I have a grails application war file, built in production mode. The Grails > version I am using is 2.1.1 and I am building the war from command prompt. > My OS is UBUNTU 12.0.4. > > The war is generated without errors . But when I am deploying it to > Tomcat(7.0.64), the app is not starting. > > I am getting the following info in the log: > > localhost.log > > Sep 03, 2015 12:29:49 PM org.apache.catalina.core.ApplicationContext log > INFO: No Spring WebApplicationInitializer types detected on classpath > Sep 03, 2015 12:29:49 PM org.apache.catalina.core.ApplicationContext log > INFO: Initializing Spring root WebApplicationContext > > catalina.out > > Sep 03, 2015 12:31:05 PM org.apache.catalina.core.StandardContext > startInternal > SEVERE: One or more listeners failed to start. Full details will be found > in the appropriate container log file > Sep 03, 2015 12:31:05 PM org.apache.catalina.core.StandardContext > startInternal > SEVERE: Context [/App] startup failed due to previous errors > This is indicating that your application failed to start properly. Try looking in the `logs/catalina.yyyy-mm-dd.log` file for more details. There should be an exception that shows you why the app failed to start. Thanks for the response. This is the message I am getting in catalina.yyyy-mm-dd.log : org.apache.catalina.core.StandardContext startInternal SEVERE: One or more listeners failed to start. Full details will be found in the appropriate container log file Sep 3, 2015 4:46:55 PM org.apache.catalina.core.StandardContext startInternal SEVERE: Context [] startup failed due to previous errors Just wanted to make sure, it this error related to some configuration specific to my project or is a general issue. Thanks, Ashish. On Thu, Sep 3, 2015 at 4:48 PM, Daniel Mikusa wrote: > On Thu, Sep 3, 2015 at 3:26 AM, Ashish Gupta > wrote: > > > Hi , > > > > I have a grails application war file, built in production mode. The > Grails > > version I am using is 2.1.1 and I am building the war from command > prompt. > > My OS is UBUNTU 12.0.4. > > > > The war is generated without errors . But when I am deploying it to > > Tomcat(7.0.64), the app is not starting. > > > > I am getting the following info in the log: > > > > localhost.log > > > > Sep 03, 2015 12:29:49 PM org.apache.catalina.core.ApplicationContext log > > INFO: No Spring WebApplicationInitializer types detected on classpath > > Sep 03, 2015 12:29:49 PM org.apache.catalina.core.ApplicationContext log > > INFO: Initializing Spring root WebApplicationContext > > > > catalina.out > > > > Sep 03, 2015 12:31:05 PM org.apache.catalina.core.StandardContext > > startInternal > > SEVERE: One or more listeners failed to start. Full details will be found > > in the appropriate container log file > > Sep 03, 2015 12:31:05 PM org.apache.catalina.core.StandardContext > > startInternal > > SEVERE: Context [/App] startup failed due to previous errors > > > > This is indicating that your application failed to start properly. Try > looking in the `logs/catalina.yyyy-mm-dd.log` file for more details. There > should be an exception that shows you why the app failed to start. > > Dan > > > > > > > My Java details are : > > > > java version "1.6.0_45" > > Java(TM) SE Runtime Environment (build 1.6.0_45-b06) > > Java HotSpot(TM) 64-Bit Server VM (build 20.45-b01, mixed mode) > > > > Also found this on my grails server log: > > > > INFO groovy.grails.commons.spring.GrailsWebApplicationContext Refreshing > > > > > org.codehaus.groovy.grails.commons.spring.GrailsWebApplicationContext@4dde8e1b > > : > > startup date [Thu Sep 03 12:40:52 IST 2015]; parent: Root > > WebApplicationContext > > [2015-09-03 12:40:53.180] INFO > > groovy.grails.commons.spring.GrailsWebApplicationContext Bean > > 'dataSourceUnproxied' of type [class > > org.apache.tomcat.jdbc.pool.DataSource] is not eligible for getting > > processed by all BeanPostProcessors (for example: not eligible for > > auto-proxying) > > [2015-09-03 12:40:53.181] INFO > > groovy.grails.commons.spring.GrailsWebApplicationContext Bean > 'dataSource' > > of type [class > > org.springframework.jdbc.datasource.TransactionAwareDataSourceProxy] is > not > > eligible for getting processed by all BeanPostProcessors (for example: > not > > eligible for auto-proxying) > > > > > > Any help will be appreciated. > > Thanks in advance , > > Ashish. > > > --20cf307f34ce63f2d9051ed61d66--