Error while upgrading to Java 1.8 : Expecting a stackmap frame [message #1778590] |
Mon, 18 December 2017 05:50  |
Eclipse User |
|
|
|
Hi there,
thanks Eclipse Virgo 3.7.2, I'm currently in the java 1.8 migration process. Unfortunately I'm now blocked by following issue :
[2017-12-18 11:20:38.681] ERROR iLogServiceListener@38e374ff org.osgi.service.log.LogService Bundle net.echinopsii.ariane.community.core.idm.base_0.4.6.SNAPSHOT, [ERROR] net.echinopsii.ariane.community.core.idm.base.proxy.iPojo.IDMJPAProviderImpl : Expecting a stackmap frame at branch target 12
Exception Details:
Location:
net/echinopsii/ariane/community/core/idm/base/proxy/iPojo/IDMJPAProviderImpl.start()V @4: ifne
Reason:
Expected stackmap frame at this location.
Bytecode:
0x0000000: 2ab4 0239 9a00 082a b702 3cb1 2ab4 0028
0x0000010: 2a13 023d 03bd 0004 b600 bf2a b702 3c2a
0x0000020: b400 282a 1302 3d01 b600 c2a7 0012 4d2a
0x0000030: b400 282a 1302 3d2c b600 c62c bfb1
Exception Handler Table:
bci [12, 43] => handler: 46
This issue is coming when I'm using a java 1.8 compiled net.echinopsii.ariane.community.core.idm library (https://github.com/echinopsii/net.echinopsii.ariane.community.core.idm) against Virgo 3.7 + JRE 1.8.0_144. I've no issue when using same library compiled with Java 1.7.
Googling this error, I found the -noverify option could help, but unfortunately it dont help me solve the issue after adding it in the dmk.sh file. So now I'm diging my dependencies one by one to get the root cause of this issue.
Meanwhile I was thinking about the reason why the -noverify option workaround was not working in my context and I would like to know if it's not because I should push this option in the OSGi classloader configuration level instead than pushing this configuration in JRE executing Virgo level ?
Anyway if you have any tips to help me accelerate this issue troubleshoot I'll be very interested.
Kind regards,
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02765 seconds