Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM throws "Version number may be negative or greater than 255" while upgrading to JDK jdk1.8.0_261

Avatar

Avatar
Level 1
ranjeet_jha
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile

Avatar
Level 1
ranjeet_jha
Level 1

Likes

0 likes

Total Posts

1 post

Correct Reply

0 solutions
View profile
ranjeet_jha
Level 1

24-01-2021

We are getting the below error after updating java from jdk1.8.0_241 to jdk1.8.0_261 for AEM 6.3 as well as 6.5.

However, If we are using jdk1.8.0_241 everything was working fine. Only issues with jdk1.8.0_261. Please let us know how to fix the below issue.

 

om.adobe.livecycle.assembler.client.ProcessingException: ALC-ASM-S00-002: Failed to execute the DDX - error messages provided.
at com.adobe.livecycle.assembler.AssemblerServiceImpl.makeResult(AssemblerServiceImpl.java:928)
at com.adobe.livecycle.assembler.AssemblerServiceImpl.execute(AssemblerServiceImpl.java:518)
at com.adobe.livecycle.assembler.AssemblerServiceImpl.invoke(AssemblerServiceImpl.java:462)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
Truncated. see log file for complete stacktrace
Caused By: java.lang.ExceptionInInitializerError
at com.adobe.agl.text.Collator.<clinit>(Collator.java:946)
at com.adobe.internal.ddxm.ddx.CollateralManager.filterXDPDocsListBySourceMatch(CollateralManager.java:2107)
at com.adobe.internal.ddxm.ddx.CollateralManager.getOrderedURLXDPDocsList(CollateralManager.java:1967)
at com.adobe.internal.ddxm.ddx.CollateralManager.getOrderedXDPSourceDocsList(CollateralManager.java:1861)
at com.adobe.internal.ddxm.ddx.xfa.XDPSource.getOrderedInputDocs(XDPSource.java:617)
Truncated. see log file for complete stacktrace
Caused By: java.lang.IllegalArgumentException: Invalid version number: Version number may be negative or greater than 255
at com.adobe.agl.util.VersionInfo.getInstance(VersionInfo.java:191)
at com.adobe.agl.impl.ICUDebug.getInstanceLenient(ICUDebug.java:65)
at com.adobe.agl.impl.ICUDebug.<clinit>(ICUDebug.java:69)
at com.adobe.agl.text.Collator.<clinit>(Collator.java:946)
at com.adobe.internal.ddxm.ddx.CollateralManager.filterXDPDocsListBySourceMatch(CollateralManager.java:2107)
Truncated. see log file for complete stacktrace

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Affirm 25
Employee
PulkitJain
Employee

Likes

69 likes

Total Posts

70 posts

Correct Reply

33 solutions
Top badges earned
Affirm 25
Boost 50
Give Back 10
Establish
Boost 25
View profile

Avatar
Affirm 25
Employee
PulkitJain
Employee

Likes

69 likes

Total Posts

70 posts

Correct Reply

33 solutions
Top badges earned
Affirm 25
Boost 50
Give Back 10
Establish
Boost 25
View profile
PulkitJain
Employee

25-03-2021

This issue was fixed with AEM Forms 6.5.7.0 and 6.4.8.3 (an internal aglj40 jar was updated)

Please upgrade to the latest to receive the fix.

Answers (2)

Answers (2)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,113 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,113 likes

Total Posts

3,145 posts

Correct Reply

1,072 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

26-01-2021

Please check with Adobe support. That's an issue which I think can be fixed only by Adobe.

Avatar

Avatar
Springboard
Level 7
KiranVedantam1992
Level 7

Likes

174 likes

Total Posts

183 posts

Correct Reply

55 solutions
Top badges earned
Springboard
Give Back 5
Ignite 1
Affirm 50
Validate 1
View profile

Avatar
Springboard
Level 7
KiranVedantam1992
Level 7

Likes

174 likes

Total Posts

183 posts

Correct Reply

55 solutions
Top badges earned
Springboard
Give Back 5
Ignite 1
Affirm 50
Validate 1
View profile
KiranVedantam1992
Level 7

24-01-2021

Hi @ranjeet_jha,

 

You need to do two things here:

  • Review the "java.version" system property.
  • Check the dependency [it might be ICU4J] version, upgrade it to the latest one.

Hope it helps.

 

Thanks,

Kiran Vedantam.