cancel
Showing results for 
Search instead for 
Did you mean: 

CBS - Building - Error with JDK6

Former Member
0 Kudos

Hi Experts.

This will probably the last time I am posting a threat, because I have almost finished my NWDI-Project.

I would like to deploy a simple "HelloWorld" JSP on SAP NetWeaver Portal 7.3.

But I do net want to deploy directly by the NWDS (by setting up a AS Server Java in the Preferences), but over the services of the NWDI (CBS ....).

First of all, I would like to give you an overview about my Systems and Landscape:

- NWDI 7.01 SP 7 => JDK 1.6.0_21

- NWDS 7.3 SP05 => JDK 1.6.0_? (not sure if correct installed, drop down for more info)

- Deploy/Runtime - System: SAP NetWeaver Portal 7.3 => JDK 1.6.0_? (correcty installed and it works)

I would like to give you a overview in this threat, what I did until now:

1. Installing JDK 1.6.0? on NWDI-System_

If I go in the NetWeaver Administrator (to the CBS-Service), I can se the following entry:

Name: JDK_HOME_PATHS

Wert: default=/usr/java14_64;JDK1.5_HOME=/usr/java5_64;JDK1.6_HOME=/sapmnt/XXX/global/sapjvm_6;

Name: BUILD_TOOL_JDK_HOME

Wert: -


(nothing, my SAP-BASIS sayed, that is right)

2. Generating a TRACK in the CMS - Landscape Configurator

- TRACK-Name: PORTAL73

- SCs: JSP7.3 => Dependencies to: ENGFACADE 7.30 and SAP_BUILDT 7.30

- Build Variants: Add -> Name: JDK6; New Build Option: Name: com.sap.jdk.home_path_key & Value: JDK1.6_HOME

JDK6 -> Assign Scs -> JSP7.3 -> Add

- Build Variants: Default -> Edit -> New Build Option: Name: com.sap.jdk.home_path_key & Value: JDK1.6_HOME

Default -> Assign Scs -> JSP7.3 -> Add

=> Checking-in the 2 SCs in the TRACK: ENGFACADE 7.30 and SAP_BUILDT 7.30

=> Checking-in the 2 SCs in the Development-System: ENGFACADE 7.30 and SAP_BUILDT 7.30

3. Working in the NWDS 7.30

- Import Development Configuration - File for Development-System

- Creating a simple "HelloWorld" JSP (with 2 DCs: Web Module & Enterprise Application)

- Local Build => SUCCESSFUL

=> Checking-In the Activity into DTR (successful)

=> Activating the Activity in the CBS

Now: After Activating in the CBS I got a "Request ID"

- I looked in the CBS -> Requests -> Request Status -> FAILED

So can you tell me please, what I did wrong?

Did I forget something?

Usually, after activating the activity in the CBS, I could call up my JSP in the Browser, by the following ULR, IS IT RIGHT:

http://<host>:<port>/contextRoot/portal.jsp

Thank you very much helping.

Best regards.

Accepted Solutions (1)

Accepted Solutions (1)

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Maximilian,

for the record, at the moment you are proceeding as per the note:

#1523989 - DC Build failed in CBS with java.lang.UnsupportedClassVersionError Unsupported major.minor

Regards,

Ervin

Former Member
0 Kudos

Hi Ervin.

Thank you very much for helping.

For all the others:

To solve this questions, please have a look at:

SAP Note - 1523989

You have to set the Parameters for

- BUILDT_TOOL_JDK_HOME (has to point to the folder of the highest-available installed JDK)

- JDK_HOME_PATTHS (all available JDKs have to be listed, also the default-JDK)

Best Regards

Former Member
0 Kudos

This note is not released.  How do I get access to this note?

ErvinSzolke
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi,

it seems that the note is going to be archived, but I am sure this link can help you:

http://help.sap.com/saphelp_nwce72/helpdata/en/45/d3a608ffa25709e10000000a114a6b/frameset.htm

and I also think that one of my SCN Threads can sheds some light on all this, please have a look at:

http://scn.sap.com/docs/DOC-25855 -->

See here the links

http://scn.sap.com/thread/2079515  and

http://scn.sap.com/thread/1775010

I hope this helps.

Best Regards,

Ervin

Answers (1)

Answers (1)

Former Member
0 Kudos

And there you have to LOG-File of the CBS:

Build number assigned: 144

Change request state from QUEUED to PROCESSING

REQUEST PROCESSING started at 2011-11-24 08:48:57.679 GMT

ACTIVATION request in Build Space "XXX_PORTAL73_D" at Node ID: 458,444,350

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

[options: NO OPTIONS]

Waiting for access: 11 ms

===== Pre-Processing ===== started at 2011-11-24 08:48:57.691 GMT

List of requested for activation activities:

'xxx.xxxx.xx_JSP-7.3_1' compartment

Activity for TRACK: PORTAL73

[ISN 6][created by XXXXXXXX at 2011-11-24 09:48:07.0][OID cd019e97167411e1cda000001a82216a]

There is 1 activity in compartment xxx.xxxx.xx_JSP-7.3_1

1 activity will be processed by this request

Analyze dependencies to predecessor activities... started at 2011-11-24 08:48:57.765 GMT

Analyzing predecessors in compartment "xxx.xxxx.xx_JSP-7.3_1"

No dependencies to predecessor activities found.

Analyze dependencies to predecessor activities... finished at 2011-11-24 08:48:57.770 GMT and took 5 ms

Analyze versions... started at 2011-11-24 08:48:57.770 GMT

List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2011-11-24 08:48:58.224 GMT and took 453 ms

Resource "/SCs/xxx.xxxx.xx/JSP-7.3/_comp/TopLevelDCs/xxx.xxxx.xx test jsp ear.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/xxx.xxxx.xx/JSP-7.3/_comp/TopLevelDCs/xxx.xxxx.xx test jsp ear.dcref'. URL does not point to DCs root directory.

Resource "/SCs/xxx.xxxx.xx/JSP-7.3/_comp/TopLevelDCs/xxx.xxxx.xx test jsp web.dcref" is not relevant for DC build and will be ignored. Reason: Invalid DC URL '/SCs/xxx.xxxx.xx/JSP-7.3/_comp/TopLevelDCs/xxx.xxxx.xx test jsp web.dcref'. URL does not point to DCs root directory.

Synchronize metadata for [xxx.xxxx.xx/test/jsp/ear] started at 2011-11-24 08:48:58.360 GMT

Verification of DL [ws/PORTAL73/xxx.xxxx.xx_JSP-7.3/dev/active/] finished at 2011-11-24 08:48:58.438 GMT and took 15 ms

Verification of cache (level 2: Comparison of attributes) finished at 2011-11-24 08:48:58.462 GMT and took 23 ms

Synchronize metadata for [xxx.xxxx.xx/test/jsp/ear] finished at 2011-11-24 08:48:58.464 GMT and took 104 ms

< CREATE > 'xxx.xxxx.xx/test/jsp/ear' DC

Synchronize metadata for [xxx.xxxx.xx/test/jsp/web] started at 2011-11-24 08:48:58.533 GMT

Verification of DL [ws/PORTAL73/xxx.xxxx.xx_JSP-7.3/dev/active/] finished at 2011-11-24 08:48:58.574 GMT and took 16 ms

Verification of cache (level 2: Comparison of attributes) finished at 2011-11-24 08:48:58.597 GMT and took 23 ms

Synchronize metadata for [xxx.xxxx.xx/test/jsp/web] finished at 2011-11-24 08:48:58.599 GMT and took 66 ms

< CREATE > 'xxx.xxxx.xx/test/jsp/web' DC

Analyze versions... finished at 2011-11-24 08:48:58.601 GMT and took 831 ms

Analyze activities... started at 2011-11-24 08:48:58.601 GMT

Loading component definitions

2 components to be build in compartment "xxx.xxxx.xx_JSP-7.3_1"

Analyze activities... finished at 2011-11-24 08:48:58.665 GMT and took 64 ms

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

Analyze request DC BV... started at 2011-11-24 08:48:58.696 GMT

'xxx.xxxx.xx/test/jsp/ear' variant 'JDK6'

'xxx.xxxx.xx/test/jsp/web' variant 'JDK6'

'xxx.xxxx.xx/test/jsp/ear' variant 'default'

'xxx.xxxx.xx/test/jsp/web' variant 'default'

Analyze request DC BV... finished at 2011-11-24 08:48:59.156 GMT and took 460 ms

Prepare build environment in the file system... started at 2011-11-24 08:48:59.156 GMT

Synchronize development configuration... started at 2011-11-24 08:48:59.156 GMT

Synchronize development configuration... finished at 2011-11-24 08:48:59.175 GMT and took 19 ms

Synchronize sources for [xxx.xxxx.xx/test/jsp/ear] started at 2011-11-24 08:48:59.196 GMT

Verification of DL [ws/PORTAL73/xxx.xxxx.xx_JSP-7.3/dev/active/] finished at 2011-11-24 08:48:59.234 GMT and took 15 ms

Verification of cache (level 2: Comparison of attributes) finished at 2011-11-24 08:48:59.266 GMT and took 32 ms

Synchronize sources for [xxx.xxxx.xx/test/jsp/ear] finished at 2011-11-24 08:48:59.268 GMT and took 72 ms

Synchronize sources for [xxx.xxxx.xx/test/jsp/web] started at 2011-11-24 08:48:59.290 GMT

Verification of DL [ws/PORTAL73/xxx.xxxx.xx_JSP-7.3/dev/active/] finished at 2011-11-24 08:48:59.339 GMT and took 16 ms

Verification of cache (level 2: Comparison of attributes) finished at 2011-11-24 08:48:59.411 GMT and took 72 ms

Synchronize sources for [xxx.xxxx.xx/test/jsp/web] finished at 2011-11-24 08:48:59.416 GMT and took 126 ms

Synchronize used libraries... started at 2011-11-24 08:48:59.498 GMT

PP 'war' of DC xxx.xxxx.xx/test/jsp/web' [DCID=404] (in SC 'xxx.xxxx.xx_JSP-7.3_1' [SCID=141]) ... OK

PP 'api' of DC 'sap.com/engine.jee5.facade' [DCID=286] (in SC 'sap.com_ENGFACADE_1' [SCID=139]) ... OK

PP 'war' of DC 'xxx.xxxx.xx/test/jsp/web' [DCID=404] (in SC 'xxx.xxxx.xx_JSP-7.3_1' [SCID=141]) ... OK

PP 'api' of DC 'sap.com/engine.jee5.facade' [DCID=286] (in SC 'sap.com_ENGFACADE_1' [SCID=139]) ... OK

Synchronize used libraries... finished at 2011-11-24 08:49:43.267 GMT and took 43 s 769 ms

Prepare build environment in the file system... finished at 2011-11-24 08:49:43.268 GMT and took 44 s 112 ms

===== Pre-Processing ===== finished at 2011-11-24 08:49:43.269 GMT and took 45 s 578 ms

Waiting for access: 17 ms

===== Processing ===== started at 2011-11-24 08:49:43.286 GMT

The java class could not be loaded. java.lang.UnsupportedClassVersionError: com/sap/tc/buildcontroller/CBSBuildController (Unsupported major.minor version 49.0)

BUILD DCs

'xxx.xxxx.xx/test/jsp/web' in variant 'default'

The java class could not be loaded. java.lang.UnsupportedClassVersionError: com/sap/tc/buildcontroller/CBSBuildController (Unsupported major.minor version 49.0)

Build failed! Unknown error

Change request state from PROCESSING to FAILED

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

Error! The following error occurred during request processing:build controller process has terminated. cannot proceed with build

Error! build controller process has terminated. cannot proceed with build

REQUEST PROCESSING finished at 2011-11-24 08:49:49.766 GMT and took 52 s 87 ms