• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Liutauras Vilda
  • Paul Clapham
Sheriffs:
  • paul wheaton
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Piet Souris
Bartenders:
  • Mike London

Why DefaultListableBeanFactory causing bean creation loop in Tomcat

 
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a Spring based web application that I am trying to load in my local Tomcat. (Spring 3.0.5, Tomcat 6)

Right now when the application is starting up on Tomcat, while it is trying to initialize the Spring Web application context, it is going into an infinite loop trying to create the beans I have defined in my XML config files. For example one of the beans bathTransactionManager, you can see below how it gets created and destroyed over and over again...



Any ideas what is causing this?

Thanks in advance for any help.
 
Jehan Jaleel
Ranch Hand
Posts: 196
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
One clue I have to the root of this problem is that the application context file imports beans from other config files like so...



Now in production (and in other developers' setup), these other config files are always in JARs within the lib folder. But what I did was deploy to Tomcat directly from MyEclipse and this caused the application to be in exploded format (so the config files are in the classes folder). When I deleted the files in the classes folder and imported the JARs, then the problem went away. But it is still strange. Why would the location of the files matter as long as it within the classpath?

Thanks.
reply
    Bookmark Topic Watch Topic
  • New Topic