Win a copy of 97 Things Every Java Programmer Should Know this week in the Java in General forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Jeanne Boyarsky
  • Junilu Lacar
  • Henry Wong
Sheriffs:
  • Ron McLeod
  • Devaka Cooray
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Frits Walraven
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • salvin francis
  • fred rosenberger

Increasing memory for the webservice

 
Ranch Hand
Posts: 48
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I have a java webservice, running on websphere4.0, which runs out of memory very frequently. Please advice as to what I can do to rectify the situation. I'm very new to webservice. If this is not the correct forum for this question then please move it to some place relevant.

Thanks
Nitin
 
Ranch Hand
Posts: 341
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I think the question belongs to Web services, SOAP ... forum but I do not think I am authorized to move this question to that thread.

First, I wish your question were little clearer; "which runs out of memory very frequently..." What runs out of memory? WAS? your code? What do you get out of memory error?

There are many reasons why this might happen:
[1] Your machine does not have enough RAM. WAS 4.0 recommends 512 MB I believe. If you are using windows, go Start > All programs > Accessories > System Tools > System Information
[2] You did not allocate enough memory to JVM. There is way to allocate memory to WAS. You have to specify some command line arguments to increase the memory it uses. Do some research on how to set this.
[3] Your code consumes a lot of memory quickly enough that the garbage collector cannot reclaim the memory.

It might help if you could post the stack trace here.
 
Bring me the box labeled "thinking cap" ... and then read this tiny ad:
Devious Experiments for a Truly Passive Greenhouse!
https://www.kickstarter.com/projects/paulwheaton/greenhouse-1
    Bookmark Topic Watch Topic
  • New Topic