问启动SAP hybris服务器时出现的Jrebel问题

EN

tomcat.javaoptions=-Xverify:none -javaagent:"C:/jrebel/jrebel.jar=de.hybris.tomcat.HybrisWebappClassLoader60"

tomcat.debugjavaoptions=-Xverify:none -javaagent:"C:/jrebel/jrebel.jar=de.hybris.tomcat.HybrisWebappClassLoader60" -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8000,suspend=n

tomcat.generaloptions=-Xmx1024M -XX:MaxPermSize=8G -ea -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=${tomcat.jmx.port} -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -Dorg.tanukisoftware.wrapper.WrapperManager.mbean=true -Djava.endorsed.dirs="%CATALINA_HOME%/lib/endorsed" -Dcatalina.base=%CATALINA_BASE% -Dcatalina.home=%CATALINA_HOME% -Dfile.encoding=UTF-8 -Dlog4j.configuration=log4j_init_tomcat.properties -Djava.util.logging.config.file=jdk_logging.properties -Djava.io.tmpdir="${HYBRIS_TEMP_DIR}" -Drebel.log=trace

Launching a JVM...

Listening for transport dt_socket at address: 8000

To run with JRebel Agent, use: -agentpath:C:\jrebel\lib\jrebel64.dll

For more information, please read https://zeroturnaround.com/software/jrebel/jrebel7-agent-upgrade-cli/

JRebel Agent is building a bootclass cache to C:\WORK\hybris\temp\hybris\rebelboot.jar

Check the instructions above to start using JRebel. The JVM will now exit.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=8G; support was removed in 8.0


JVM exited while loading the application.

Reloading Wrapper configuration...

Launching a JVM...

Listening for transport dt_socket at address: 8000

To run with JRebel Agent, use: -agentpath:C:\jrebel\lib\jrebel64.dll

For more information, please read https://zeroturnaround.com/software/jrebel/jrebel7-agent-upgrade-cli/

JRebel Agent is building a bootclass cache to C:\WORK\hybris\temp\hybris\rebelboot.jar

Check the instructions above to start using JRebel. The JVM will now exit.

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=8G; support was removed in 8.0

JVM exited while loading the application.

There were 5 failed launches in a row, each lasting less than 300 seconds.  Giving up.

  There may be a configuration problem: please check the logs.

<-- Wrapper Stopped