• 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

Urgent: OutOfMemoryError in WLS 6.1 in Production mode

 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all,
We are running two web applications in an exploded directory format in WLS 6.1 in production. Quite often we are getting 'OutOfMemoryError' when we access any page in 'info' web application. For your information, I have attached log content from weblogic.log file. Could anyone please guide me in resolving this issue.

Thanks.
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I guess u need to change the JVM heap size.Check out this link
http://edocs.bea.com/wls/docs61/perform/JVMTuning.html#1104200
 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
Running in an exploded directory is a REALLY inefficient and non-performant way to run a Web app in production mode. Essentially what you are doing is forcing and calls between not only the apps but also among the war and jar files into making a remote network call and a JNDI lookup for each invocation. It doesn't matter that they are running in the same server...
By using the appropriate link tags in your jar files and bundling jars and wars together you avoid a JNDI lookup every time you need a reference.
This could be another reason you're seeing performance issues...
Cheers,
Chana
 
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi
try starting web logic server with the following options. -ms64m -mx64m . These options woluld specify a default allocation of 64 mega bites of java heap memory to the weblogic server.
 
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Chana,
How do you say, exploded format of web application reduces the performance?
Can you please give is more reasons and source?
Thanks
Lara
 
reply
    Bookmark Topic Watch Topic
  • New Topic