• 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 ...
  • Campbell Ritchie
  • Tim Cooke
  • Devaka Cooray
  • Ron McLeod
  • Jeanne Boyarsky
  • Liutauras Vilda
  • paul wheaton
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
  • Tim Holloway
  • Martijn Verburg
  • Frits Walraven
  • Himai Minh

Strange database problem in Glassfish

Ranch Hand
Posts: 216
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello to all,

This is a very strange problem and I hope I can explain it properly. I have two web applications deployed in Glassfish 2.1. Both apps are Spring-based and they use Hibernate. Both are configured via properties files in the classpath. When only one application is deployed all is well and good. However, when the apps are both deployed there is this behaviour:

One of the apps fails because it tries to use the database which does not belong to it i.e. the db that was configured for the other app. So I get a situation where the application is accessing the wrong database and trying to use tables and then failing to find those table well, because it's the wrong db. What could be causing this? Is it a Hibernate issue? The apps work fine in Tomcat. I have verified that both applications are configured using the correct property files when they are deployed.

Please shed some light because I'm going nuts. Anthing will be helpful at this stage ;) Thanks.
I'm full of tinier men! And a tiny ad:
the value of filler advertising in 2021
    Bookmark Topic Watch Topic
  • New Topic