Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Cloud/Virtualization forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

URGENT:Not enough space problem

 
Siddalinga Murthy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
I am facing a problem while uploading a jsp to the document root and accessing it from browser.
I tried to put a new jsp in the document root directory and tried to get it in the browser
It gave the following error
/site/tms-weblogic/weblogic/myserver/classfiles/jsp_servlet/_FirstJsp.java failed: java.io.IOException: Not enough space
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:62)
at java.lang.Runtime.execInternal(Native Method)
at java.lang.Runtime.execInternal(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at java.lang.Runtime.exec(Compiled Code)
at weblogic.utils.Executable.exec(Compiled Code)
at weblogic.utils.Executable.exec(Compiled Code)
at weblogic.utils.compiler.CompilerInvoker.compileMaybeExit(Compiled Code)
at weblogic.utils.compiler.CompilerInvoker.compile(Compiled Code)
at weblogic.servlet.jsp.JspStub.compilePage(Compiled Code)
at weblogic.servlet.jsp.JspStub.prepareServlet(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.getServlet(Compiled Code)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextImpl.invokeServlet(Compiled Code)
at weblogic.servlet.internal.ServletContextManager.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.invokeServlet(Compiled Code)
at weblogic.socket.MuxableSocketHTTP.execute(Compiled Code)
at weblogic.kernel.ExecuteThread.run(Compiled Code)
I have enough space in hard disc as well as in RAM
Can anybody help me out.
One more thing i am doing it in solaris
 
Madhav Lakkapragada
Ranch Hand
Posts: 5040
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

I don't think your browser cache is equal to RAM.
ummm...did you try clearing the Cache?
I would try this, then quit all the
Browser windows and restart the Browser.
regds.
- satya
 
Siddalinga Murthy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi madhav
This error is not coming iun the browser
This error is displayed in the log file of the weblogic server.
In the browseer it doesn't display anything.It says page cannot displayed
 
Naveen Kuppili
Greenhorn
Posts: 24
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Siddalinga Murthy:
Hi madhav
This error is not coming iun the browser
This error is displayed in the log file of the weblogic server.
In the browseer it doesn't display anything.It says page cannot displayed

You can run truss on the process and check out whats wrong. But, it looks like a genuine I/O error to me. Are there any mounts that your appserver is using which are full? Try doing a "df -k" and check out if any mounts are near 100% utilization.
--------------
Regards,
Naveen Kuppili
Software Architect
 
Siddalinga Murthy
Greenhorn
Posts: 10
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanx naveen,
Actually i looked at that but the swap spaae is also good enough.
Now its actually solved by increasing the number of processes in the solaris system.
I changed that and restarted the server.Now its working fine
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic