| java heap | Out of memory | jobs api [message #330514] |
Wed, 30 July 2008 18:57  |
Eclipse User |
|
|
|
Originally posted by: prasad.chand.gmail.com
Hi all,
I am facing a problem running a background job (using the jobs api). The
code in the job's run method accesses code to which I don't have source
access (They are corba-related class files included in a jar file).
Problem is in one of the methods I am getting a "java heap - out of
memory" error. I decompiled the classes using jad and I found that the
error occurs at the following spot
ResultDocument resultdocument = new ResultDocument();
resultdocument.szBreakPoint = inputstream.read_string();
err-> resultdocument.szOutputDocument = inputstream.read_string();
return resultdocument;
These class files are not generic but is there any specific reason why
we get an out of memory error in jobs api. what are the possible fixes?
Any help will be greatly appreciated.
Thanks,
Prasad
|
|
|
| Re: java heap | Out of memory | jobs api [message #330764 is a reply to message #330514] |
Tue, 12 August 2008 16:13  |
| Eclipse User |
|
|
|
Originally posted by: eclipseng.arthorne.com
There is nothing inherent about jobs that consume a large amount of
memory. They spawn a threads, which consume heap space, but the likely
cause is that you have several memory-intensive things going on
concurrently, which is using up all the memory. If you are doing a large
number of concurrent jobs you may want to reduce the number of jobs you
schedule at once. Otherwise, you can also increase the Java heap using
arguments such as -Xmx to the VM.
--
Prasad Chand wrote:
> Hi all,
>
>
> I am facing a problem running a background job (using the jobs api). The
> code in the job's run method accesses code to which I don't have source
> access (They are corba-related class files included in a jar file).
> Problem is in one of the methods I am getting a "java heap - out of
> memory" error. I decompiled the classes using jad and I found that the
> error occurs at the following spot
>
> ResultDocument resultdocument = new ResultDocument();
> resultdocument.szBreakPoint = inputstream.read_string();
> err-> resultdocument.szOutputDocument = inputstream.read_string();
> return resultdocument;
>
> These class files are not generic but is there any specific reason why
> we get an out of memory error in jobs api. what are the possible fixes?
>
> Any help will be greatly appreciated.
>
> Thanks,
> Prasad
|
|
|
Powered by
FUDForum. Page generated in 0.03570 seconds
] 
Search
Help
Register
Login
Home
