cancel
Showing results for 
Search instead for 
Did you mean: 

CBS Exception during activation: No space left on device

Former Member
0 Kudos

Hi,

I modified some of the standard SAP ESS web dynpro java codes(bank, personal data) and have successfully deployed them onto the dev server. After testing them on dev, I have checked in and activated my activities from NWDS. The activation view has a green tick mark, so it can be considered that the build is successful.But in the CBS I can see that there are 27 dirty Dcs, broken Dcs 165 and failed requests: 1186. The CBS itself is creating requests of type INTERNAL_BUILD and their staus is FAILED. Also the DCs are broken and hence not processed successfully.

When I see the CBS request log: it shows the exception chain as:

com.sap.tc.cbs.common.types.InternalErrorException: No space left on device (errno:28)

at com.sap.tc.cbs.api.impl.RequestState.getRequestLog(RequestState.java:658)

at com.sap.tc.cbs.receiver.ArchiveServlet.getRequestLog(ArchiveServlet.java:1174)

at com.sap.tc.cbs.receiver.ArchiveServlet.doGet(ArchiveServlet.java:138)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Caused by: java.io.IOException: No space left on device (errno:28)

at java.io.FileOutputStream.writeBytes(Native Method)

at java.io.FileOutputStream.write(FileOutputStream.java:260)

at com.sap.tc.cbs.util.Util.writeStreamToStream(Util.java:323)

at com.sap.tc.cbs.api.impl.DBIOHelper.retrieveBinary(DBIOHelper.java:383)

at com.sap.tc.cbs.api.impl.BSState.getArchive(BSState.java:1216)

at com.sap.tc.cbs.api.impl.BSState.getArchive(BSState.java:1250)

at com.sap.tc.cbs.api.impl.RequestState.getRequestLog(RequestState.java:655)

... 20 more

Caused by:

java.io.IOException: No space left on device (errno:28)

at java.io.FileOutputStream.writeBytes(Native Method)

at java.io.FileOutputStream.write(FileOutputStream.java:260)

at com.sap.tc.cbs.util.Util.writeStreamToStream(Util.java:323)

at com.sap.tc.cbs.api.impl.DBIOHelper.retrieveBinary(DBIOHelper.java:383)

at com.sap.tc.cbs.api.impl.BSState.getArchive(BSState.java:1216)

at com.sap.tc.cbs.api.impl.BSState.getArchive(BSState.java:1250)

at com.sap.tc.cbs.api.impl.RequestState.getRequestLog(RequestState.java:655)

at com.sap.tc.cbs.receiver.ArchiveServlet.getRequestLog(ArchiveServlet.java:1174)

at com.sap.tc.cbs.receiver.ArchiveServlet.doGet(ArchiveServlet.java:138)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

And now from NWDS also , I am unable to activate requests, it shoes the same error log as above.

Can anybody suggest which server parameter needs to be reset for the disk space error?

Any help in this direction is appreciated.

Thanks.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Check the space on the NWDI server, while cbs builds the ESS it might ran out of space.clear some space and try again, it should work.

Thanks,

pkv

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

This issue is resolved now.

The problem was with the file system space on the Unix server(on which portal is installed).

The server administrators and the Basis team extended the disk space and issue got resolved.

Thanks for all your inputs.

Sonali.

Former Member
0 Kudos

Duplicate post.

Former Member
0 Kudos

HI,

IN Visual Admn.

Dispatcher->Services->HTTP Provider->Properties,

increase the value of 'maximunrequestcontentlength' and

click on update.

Regards,

Satya.

Former Member
0 Kudos

Thanks Satya and PKV for your immediate response.

Satya can you please confirm what should be the max value which should en changed in teh VA parameter as told by you.

Thanks,

Sonali.

Former Member
0 Kudos

HI,

the maximum permitted value is 131072 KB (or 128MB)

Regards,

Satya.