Dear all,
We are facing a big issue with NWDI/JDI transports because of which we are unable to transport any request into the consolidation system.
After the developer is releasing a request from NWDS,when and we start importing the request to the consolidation system, the request takes around 3 4 hrs to get processed and after this it says: Import Failed. Before releasing the request I already checked that the buildspace is not in the PRIVELAGE mode, it was in open mode at the time of import.
But when i imported the request for the first time, i got an error which said psaptemp file system full and it took around 5 hrs for the request to get cancelled. Since then we have 2 dirty DCs & as well as 2 failed requests in the CBS. The tablespace size was increased and when I started to transport again, i still get this big error. This was all working fine till yesterday & there were no dirty DCs we got the first error.
The error which we are getting after the transport fails is as follows:
Info:Starting Step CBS-make at 2007-05-09 23:26:26.0855 +2:00
Info:wait until CBS queue of buildspace JDI_TSHOP_C is completely processed, before starting the import
Info:waiting for CBS queue activity
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
Info:build process already running: waiting for another period of 30000 ms
...
Info:no changes on the CBS request queue (JDI_TSHOP_C) after a waiting time of 14430000 ms
Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
Fatal:Please look after the operational status of the CBS.
Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.
com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. Please look after the operational status of the CBS.
at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:370)
at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:197)
at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:227)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:634)
at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:103)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:584)
at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:560)
at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1146)
at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1307)
at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2215)
at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:881)
at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2390)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:330)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:707)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:661)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:229)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
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:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2007-05-10 03:27:46.0534 +2:00
-
Can someone please help us out with this issue. how to remove the dirty dcs etc. There are no broken DC as of now but we do have 2 dirty dcs as i told.
Will surely reward points if I get the solution.
Thanks.
Warm Regards,
Rajeet
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.