Latest posts for the topic "Not enough space"

Not enough space

karl — GMT

Hi,
I have an JAVA application which processes jobs running on a SOLARIS platform.Jobs are submitted through job submission clients.
In the case of a job processing for 24hrs duration i am getting a "java.io.IOException Not enough space".
My Jprobe reports are fine.

HELP IMMEDIATELY REQUIRED.

regards

Re:Not enough space

stdunbar — GMT

Have you increased the size of your Java heap already? This is with the -Xmx option that is passed to the Java runtime. Under the 32 bit Solaris JDK you can go to a maximum of about 1.7GB. If you are running a 64 bit Solaris O/S I don't know the actual limit but I do know that it is much, much higher. The parameter can be specified in megabytes so -Xmx1024m gives you 1GB of Java heap space.

Of course, you'll still need to have enough memory and/or swap space in the O/S to handle an increased Java heap size.

Re:Not enough space

karl — GMT

Hi,
The Xmx option you told i have kept it at 512 MB (as this is the specified limit) , so the same is maintained both on SOLARIS and WINDOWS operating systems.
Thing to be noted is that the same scenario that is pdf-pdf processing for a job works well for WINDOWS OS.No error seen here.
Please let me know if anyother solution possible.
Help immedtly required.

Re:Not enough space

stdunbar — GMT

Are you using the same JVM on both Solaris and Windows? That is, there is a client JVM and a server JVM. Under Windows the client JVM is the default. For a [url=http://java.sun.com/j2se/1.5.0/docs/guide/vm/server-class.html]certain class of machine[/url] the server JVM is the default under Solaris (2GB and 2CPU's). The server JVM takes more memory as it is expected to be on a server class machine.

Re:Not enough space

karl — GMT

My Solaris system is a 2GB and a single processor machine with a 2GB swap space.
I didnt know about the server thing you talked about.
Thanks.
So a Xmx value with 1024 and swap space 2GB works is it?

Re:Not enough space

stdunbar — GMT

[quote=karl]So a Xmx value with 1024 and swap space 2GB works is it?[/quote]

I would think that that would work but it depends on what else you have on the machine. For example, if this machine is also you database server then it might not work so well.

And just something that has caught me before. When you specify -Xmx you are actually telling the JVM the number of [b]bytes[/b] to use. I've forgotten that before and didn't understand why my JVM wouldn't even start when I said "-Xms2048". That is because I told the JVM to use 2[b]K[/b] of memory! -Xm1024m says to use 1024 megabytes - a gig.

Re:Not enough space

karl — GMT

I am not using my m/c as a database server and not for anything else also.
[color=brown]Just tell me the parameters to be tuned with exact syntax.[/color]As told earlier my [size=18]Solaris m/c is a 2GB , dual processor and Ultrasparc III i m/c with a 2GB swap space[/size].Except for the PDF-PDF processsing nothing elseworks on my m/c simultaneously.

Re:Not enough space

stdunbar — GMT

Your previous post indicates that you only have a single processor so I though that you were using the client JVM.

Pass -client and, perhaps, -Xmx1024m to the command that runs the process. If you're passing the memory argument I doubt that you need the -client but it would make it the same as Windows.

Re:Not enough space

karl — GMT

Can there be a common solution to both single processor and dual processor machine.
Anyway i am going now trying -Xmx1024m without passing the -client.
I will reply as soon i get some result.

Re:Not enough space

karl — GMT

I tried the following
1.-Xms=512m and -Xmx=1024m
2.-Xms=512m and -Xmx=1024m -client
But no luck.The Not enough space exception seen in 6 hrs time only.
Anyother solution?
I need urgent help.

Re:Not enough space

stdunbar — GMT

I really think that something else is going on. If the jars on Windows at 512M work and a gig on Solaris doesn't work then I'd think that there is some difference in either the Jars or, perhaps, shared libraries/dlls. Are there any native libraries associated with this process? Are you using the same version of Java on both platforms? Also, what version of Solaris are you on? Sparc or x86?

I've been using Java on Solaris for years and haven't had the big issues you're having. I know this has to be a pain for you.

Re:Not enough space

karl — GMT

[quote] perhaps, shared libraries/dlls. Are there any native libraries associated with this process?[/quote] ya, we are using shared libraries and dlls stuff. Also, we are using the JNI stuff to call the methods of sharedlibraries/dlls.

[quote]Are you using the same version of Java on both platforms?[/quote] ya, we are using the same version of java.

[quote]Also, what version of Solaris are you on? Sparc or x86? [/quote]t's a SPARC (Ultra Sparc IIIi)

Re:Not enough space

stdunbar — GMT

[quote=karl]It's a SPARC (Ultra Sparc IIIi)[/quote]

Yeah, you had already said that and I spaced it. What version of Solaris are you running? Is it up to date?

I feel that there is some issue with the shared libraries. As far as the O/S is concerned Java and any shared libraries it loads are part of a single process space. If they are leaking memory then it will appear that Java is leaking memory.

I've used [url=http://www-128.ibm.com/developerworks/rational/library/1499.html]Purify[/url] with a great deal of success. Admittedly this was when it wasn't a Borland product so I don't know if it is still as good as it was. But it helps with a large variety of issues in native code.

Re:Not enough space

karl — GMT

Following is my Solaris System Configuration

Number of CPU's: 1
Type : Ultra Sparc IIIi
Clock Speed: 1,280 MHz
Operating System: SunOS 5.10

Physical Memory: 2,048 MB
Virtual Memory: 3,663 MB
Virtual Memory Used: 23% , 2830 MB Available

I am using 64-bit machine.

The java environment is as follows:

Windows
----------
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)

Solaris
--------
java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-b05)
Java HotSpot(TM) Client VM (build 1.4.2_09-b05, mixed mode)

Yes I am using native libraries. Do you think the trial version of Rational Purify would help us to find any leaks in java/native code on Solaris. I am using JProbe Memory Debugger to find out leaks in java. I didn't find any leaks in java.

Re:Not enough space

stdunbar — GMT

It looks like IBM [url=http://www14.software.ibm.com/webapp/download/preconfig.jsp?id=2005-04-28+14%3A03%3A28.342185R&S_TACT=104CBW71&S_CMP=&s=]offers a trial[/url] that will run on Solaris Sparc. I'd try to run it against the entire executable, including the shared libraries.

Re:Not enough space

karl — GMT

Can you suggest me a link which would guide me how to use the rational purify plus tool to detect memory leaks effectively( an online manual type).

Re:Not enough space

karl — GMT

I tried using rational purify plus on solaris but the tool gives options to run the native libraries(.c files) individually and not attaching with my application. Testing individually is a huge overhead.
So i am not able to test the native part .
Help required.

Re:Not enough space

karl — GMT

I ran my application on another memory leak detect tool called GlancePlus but no leaks are detected.
I have some additional info. down here can you help me

Our application uses JNI calls. It works well on windows but is failing on Solaris. The Native code is third party software. I cannot suspect a memory leak as it is working well on windows. I suspect the integration of Java Native code. I have seen that temporary files are created and deleted in /tmp folder. The physical RAM is v.low when observed after this error. I think that solaris is able to use physical RAM but is failing to release memory back.

Stack trace:
-----------------
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.(Unknown Source)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at java.lang.Runtime.exec(Unknown Source)
at JobPreproc.exec(JobPreproc.java)
at JobPreproc.execPreproc(JobPreproc.java)
at JobPreproc.startAnotherPreproc(JobPreproc.java)
at JobChangeMed.tryStartPreprocWaitJob(JobChangeMed.java)
at JobObs.procJobExternalProcCompleted(JobObs.java)
at JobObs.onEvent(JobObs.java)
at EventMan.sendEventToObserver(Unknown Source)
at EventMan.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

The following are the reading taken before submitting the input to my application and after the error is seen.

Before

Physical Memory Used: 597,056 Kb
Physical Memory Free: 1,500,096 kb
Total Physical Memory: 2 GB
Active Processes: 80
Swap Used: 848,290 kb
Swap Free: 3,927,152 kb
Total Swap Space: 3 GB
Virtual Memory Used: 17%

After

Physical Memory Used: 2,048,529 Kb
Physical Memory Free: 48,624 kb
Total Physical Memory: 2 GB
Active Processes: 87
Swap Used: 2,512,696
Swap Free: 2,191,928 kb
Total Swap Space: 3 GB
Virtual Memory Used: 53%

Its an Ultra Sparc IIIi single processor machine and OS is Solaris 10.
Help me out?

Re:Not enough space

stdunbar — GMT

[quote]
I cannot suspect a memory leak as it is working well on windows.
[/quote]

[quote]
java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
[/quote]

I'm sorry, but I'm going to say it is your third party library. Why are they java.lang.Runtime.exec()'ing a process? Under Unix this can be an extremely expensive operation. The [b]entire[/b] process space is duplicated during a fork()! That means if you have a process taking 2.5GB of space you now need 5GB of space as there will be two of the exact same processes for a small amount of time - until the O/S level exec() can run.

We need more information - [b]what[/b] is the processing exec()'ing? Why can't it spawn a thread? Is it possible to change the architecture of this - perhaps a small "spawning" process that can be sent a signal somehow to start the process?

You posted this in the J2EE forum which makes me think you're running this under some sort of application server. Is this the case? I would really caution you to not try to exec() something out of an app server - they are large and it is expensive to do under Unix.

Let us know.

Re:Not enough space

karl — GMT

what is the processing exec()'ing?
It uses a third party kit to determine whether the document is color or not.

Why can't it spawn a thread? Is it possible to change the architecture of this - perhaps a small "spawning" process that can be sent a signal somehow to start the process?
Changing the architecture is not possible.

The application uses Tomcat server.

Re:Not enough space

karl — GMT

I reverted back to the old library version of the native code and it worked fine.
One observation made was the older library was maintaining some 20K files in the /tmp folder. The total size of the /tmp folder was around 50MB all the time. With the new native library the /tmp folder only a couple of files were created and deleted in few seconds.
Can anything be infered from this observation.

Re:Not enough space

karl — GMT

Before I doubted my third party library i did a small test.
I wrote a prog. which creates a files writes some data into it and deletes the file in /tmp folder.I ran the prog. in a loop for 1 hr.
When i compared the memory statistics before and after the run I found that Solaris had consumed around 50MB space and not released back as the files created were deleted.The physical and vitual memory spaces were consumed and not released.
I am doubting that the Solaris is not able to release the memory?
Any solution...

Re:Not enough space

karl — GMT

Atlast we could drill down the problem to the third party libraries.
Thanks a lot for your valuable suggestions all the way.

Re:Not enough space

stdunbar — GMT

That is fantastic! Glad you got it working.

Re:Not enough space

sps — GMT

Can you please share the solution for this problem.I am facing the same. Using Tomcat5.5 and jsp. Running parallel perl scripts from Java using invoking using Runtime.exec(path to perlscript)