tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Daniel Mikusa <dmik...@pivotal.io>
Subject Re: Grails war file not starting on Tomcat 7.0.64
Date Thu, 03 Sep 2015 12:28:29 GMT
On Thu, Sep 3, 2015 at 7:30 AM, Ashish Gupta <ashish.gupta@thinkvidya.com>
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.
>
> 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.
>

It's an issue with the app or the app's configuration, not Tomcat.  There
should be an exception in the logs which gives you more details.  Look
through `logs/`.  The exception will tell you what the application did to
cause the problem.

Dan



>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Thu, Sep 3, 2015 at 4:48 PM, Daniel Mikusa <dmikusa@pivotal.io> wrote:
>
> > On Thu, Sep 3, 2015 at 3:26 AM, Ashish Gupta <
> ashish.gupta@thinkvidya.com>
> > 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.
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message