NWDI, ESS import fails

Hi,

I am trying to import .sca file in CMS, after 22 hours i was able to import into CMS. In between I got couple of times communication error.

After that, I got problem in CBS. I tried import again and it started to import into CBS.

But after couple of times, it started import into CMS, I believe whatever I imported into CMS is gone.

Right now I am back to pavilion, I am trying to import it again, I am getting communication error.

Any help appreciated.

Our envrionment: NWDI is installed on Unix.

Regards,

Balu

SAP Managed Tags:
NW Java Development Infrastructure (NWDI)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (7)

Our problem got resolved by increasing the event timeout parameter in the server0->Kernel->ServiceManager.

saved it and restarted the j2ee engine and deployed the ESS component again. It worked !!

thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Balu,

There can be two things in guess...

1. Check if your CBS service is active and on

2. Seems from your log, your CBS is locked by any other request.

To check that goto CBS -> Requests -> Open Requests and search it will specify what activities are open.

You can cancel that activity and try back.

The above two points i gave were based on my experience. They worked for me.

If works, do close the threads and also do post your response on how did u solved it.

Regards,

Santosh.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

I have two hints for you:

- get better HW: 22 hours for an ESS import is way too much (properly setup, 2-3 hours are ok)

- get someone who knows how to configure a NWDI

Best regards,

Timo

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

try to check your CBS config:

http://help.sap.com/saphelp_nw2004s/helpdata/en/b5/7a5e4088dc0272e10000000a155106/frameset.htm

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Balu & Gopal,

I am having same issue . I checked with CBS Authorizations and everything looks fine. Could you please tell me resolution for this issue.?

Thanks & Regards

Srinivas

Hi Guys,

The following worked for me -

1. Checkin all open activities

2. Delete the track

3. recreate the track. Make sure you use all the same names for the Track ID and Name.

there will be no loss of content as the DTR workspace is not deleted when a track is deleted.

thanks,

Sri

Balu,

Did u solve this issue.

I am also getting the same issue.

The ESS import is failing in CBS-make with the same message. Appreciate if you can post the solution if you did find one.

regards

Sam

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

In the logs I can see

Error:CBS error on setting mode (to open): 
caused by:User not authorized.

Check the CMS user on the landscape configurator has the appropiate permissions.

Please feel free to reward points if this solves your problem.

Best regards,

Homer Vargas

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi Balu,

Please post the error log.

Regards,

Shubham

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi,

Right now I am able to finish importing into CMS, now import is failed at CBS import, Please see the following error. Now the state is Import running. But in the details tab it shows import failed in CBS-make.

Thanks,

Balu

Info:Starting Step CBS-make at 2006-09-13 15:45:18.0628 -7:00

Info:wait until CBS queue of buildspace DI1_XSSSP6_D is completely processed, before starting the import

Info:waiting for CBS queue activity

Info:buildspace = DI1_XSSSP6_D build request id = 48

Info:wait until CBS queue of buildspace DI1_XSSSP6_D is completely processed, before asking for build results

Info:waiting for CBS queue activity

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

Error:CBS error on retrieving open build requests

caused by:Read timed out (Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out)

com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:

java.net.SocketTimeoutException: Read timed out)

at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:530)

at com.sap.cms.tcs.client.CBSCommunicator.getOpenBuildRequests(CBSCommunicator.java:1166)

at com.sap.cms.tcs.client.CBSCommunicator.isThereQueueActivity(CBSCommunicator.java:1546)

at com.sap.cms.tcs.client.CBSCommunicator.getBuildResult(CBSCommunicator.java:883)

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

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

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)

Caused by:

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

java.net.SocketTimeoutException: Read timed out

at com.sap.tc.cbs.wsproxy.CBSHttpSOAPBindingStub.getOpenRequests(CBSHttpSOAPBindingStub.java:1800)

at sun.reflect.GeneratedMethodAccessor378.invoke(Unknown Source)

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

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

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

at $Proxy120.getOpenRequests(Unknown Source)

at com.sap.tc.cbs.client.impl.BuildSpace.listOpenRequests(BuildSpace.java:527)