Skip to Content
author's profile photo Former Member
Former Member

(ess)cms track import in development getting faiiled

Hi friends,

Iam trying to import ess track(cms track) into development after running to 6-7 hrs it failed and got error message like

20111202230421 Info :no changes on the CBS request queue (XSSTrack_D) after a waiting time of 14430000 ms

20111202230421 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

20111202230421 Fatal :Please look after the operational status of the CBS.

20111202230422 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2011-12-02 23:04:22.0800 +5:00

our basis team dont have much knowledge about nwdi.so i need to solve it.

pls give some idea.

Regards,

Edited by: babanmohi on Dec 3, 2011 7:11 AM

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Dec 03, 2011 at 06:26 AM

    Hi,

    please check that yiour CBS Service is actually running (in VA) and that idlestart is set to false

    Hope this helps.

    Regards,

    Deepak Kori

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 05, 2011 at 04:29 PM

    Hi,

    1. Check if the activities are queued in httP://<hostname>:<portno>/TCS/Deployer

    2. Trigger the deployment manually for the buildspace.

    3. Check if CBS service is running in Visual Admin.

    Hope this helps.

    Cheers-

    Pramod

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 09, 2011 at 09:27 AM

    Actually we have two portals(ie., 1 and 2)and nwdi is installed on 1 and i want make changes to ess of 2 portal,so iam using 1's nwdi to make changes so i hav given the info of 2's portal in runtime system of 1's portal,is it right way?i was able to import SAP_JTECHS,SAP_BUILDT,SAP-JEE,but iam not able to import SAP_ESS file into development, and the error is

    20111209141527 Fatal :more details on this error:

    20111209141527 Fatal :caused by Exception:java.rmi.RemoteException: Service call exception; nested exception is:

    java.net.SocketTimeoutException: Read timed out:Service call exception; nested exception is:

    java.net.SocketTimeoutException: Read timed out

    java.rmi.RemoteException: Service call exception; nested exception is:

    java.net.SocketTimeoutException: Read timed out

    at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.activate(CBSHttpSOAPBindingStub.java:226)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:331)

    at com.sap.tc.cbs.client.impl.BuildServer$1.invoke(BuildServer.java:528)

    at $Proxy196.activate(Unknown Source)

    at com.sap.tc.cbs.client.impl.BuildSpace.activate(BuildSpace.java:790)

    at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:414)

    at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:223)

    at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:495)

    at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)

    at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:206)

    at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:447)

    at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:176)

    at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:500)

    at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:113)

    at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:648)

    at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:620)

    at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0_0.startImport(LocalCmsTransportProxyLocalObjectImpl0_0.java:678)

    at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1429)

    at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2817)

    at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:957)

    at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2866)

    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:335)

    at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)

    at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:319)

    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:713)

    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:666)

    at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:250)

    at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:149)

    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: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.net.SocketTimeoutException: Read timed out

    at java.net.SocketInputStream.socketRead0(Native Method)

    at java.net.SocketInputStream.read(SocketInputStream.java:129)

    at java.io.BufferedInputStream.fill(BufferedInputStream.java:183)

    at java.io.BufferedInputStream.read(BufferedInputStream.java:201)

    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.readLine(HTTPSocket.java:890)

    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getInputStream(HTTPSocket.java:375)

    at com.sap.engine.services.webservices.jaxm.soap.HTTPSocket.getResponseCode(HTTPSocket.java:284)

    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.HTTPTransport.getResponseCode(HTTPTransport.java:415)

    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.outputMessage(MimeHttpBinding.java:553)

    at com.sap.engine.services.webservices.jaxrpc.wsdl2java.soapbinding.MimeHttpBinding.call(MimeHttpBinding.java:1464)

    at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.activate(CBSHttpSOAPBindingStub.java:219)

    ... 52 more

    20111209141529 Info :Step CBS-make ended with result 'fatal error' ,stopping execution at 2011-12-09 14:15:29.0666 +5:00

    i followed the inputs of both deepak and pramod ,

    Regards

    Edited by: babanmohi on Dec 9, 2011 10:27 AM

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.