Error on accessing the Webdynpro DC - SAP Community

Hi All,

The web dynpro development component is throwing error as soon as we run it. It was working fine till yesterday and suddenly it has started giving the error. We are not able to execute any of the Web dynpro development components.

Error is : java.lang.UnsupportedClassVersionError: com/xxx/wssapp/billingdetails/wdp/InternalBillingDetailsComp (Unsupported major.minor version 49.0)

I've browsed few of the SDN forums for this issue but did not get a clear idea of the root cause.

We are on NWDS 7.01 and using JDK 1.4 for compiling the source code.

Kindly assist.

PS: Not sure if any of the server settings has been modified.

Thanks & Regards,

Anurag

SAP Managed Tags:
UI Web Dynpro Java

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 (1)

Answers (1)

1.check at the server side to see if any new deployment is made

2.if there is any new deployment, ask who made it and check the jdk used to build the project, make sure it is jdk1.4..

are you using nwdi? how about other wd application?

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

Comment

Hi John,

1.check at the server side to see if any new deployment is made : I only do the deployment and I am using JDK 1.4 only to build the components.

I've been deploying this component for the past 6 months and this is the first time that I've faced such an issue.

2.if there is any new deployment, ask who made it and check the jdk used to build the project, make sure it is jdk1.4. : I am using JDK 1.4 only.

Yes, I am using NWDI and the issue exists for all the WD components.

Please assist.

Best Regards,

Anurag

are the nwdi used to do the deployment?

how you make sure you are using JDK1.4?

Hi John,

Yes, I am using JDK 1.4 only.

are the nwdi used to do the deployment? : I am sorry but I did not understand this question. Can you please explain me a bit more?

I do deployment from my NWDS by configuring the J2ee engine details and using SDM.

Best Regards,

Anurag

nwdi can trigger the deployment to target server if you configured the runtime system for the track.

at your local, you have only jdk1.4 installed?

Okay, I got your point.

Yes, We are using NWDI as well for the deployment to the target server.

But the issue is that I deploy my component on the dev server by using SDM through NWDS and for building the WD DC I am using JDK 1.4 only but still when I try to run the WD DC in dev environment, it gives an error.

The error that I've mentioned is appearing on the dev environment.

Before dev server we used to use another local server for development.

I am able to run the WD DC there successfully but not on the dev server.

We have not migrated all the components to Quality and we cannot test there.

But it works fine on the local server but does not work on the remote dev server.

There may be a possibilty that the n/w team might have modified something at the OS level which has impacted some sort of setting but they are not sure about that.

Moreover, it used to work fine earlier since the dev server was configured(almost a month back).

This has started appearing suddenly which is why I feel that some of the dev server setting has ben disturbed.

But I am not sure how to troubleshoot this issue and what to check exactly on the dev server to fix this issue.

I hope that I am clear to explain the issue.

Best Regards,

Anurag

1. check what jdk is used in nwdi and dev server?

2. check the error if it caused by nwdi deployment or your local deployment

you only have jdk1.4 at your local?

Hi John,

I have only jdk1.4 at my local machine though not sure about the JDK at the local server.

I will ask my Basis team to let us know the JDK version installed in the Dev server and the NWDI server.

I think that this might be the issue.

The issue is certainly with the local deployment because of the dev server but going forward it could be with NWDI deployment as well if there is the JDK version mismatch in the other environments also.

Will let you know the outcome.

Best Regards,

Anurag

you can check the jdk at the system info page.

Hi John,

We are using JDK 1.4.2_17 on the dev server and using j2sdk1.4.2_02 in my system for compiling the WD code.

Could it be the issue?

As per our Basis team, the JDK setting has not been modified and it is the same from the past 1 month when our dev server came into picture.

And if that is the case, why are we facing ths issues now and not since then?

PS: We are on EP 7.01.

Best Regards,

Anurag

http://sourceforge.net/projects/jclasslib/

using this tool to check the class generated in the deploy-able archive.

major version should be 48 if the class is generated jdk 1.4

Hi John,

I've downloaded the tool.

Can you please confirm by the class generated in the deploy-able archive, are you referring to the EAR file in the deply folder in the workspace?

If not, please specify the file to be analysed.

Thanks for the help so far!!!

Best Regards,

Anurag

yes, just grab one class file from the ear.

Hi John,

When I select the EAR file in the ByteCode viewer, it does not show any class for selection in the "Classes in selected jar file".

Do I need to pick some other file instead of the EAR file?

Please suggest.

Best Regards,

Anurag

buddy, you really drive me crazy..................

extract the ear and grab one class file....................................

Hi John,

Sorry for the late reply!!!

I checked few of the classes generated in the deploy-able archive file and noticed the below observations:

Minor Version: 0

Major Version: 46

As I've already mentioned, we are on NWDS 7.01 and using j2sdk1.4.2_02 for compiling the WD DC before deploying it on the dev server through SDM.

Please suggest if this setting is fine from our end.

Also, please suggest if something has to be checked at the server level.

Best Regards,

Anurag

server should be ok, if not, all application should not be able to run.

again, MAKE SURE YOU ARE USING JDK1.4.*

do you know which jdk is used:)

Hi John,

None of the Web Dynpro DC's are running.

On the server, we have JDK 1.4.2_17 version.

and in NWDS I use JDK 1.4.2_02 version.

Now, please tell me is these things fine?

Also, what should be the JRE version to be used on the server?

If there are multiple JDK's on the server, would it create issues?

Please suggest as I am really stuck with this.

Best Regards,

Anurag

have you checked the sap wd application? like ume.

in most case, the error is caused by your local compilation.

DO YOU REALLY KNOW YOU ARE USING JDK1.4* TO COMPILE YOUR CODE?

Hi John,

Yes, I am able to run the UME application(sap wd application) in the portal.

The issue is only with the WD Java DCs.

I really wonder, if the issue is with the local compilation. why it did not appear for so long as I've been using the same JDK in my classpath for the past 6 months.

So, since my classpath indicates 1.4, I feel that I am using JDK 1,4 only.

Best Regards,

Anurag

Hi All,

The problem is resolved now.

The issue was with the JDK of the NWDI. Since no other build variant was available, it was using JDK 1.5 which was available there to build the code.

Special thanks to John for all the help!!!

Best Regards,

Anurag

Ask a Question

Top Q&A Solution Author

User

Count

86

10

10

9

7

7

6

5

4

4