cancel
Showing results for 
Search instead for 
Did you mean: 

Hybris upgrade from 2105 to 2205

felipe_lima08
Explorer
0 Kudos

Has any configuration for jrebel changed from version 2105 to 2205?

On the 2105, Jrebel works perfectly.But, on 2205 I have error about mockit.

The project starts perfectly in version 2205 without starting Jrebel


Jrebel config

# JRebel Configuration
##################################################################
tomcat.javaoptions=-agentpath:"/home/myuser/.local/share/JetBrains/Toolbox/apps/IDEA-U/ch-0/221.5921.22.plugins/jr-ide-idea/lib/jrebel6/lib/libjrebel64.so"
tomcat.debugjavaoptions=-agentpath:"/home/myuser/.local/share/JetBrains/Toolbox/apps/IDEA-U/ch-0/221.5921.22.plugins/jr-ide-idea/lib/jrebel6/lib/libjrebel64.so" -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n
mansurarisoy
Contributor

Can you share how you activate JRebel? Configuration lines might be useful to understand the problem.

felipe_lima08
Explorer
0 Kudos

mansurarisoy , i update the question

Harish_Vatsa
Active Contributor

Hi felipelima08,

Can you please explain the steps you have taken while activating JRebel.

Thanks,

Accepted Solutions (0)

Answers (2)

Answers (2)

Harish_Vatsa
Active Contributor

While activating JRebel, please follow all the steps mentioned in SAP Help portal

felipe_lima08
Explorer

I followed the official SAP documentation to configure Jrebel

I deleted the references from OrderManagementwebservices-spring-test.xml and jrebel works. I don't know why this error occurs to me and the people in the project I'm on

0 Kudos

Hi ,

Did you get any issues related to JDK / Caused by java lang IllegalAccessException module java base does not open java lang to unnamed module 723279cf. We were experiencing this in server startup, any pointers will be appreciated.

former_member825146
Discoverer
0 Kudos

You probably have overwritten the OOTB tomcat.generaloptions in your local.properties. among other things, you are likely missing ${tomcat.jdkmodules.config} in your tomcat.generaloptions. if that's the case, then you just need to compare the ootb tomcat.generaloptions with yours and update it.