Import SCA files in Development Tab of the Transport Studio take more time

[Former Member]

Hi,

After Check-In files in the Transport Studio, the import of SCA files starts in the development Tab of the Transport Studio.

The import takes more time. Why this happens?

Am I missing any configuration? Please specify in detail.

Thanks in Advance,

Sathya

[Former Member]

Login to J2EE Engine - Visual Administrator

Navigate to Global Configuration Tab and then to Server tab.

Expand Services and Select "Component Build Service"

Properties of CBS:

-

---

idleStart = true changed to false.

JDK_HOME_PATHS = JDK1.3.1_HOME=?;

j2sdk1.4.2_13_HOME=C:\j2sdk1.4.2_13;

Save & Restart.

Thanks for everyone. Thanks alot.

[Former Member]

SC: sap.com_SAP-JEE:

-

---

SDM-deploy

-

---

Returncode : Not executed.

How to check the username, password and url for SDM?

Log file of Repository-import:

-

---

Info:Starting Step Repository-import at 2009-10-13 22:15:49.0484 +5:00

Info:Component:sap.com/SAP_JTECHS

Info:Version :SAP AG.20060119105400

Info:3. PR is of type TCSSoftwareComponent

Info:Component:sap.com/SAP_BUILDT

Info:Version :SAP AG.20060411165600

Info:2. PR is of type TCSSoftwareComponent

Info:Component:sap.com/SAP-JEE

Info:Version :SAP AG.20060119105300

Info:1. PR is of type TCSSoftwareComponent

Info:Step Repository-import ended with result 'not needed' at 2009-10-13 22:15:49.0500 +5:00

Log File of CBS-make :

-

---

Import got failed.

Info:build process already running: waiting for another period of 30000 ms

Info:no changes on the CBS request queue (DM0_DEMObp1_D) 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:There seems to be a structural problem in the NWDI. 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. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. 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. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.

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

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

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

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

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

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

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

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

at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1736)

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

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

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

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

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

at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)

at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)

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

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

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

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

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

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

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)

at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)

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 2009-10-14 02:16:28.0296 +5:00

[junwu]

hi Sathya,

it is expected so. just be patient.

Best regards,

John

[Former Member]

If the State changed from "Waiting for import" to " import running" state in the development tab of the Transport Studio.

What needs to be done to complete the import state?

[junwu]

Nothing but wait:)

[Former Member]

Hi,

The process is running for more than 10 hours. How long will it take to complete.

Actually whats happening in this process? Please explain.

The IE got disturbed and now the state is "import failed". What is need to do? Please guide.

Regards,

Sathya