NWDI Build Problems / CBS Error Analysis

[Former Member]

Hello,

I'm trying to track down the source of my difficulties to compile a self-services DC. In the DTR perspective, NWDS is unable to sync archives for used DCs. The obvious error is that the DCs are not deployed in the CMS/CBS systems. However, the web-interface for the CMS shows required SCs deployed in the Dev and Con tabs. The web-interface for the CBS shows the requisite buildspaces and compartments with zero broken or dirty DCs.

The reference guide of the NWDI mentioned a CBS Command Line Tool. There is a value called u201Coutputlocku201D which restricts the downloading of archives from the CBS. I have explicitly turned off that value. While using the cbstool_nw.bat included with NWDS the following behavior is encountered:

1.) connect works as expected

2.) listbuildspaces lists the expected buildspaces (for instance: SLP_XSSMOD_D)

3.) listcompartments (listcompartments -b SLP_XSSMOD_D) encounters a strange error

Error while accessing build space u2018SLP_XSSMOD_Du2019
Build Server request failed without CBS specific error code. HTTP status: 500 (Internal Server Error)

Could this be indicative of the root problem? The CBS appears to be moderately working; if I input an invalid buildspace, then an error is encountered (as expected):

Error while accessing build space u2018abc123u2019
CBS Server Error: The build space is not known on the server (internal code: BS_UNKNOWN)

Any advice is greatly appreciated. Please let me know what other information is pertinent.

Thank you,

Zach

[Former Member]

I suggest you have a look at the server logs (defaultTrace, etc.). Those will probably indicate what causes the internal server error.

[Former Member]

I suggest you have a look at the server logs (defaultTrace, etc.). Those will probably indicate what causes the internal server error.

[Former Member]

I suggest you have a look at the server logs (defaultTrace, etc.). Those will probably indicate what causes the internal server error.

[Former Member]

Pascal,

Thank you for the continued help. Here is the error as recorded by the defaultTrace in the SLD server. Every time I try to 'listcompartments' in thecbstool_nw.bat, this error occurs:

#
#1.5#001A64282330005B000049A00003E0B600047A37725AB7D7#1260278467180#com.sap.engine.services.servlets_\
Jsp.server.HttpHandlerImpl#sap.com/tc.CBS.Appl#com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl#NWDI_\
ADM#72760##n/a##8af417d0e3fc11de8aa5001a64282330#SAPEngine_Application_Thread[impl:3]_31##0#0#Error#1\
#/System/Server/WebRequests#Plain###application [tc.CBS.Appl] Processing HTTP request to servlet [archiveapi\
] finished with error.
The error is: java.lang.NoSuchMethodError: com/sap/tc/cbs/util/Util.writeStreamToStream(Ljava/io/InputStream;\
Ljava/io/OutputStream;)V
Exception id: [001A64282330005B0000499E0003E0B600047A37725AB63F]#

Is this class a part of EBUILT, JEE, or JTECHS? If so, I will ask to again deploy the required SCs to Dev and Con.

Thank you,

Zach

[Former Member]

Here is more of the error. I had to break it up due to restrictions on the forumsu2026

The error is: java.lang.NoSuchMethodError: com/sap/tc/cbs/util/Util.writeStreamToStream(Ljava/io/InputStream;Ljava/io/OutputStream;)V
                at com.sap.tc.cbs.api.impl.DBIOHelper.retrieveBuildspaceConfiguration(DBIOHelper.java:234)
                at com.sap.tc.cbs.api.impl.BSState.getConfig(BSState.java:176)
                at com.sap.tc.cbs.receiver.ArchiveServlet.getBSConfig(ArchiveServlet.java:1489)
                at com.sap.tc.cbs.receiver.ArchiveServlet.dispatchRequest(ArchiveServlet.java:1522)
                at com.sap.tc.cbs.receiver.ArchiveServlet.doPost(ArchiveServlet.java:143)
                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(AccessController.java:219)
                at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:102)
                at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

[Former Member]

This looks like CBS is not deployed correctly (it's missing classes). Ask your administrator to redeploy the SCA's containing CBS.

[Former Member]

Are you alluding to DI_CBS? I will ask the basis staff to confirm its deployment on the SLD (also running the CBS/CMS). If it is showing up in the System Information page, should I have it redeployed via SDM?

Thank you,

Zach

Edited by: Zachary Shay on Dec 8, 2009 4:25 PM

[Former Member]

The version/SP you require depends on your installation. Search for 'component build server' in http://service.sap.com/swdc --> Support Packages.

[Former Member]

Community,

This issue has been resolved. These are the steps taken for resolution:

1.) Syncu2019ing archives in NWDS failed

2.) Because of 1.), I tried using the CBS commandline tool. This also failed; however, the commandline tool gave a specific error message. It referenced a NoSuchMethodError when executing the command listcompartments.

3.) Because of 2.), tail u2013f in conjunction with usage let me know that the DBIOHelper class was trying to use a utility function u201Cthat did not existu201D.

4.) Note 136002 gave instructions to find use the telnet administrator and LLR command to determine the application for a given class.

5.) Open the u201Csystem informationu201D page and look for the application determined in 4.). Take note of the Software Component that includes the applications.

The DI_CBS component was on level 12. The SAP_JTECHF component was on level 16. This was a problem because the function writeStreamToStream is declared as public static void in level 12, but is declared as public static int in level 16. Once the basis staff upgraded everything to level 16, CBS worked as desired. Once the CBS was able to provide NWDS the used DCs, the build process went smoothly.

Thank you for the help,

Zach