• 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
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

JVM size on websphere

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

I am using IBM websphere version 5.1.2. I am currently working on a project in which Websphere is used. I created a module in which data is very large; about 1-2 lakhs records are there. So there was a memory dump problem.
How can I increase the size of JVM in Websphere or if somebody has better suggestion, then please tell me.

Regards,
Vaibhav Goel
 
Greenhorn
Posts: 5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The easiest way to increase the JVM size of the app server in 5.1 is via the admin console.

Expand the Servers tree and click on Application Servers. In the app servers list, click on your app server name. Under additional properties, click on Process Definition. On the next screen, click on Java Virtual Machine. On the next screen, you can change the initial heap size and maximum heap size. Make sure to press Save.

Fyi, this is for WAS 6.1, but provides some useful memory analysis discussion: http://www.ibm.com/developerworks/websphere/library/techarticles/0706_sun/0706_sun.html
 
author and cow tipper
Posts: 5009
1
Hibernate Spring Tomcat Server
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Indeed, configuring the Java Heap Size for WebSphere via the admin console is the best way to go. Bump that memory size up good, but not excessively.

Memory dumps can be very misleading in WebSphere and the Portal. It's not always a lack of memory, or memory suffocation. There are many seemingly innocuous problems that will trigger a Java Heap Dump.

Good luck!

-Cameron McKenzie
 
Yeah. What he said. Totally. Wait. What? Sorry, I was looking at this tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic