Skip to Content
avatar image
Former Member

Standard ESS SCA import failed with auto-restart of J2EE Engine

Hi,

we are configuring NWDI for customizing ESS components. ESS version is SAP_ESS 600 SP4 and the WebAS version is EP7.01 SP03. While importing the SAP_ESS components in CMS, Input Mode for buildspace is set to PRIVILEGED automatically in CBS and the server gets restarted repeatedly. Import is failed and the ,CBS-make' error log shows the following:

20100927175845 Info :Starting Step CBS-make at 2010-09-27 17:58:45.0416 +4:00

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

20100927175847 Info :CBS queue of buildspace P10_XSSTRK00_C is completely processed. Starting the import now.

20100927192800 Fatal :CBS throws exception during activation:

20100927192800 Fatal :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc"):Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc")

com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is:

com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc")

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

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

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

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)

Thanks in advance

Regards

Arindam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Best Answer
    avatar image
    Former Member
    Sep 29, 2010 at 05:58 AM

    Hi Ervin,

    Understood the problem. In my ESS track I have only one RTS defined and that is Dev (declared the same host as NWDI and dev portal resides in the same host).

    Now I have two system only left Q system and P system in my landscape (no sandbox).

    If I remove the Dev RTS from my track and keep it blank..and Declare the Test RTS as AQ and Prod RTS as P system..will it be fine? I will manually deploy code from NWDS for Dev portal.

    Again while importing the sca in the Development system of the track (I had Dev RTS declared as the host of Dev portal), I kept the checkbox 'Disable Automatic Deployment' because there was some manual code changes already deployed oin Dev portal so did not want to disturb that. Because of that lot of request are showing in Queued status in TCS servlet. I thought I wil do replicate all modifications done in the track and then finally deploy all code to Dev portal using TCS servlet.

    If now I remove the Dev RTS from track , what will happen to those Queued requests in TCS servlet.. will it be a problem?

    After removing the RTS, do I need to do a 'restore System State' in Dev and Cons system of the track?

    I know, there are lot of questions in my mind!!..pls help ...and many thanks

    regards

    Arindam

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      yes, that is also fine. Deploying to DEV system or to CONS has basically the advantage that you can catch runtime errors in a pretty early state of the development cycle. But if you have simply no further resources, then I'd say, let's do it as you also mentioned.

      I send you couple of documents also about track design you may welcome:

      Best Practices: Track design for ongoing development

      /people/marion.schlotte/blog/2006/03/30/best-practices-for-nwdi-track-design-for-ongoing-development

      See some further explanation in the forum:

      SAP Netweaver CE 7.1 Ehp1 SP5 & multiple SAP release version support

      You can also check the master guide at

      https://websmp206.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000718025&

      See also some explanation about this guide inside the forum:

      NWDI Landscape Design

      Regarding the questions:

      - Requests which are already Queued will be deployed even if you remove the RTS config. If not, you can still trigger deployment using the TCS Deploy servlet.

      - There's no need to trigger "restore system state". You usually use this feature if you do a major change on the track config, like reorganizing SCs, therefore these must be imported again into the buildspaces of dev/cons, or you update the NWDI_CMSADM password, etc.

      I hope this answers your questions.

      Best Regards,

      Ervin

  • Sep 28, 2010 at 08:46 AM

    Hi,

    the fact that when you start the import, the buildspace mode automatically changes to PRIVILEGED, is normal, means only that the buildspace is reserved for request processing. But it is not normal if your engine gets restarted during the import.

    ...

    Fatal :CBS throws exception during activation: 20100927192800 Fatal :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Invalid Response Code: (-1) null. The requested URL was:"http://dc1depdv:50000/CBSWebService/CBSHttpSOAP?style=rpc" (Service call exception; nested exception is: com.sap.engine.services.webservices.jaxrpc.exceptions.InvalidResponseCodeException:

    ...

    Still, the error message you have provided means that the CBS isn't running properly, could you please try the following:

    1. restart the whole j2ee engine where CBS is running.

    2. then please go to check CBS web UI -> BuildSpace, then click the Edit button by selecting the buildspace in question.

    If the parameter "Input Mode" is not being set to "OPEN", please change it to OPEN and click the Save button.

    3. finally please try the import again

    If the engine is still restarted at the CBS make step of the import, then I believe it is worth to check the following settings:

    0. Is your system meeting the requirements?

    Check SAP note #737368 - Hardware requirements of Java Development Infrastructure (http://service.sap.com/sap/support/notes/737368)

    1. doublecheck whether you can see any outofmemory error in the defaultTrace, if yes, check the SAP note

    #723909 -- Java VM settings for J2EE 6.40/7.0 (http://service.sap.com/sap/support/notes/723909)

    2. If you still face the problem, then please notice the time when the engine got restarted, and check these time related entries in the following log files:

    -\usr\sap\...\j2ee\cluster\server<n>\log\applications\cms.<n>.log

    -\usr\sap\...\j2ee\cluster\server \ sap.com\tc dtrenterpriseapp\dtr.<n>.log

    -\usr\sap\...\j2ee\cluster\server<n>\log\services\tc.CBS.Service\cbs.<n>.log

    -\usr\sap\...\j2ee\cluster\server<n>\log\defaultTrace.<n>.trc

    -\usr\sap\...\j2ee\cluster\server<n>\log\sysyem\database.<n>.log

    I hope this helps.

    Best Regards,

    Ervin

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 28, 2010 at 05:16 PM

    Hi Ervin,

    Thanks a tonne for your valuable help!! That surely helps..I will investigate the logs..

    One thing I want to inform you I have my NWDI system and Dev Portal running on the same J2EE Engine..

    If the standard SCA needs an engine restart while deployment..will there be problem because of my NWDI system will also be restarted?

    I have my Dev Portal declared as the Dev Runtime system in the track also.

    Regards

    Arindam

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Arindam,

      I am glad to hear if these tips are helping.

      One addition, you mentioned that the NWDI and the dev runtime system is basically one and the same j2ee instance.

      Please notice that we are not supporting this scenario, if possible please use a separate engine as runtime system, else you can do it only for test purposes and we cannot provide you support, see the note:

      http://service.sap.com/sap/support/notes/754143

      Excerpt from the note:

      "Do not use CMS server as a runtime system:

      Do not use the J2EE Engine, on which the CMS is running, as a runtime system. When you import software components that have offline deployment portions, deployment causes a deadlock. In other words, the CMS is shut down by the import that it is supposed to check."

      Best Regards, 😉

      Ervin