• 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
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Out Of Memory Exception on Weblogic 8.1 SP5

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

We are facing a very peculiar problem. One of our application is into Production since last 2.5 years, and running efficiently on Weblogic 7.0 SP2. Some time ago, we decided to migrate it to Weblogic 8.1. It ran perfectly fine on SP2, and SP3 without any problems. After running it through multiple test rounds, we thought that it was ready for Production migration.

When we checked the BEA website, we noticed that SP5 had come out, so we downloaded it and deployed the application on it. But after starting the application, it is giving a java.lang.OutOfMemoryException. The same ear file runs perfectly fine on Weblogic 7.0 SP2, 8.1 SP2, 8.1 SP3, but throws out this exception on SP5. We've made sure that all the configuration settings (JVM heap size, JDBC connections, etc.) are exactly the same on all versions, but still we are getting the exception.

We have also tried swapping the Sun JDKs, i.e running SP3 on the JDK which comes with SP5, and vice-versa. SP3 runs properly on both JDKs, while SP5 throws the exception on both JDKs. Then we tried running it with JRockit JVM, and it did not give the exception the first time around. But this is not reproducible, i.e. sometimes it throws the exception, and sometimes it does not.

Any help would be greatly appreciated.

Thanks in advance,
Prasanna
 
Ranch Hand
Posts: 775
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I'd recommend getting a BEA support contract and asking them about it. They often know about such problems and have patches that are available if you are a paying customer.

If you can't do that, your only option may be the painful one - deploy a small piece of your app, test it, keep adding pieces until you hit the transition point where you begin to see the memory problem. Keep your fingers crossed that you spot something that you can work around.
reply
    Bookmark Topic Watch Topic
  • New Topic