Error while Activating DC

[Former Member]

Hi,

After creating an external library dc and the corresponding usage dc, when I am check-in and Activate the activity, I get the following erro.

Please help.

Regards,

Shubham

Build number assigned: 9

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "Tst_APPL_D" at Node ID: 7,652,950

[id: 8; parentID: 0; type: 4]

[options: NO OPTIONS]

REQUEST PROCESSING started at 2005-12-05 05:39:50.374 GMT

===== Pre-Processing =====

List of activities to be activated:

1 activity in compartment "com.diagonal_APPLICATION_1"

ApacheUtilities

[seq. no 8][created by ADMINISTRATOR at 2005-12-05 13:39:29.0][ID 25e3e097654911da909300123f12ac1c]

Analyse activities... started at 2005-12-05 05:39:51.525 GMT

Synchronizing component "apache.org/util/jars" from repository... finished at 2005-12-05 05:39:57.150 GMT and took 5 s 144 ms

Component "apache.org/util/jars" is to be CHANGED by this activation.

1 component to be build in compartment "com.diagonal_APPLICATION_1"

Analyse activities... finished at 2005-12-05 05:39:57.580 GMT and took 6 s 55 ms

Calculate all combinations of components and variants to be built...

"apache.org/util/jars" variant "default"

Prepare build environment in the file system... started at 2005-12-05 05:39:58.121 GMT

Synchronize development configuration... finished at 2005-12-05 05:39:58.551 GMT and took 430 ms

Synchronize component definitions... finished at 2005-12-05 05:39:58.561 GMT and took 10 ms

Synchronize sources...

Synchronize sources... finished at 2005-12-05 05:39:58.901 GMT and took 340 ms

Synchronize used libraries...

Synchronize used libraries... finished at 2005-12-05 05:40:32.478 GMT and took 33 s 577 ms

Prepare build environment in the file system... finished at 2005-12-05 05:40:32.478 GMT and took 34 s 357 ms

===== Pre-Processing ===== finished at 2005-12-05 05:40:32.478 GMT and took 41 s 443 ms

===== Processing =====

BUILD DCs

"apache.org/util/jars" in variant "default"

WARNING: The build process will be forcibly terminated as it has not completed execution even after 60 minute/s.

.. FAILURE: The build was terminated as it exceeded the configured build-timeout value [result code: 501]

===== Processing ===== finished at 2005-12-05 06:41:08.918 GMT and took 60 m 36 s 330 ms

===== Post-Processing =====

Check whether build was successful for all required variants...

"apache.org/util/jars" in variant "default" FAILED

===== Post-Processing ===== finished at 2005-12-05 06:41:17.020 GMT and took 140 ms

Change request state from PROCESSING to FAILED

ERROR! The following problem(s) occurred during request processing:

ERROR! The following error occurred during request processing:Activation FAILED due to build problems. See build logs for details.

REQUEST PROCESSING finished at 2005-12-05 06:41:17.030 GMT and took 61 m 26 s 656 ms

[htammen · Accepted solution]

Hi Shubham,

is this the first activation? If yes, you´re CBS service may be misconfigured.

You can check it here:

http:///tc.CBS.Appl/properties

It should look similar to this:

rootFolder                 ./temp/CBS 
JDK_HOME_PATHS             JDK1.4.2_HOME=C:j2sdk1.4.2_06; 
idleStart                  false 
cleanUpRequestFolders      true 
AdminTaskDelay             5000 
notifyTCS                  true 
BUILD_TOOL_JDK_HOME        C:j2sdk1.4.2_06 
tcsQueueCheckDelay         10000 
BUILD_TOOL_VM_ARGS         -Xmx768M 
threadPoolSize             1 
useClassicSync             true 

More details can be found at:

http://help.sap.com/saphelp_nw04/helpdata/de/31/9959400d9d1059e10000000a155106/frameset.htm

If it is configured correctly please show us the content of the build log which you can find at:

http:///webdynpro/dispatcher/sap.com/tc.CBS.WebUI/WebUI

under "Requests" search the request with id:8, click at request results in the lower table and then the link in the column "Build Log File".

Regards

Helmut

[Former Member · Accepted solution]

Hi Helmut,

I have already checked help.sap.com link.

Here is the CBS properties.

rootFolder ./temp/CBS

JDK_HOME_PATHS JDK1.3.1_HOME=C:\j2sdk1.4.2_07;

idleStart false

cleanUpRequestFolders true

AdminTaskDelay 5000

notifyTCS true

BUILD_TOOL_JDK_HOME C:\j2sdk1.4.2_07

tcsQueueCheckDelay 10000

BUILD_TOOL_VM_ARGS -Xmx1000M

threadPoolSize 3

useClassicSync true

The build log I have already posted. Anyway its again here.

CBS Request Log - [ 8/Tst_APPL_D ]

lt03574 SAP Component Build Server

Build number assigned: 9

Change request state from QUEUED to PROCESSING

ACTIVATION request in Build Space "Tst_APPL_D" at Node ID: 7,652,950

[id: 8; parentID: 0; type: 4]

[options: NO OPTIONS]

REQUEST PROCESSING started at 2005-12-05 05:39:50.374 GMT

===== Pre-Processing =====

List of activities to be activated:

1 activity in compartment "com.diagonal_APPLICATION_1"

ApacheUtilities

[seq. no 8][created by ADMINISTRATOR at 2005-12-05 13:39:29.0][ID 25e3e097654911da909300123f12ac1c]

Analyse activities... started at 2005-12-05 05:39:51.525 GMT

Synchronizing component "apache.org/util/jars" from repository... finished at 2005-12-05 05:39:57.150 GMT and took 5 s 144 ms

Component "apache.org/util/jars" is to be CHANGED by this activation.

1 component to be build in compartment "com.diagonal_APPLICATION_1"

Analyse activities... finished at 2005-12-05 05:39:57.580 GMT and took 6 s 55 ms

Calculate all combinations of components and variants to be built...

"apache.org/util/jars" variant "default"

Prepare build environment in the file system... started at 2005-12-05 05:39:58.121 GMT

Synchronize development configuration... finished at 2005-12-05 05:39:58.551 GMT and took 430 ms

Synchronize component definitions... finished at 2005-12-05 05:39:58.561 GMT and took 10 ms

Synchronize sources...

Synchronize sources... finished at 2005-12-05 05:39:58.901 GMT and took 340 ms

Synchronize used libraries...

Synchronize used libraries... finished at 2005-12-05 05:40:32.478 GMT and took 33 s 577 ms

Prepare build environment in the file system... finished at 2005-12-05 05:40:32.478 GMT and took 34 s 357 ms

===== Pre-Processing ===== finished at 2005-12-05 05:40:32.478 GMT and took 41 s 443 ms

===== Processing =====

BUILD DCs

"apache.org/util/jars" in variant "default"

WARNING: The build process will be forcibly terminated as it has not completed execution even after 60 minute/s.

.. FAILURE: The build was terminated as it exceeded the configured build-timeout value [result code: 501]

===== Processing ===== finished at 2005-12-05 06:41:08.918 GMT and took 60 m 36 s 330 ms

===== Post-Processing =====

Check whether build was successful for all required variants...

"apache.org/util/jars" in variant "default" FAILED

===== Post-Processing ===== finished at 2005-12-05 06:41:17.020 GMT and took 140 ms

Change request state from PROCESSING to FAILED

ERROR! The following problem(s) occurred during request processing:

ERROR! The following error occurred during request processing:Activation FAILED due to build problems. See build logs for details.

REQUEST PROCESSING finished at 2005-12-05 06:41:17.030 GMT and took 61 m 26 s 656 ms

Regards,

Shubham

[Former Member · Accepted solution]

Hi Helmut,

When I activate a Request, and check the same in the Request DCs Tab, I see the following.

The SC Name is 'Error'? Can this be a reason for faliure?

Also is it required to create all the 'dc name' in the SLD first before creating the same?

Name Imported SC Name Vendor

js/jars Error apache.org

js/lib Error diagonal.com

We don't have any namespace in the Service Marketplace.

When I look at the DTR Log, I see a lot of these warnings.

Message : can't process name reservation queue since no name server is configured

Date : 12/06/2005

Time : 9:54:17:518

Category : /Applications/DTR/BackgroundTasks

Message ID : 00123F12AC1C00560000000100000CD400040737503C9A2F

Severity : Warning

Location : com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager

Source Name : /Applications/DTR/BackgroundTasks

Thread : Thread[Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask#0_workerThread#0,1,Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask#0]

Message : can't process name reservation queue since no name server is configured

Datasource : 7652950:C:\usr\sap\J2E\JC00\j2ee\cluster\server0\sap.com\tc_dtrenterpriseapp\dtr.log

Application : sap.com/tc_dtrenterpriseapp

Argument Objs :

Arguments :

Dsr Component :

Dsr Transaction : 35d32e4065fb11da884600123f12ac1c

Dsr User :

Indent : 0

Level : 0

Message Code :

Message Type : 0

Relatives : com.tssap.dtr.server.deltav.nameres.impl.NameReservationManager

Resource Bundlename :

Session : 2

Source : /Applications/DTR/BackgroundTasks

ThreadObject : Thread[Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask#0_workerThread#0,1,Scheduler_com.tssap.dtr.server.deltav.nameres.ProcessNameReservationsTask#0]

Transaction :

User : Guest

Can this be some problem?

Regards,

Shubham

[Former Member · Accepted solution]

You have:

JDK_HOME_PATHS JDK<b>1.3.1</b>_HOME=C:\j2sdk1.4.2_07;

While Helmut's list states

JDK_HOME_PATHS JDK<b>1.4.2</b>_HOME=C:\j2sdk1.4.2_07;

[htammen · Accepted solution]

Hi Shubham,

1. SC Name

This could be a reason for the error. Which SC did you define in SLD and import into your track?

I remember that I also had this error once but unfortunately I don´t remember how I fixed it and if it caused any errors.

2. Name reservation

You don´t have to register a namespace at service marketplace to use the name service of SLD.

3. DTR waring message

This does not lead to an error in the build process. It just means that you didn´t configure a name server in DTR yet.

This can be done under

http:///dtr/system-tools/administration/NameServerConfiguration

4. JDK_HOME

As far as I know the fact that you defined JDK1.3.1_HOME in spite of JDK1.4.2_HOME does not lead to an error but should nevertheless change it.

Regards

Helmut

[Former Member · Accepted solution]

Hi,

just some additional info:

Situation: CBS executes the request, but the build is terminated after an hour. The only DC that is built is an external library DC. Right?

1. SC Name: No, it's irrelevant. The SC name may be relevant for ACL checks and for packaging SDAs, but for an external library DC it is not really used.

3. When the build is really executed at that stage then CBS already downloaded all sources from DTR.

4. Those keys are rather obsolete but the documentation is not really up-to-date. Those keys are only evaluated if a) the Java compiler runs as part of the build and b) the build-option "com.sap.jdk.

home_path_key" is specified in the Track configuration (see http://help.sap.com/saphelp_nw04s/helpdata/en/bd/cddf4164ee6024e10000000a1550b0/frameset.htm if the option is not set the build will simply use the running VM, i.e. that one configured as BUILD_TOOL_JDK_HOME or you can define a "default" JDK in the JDK_HOME_PATHS list).

To analyse this issue I'd turn off "cleanUpRequestFolders", trigger a build and then look into the CBS rootFolder to see what is there. Maybe the Build VM crashes or freezes for some unknown reason and that folder may contain helpful information.

Regards,

Marc

[Former Member]

The build timeout is configurable.

Below is how to configure it: just add a service property and value

BUILD_TIMEOUT = N [min]

[Former Member]

Hi Jason,

I'd still analyse why that timeout is reached at all. In the original case an external library was affected, but then why would copying a few megabytes of Jar files in the file system take an hour? That sounds like some severe bottleneck on the server somewhere.

Even heavy Web Dynpro components (like some travel expense stuff in ESS) should build within one hour.

Regards,

Marc

[Former Member]

You guys are over analyzing this. The error is becase the build is taking too long and the timeout value needs to be increased:

"<i>FAILURE: The build was terminated as it exceeded the configured build-timeout value [result code: 501]</i>"

I have the same problem but can't find this value to increase in the settings, does anyone know where it is?