I am facing this same problem… I will send you the log by e-mail. ‘java -agentpath:/path/to/libjrebel64.so -jar target/app-swarm.jar’ ) requires the rebel.xml to be generated and packaged in the same jar, which can be accomplished via the IDE plugins or maven/gradle plugins. Starting the application via uberJar(e.g. ‘mvn wildfly-swarm:run -Dswarm.jvmArguments=-agentpath:/path/to/libjrebel64.so’ Starting swarm via maven plugin similarly needs the agent added under JVM arguments, for example: In IntelliJ the configuration is exactly the same, just that instead of a checkmark in configurations you have separate start buttons for start with/without JRebel. The rebel.xml(JRebel Nature) is not required in this configuration as target/classes will be included in the ClassLoader URL-s. If this did not happen or you wish to change it, you can do so via Run Configuration -> JRebel tab -> “Enable JRebel agent” If you launch it this way the JRebel plugin should prompt whether to attach the agent. In eclipse, create an Application Run-Configuration with as Main class. ![]() ![]() JRebel can be used with wildfly-swarm in all the startup configurations. ![]() ![]() JRebel should work out-of-the-box for wildfly-swarm applications.Īs the original poster did not provide details as to how he was launching the swarm application, i picked one option to demonstrate that JRebel needs to be added as any other JVM argument, such as memory options.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |