Hi,
The issue you are seeing should be fixed in our latest JRebel plugin nightly build that can be downloaded from “here”:https://zeroturnaround.com/software/jrebel/download/nightly-build/.
Let me know if you are still experiencing the issue after using the nightly build.
Still waiting for this feature!!!
Oh… there it is! No one told me but you added it. yay
Hi Valerie. Or rebel staff.
Is emailing support and creating a forum post still the best way to submit a jrebel feature?
The JRebel Console in IntelliJ is pretty non-useful at this point.
You should make the ability to display the changes events from the jrebel.log file. Such as:
2018-01-31 00:27:48.094 INFO [47] [IntelliJFSNotify] Event 'CREATE' on: '/home/ndipiazza/myproject/web/out/production/classes/myclass.class'
That would be super helpful instead of just wasting space.
IT’S AWESOME!!!! TOTAL GAME CHANGER!
Hey,
Thanks for letting us know. I quickly tried setting up a project with similar dependencies but wasn’t able to reproduce the issue just yet. Do you happen to have a small repro app which you could send?
If not, please start Payara with the following additional VM argument ‘-Drebel.log=trace‘ and reproduce the issue once more. This will generate a detailed log to {user.home}/.jrebel/jrebel.log.
Please send this log (or repro app) to support@zeroturnaround.com, that’ll speed up our debugging process. Anyway, I’ll continue trying to reproduce this issue and will notify you as soon as I have any progress!
Best,
Hannes
Hi Nicholas,
Thank you for the suggestion!
I think it is a valid point and I’ve forwarded this idea to our product manager. Will keep you informed when there are updates regarding this functionality.
All the best,
Tiit
Looks better on the nightly build. Thanks.
Hi,
In that case can you send the jrebel.log from the remote server and the jrebel-[ide].log from the local machine. Hopefully it will provide a better overview of why the password settings are not taking effect.
You can send the logs to support@zeroturnaround.com
Make sure to zip them beforehand and provide a link to this forum thread just in case.
Hello,
This error occurs, since we do not inject XRebel toolbar into a couple of applications such as the Tomcat manager application.
I’d suggest using the workaround by navigate to your ${USER_HOME}/.xrebel/disabled-deployments.txt and deleting following:
“Welcome to Tomcat”
“Tomcat Manager Application”
“Tomcat Host Manager Application”
“WebLogic Console”
“Diablo Console”
“isclite”
Start your Tomcat server and try to access localhost/xrebel.
Leila
Hi,
This is very frustrating to debug with JRebel 7. It hangs when I debug into any transactional method. JRebel version is 7.1.5. (The error was also with previous versions of 7 as well).
I am using java8 (update 141) and IntelliJ Idea 14.1.7. The DBMS is SQL Server 2014. I had no such error when I was on Oracle 11g.
Please help regarding this!
Regards,
Bharat Arya
Hello,
JRebel 7.1.6 was released earlier today, this update should resolve the issue that was happening when using JRebel with FlightRecorder in debug mode.
Let me know if you continue running into any issues.
Colton
Hello All,
I added the following to the standalone.sh script to enable debugging and JRebel (Same flags as I use for Jboss 5.1.0 which works fine)
export JAVA_OPTS=”-Xmx768m -noverify -javaagent:/Applications/ZeroTurnaround/JRebel-4.5.3/jrebel.jar -Drebel.trace.log=true -Drebel.wicket_plugin=true -XX:PermSize=256M -Xdebug -Xrunansport=dt_socket,server=n,suspend=y,address=8787″
JBoss dies with a segmentation fault:
ERROR: transport error 202: connect failed: Connection refused
Invalid memory access of location 0x0 rip=0x7fff88a515f0
./standalone.sh: line 178: 31708 Segmentation fault: 11 “/System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home//bin/java” -D”[Standalone]” -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xmx768m -noverify -javaagent:/Applications/ZeroTurnaround/JRebel-4.5.3/jrebel.jar -Drebel.trace.log=true -Drebel.wicket_plugin=true -XX:PermSize=256M -Xdebug -Xrunjdwp:transport=dt_socket,server=n,suspend=y,address=8787 “-Dorg.jboss.boot.log.file=/Users/novotny/Software/jboss-as-7.1.0.Final/standalone/log/boot.log” “-Dlogging.configuration=file:/Users/novotny/Software/jboss-as-7.1.0.Final/standalone/configuration/logging.properties” -jar “/Users/novotny/Software/jboss-as-7.1.0.Final/jboss-modules.jar” -mp “/Users/novotny/Software/jboss-as-7.1.0.Final/modules” -jaxpmodule javax.xml.jaxp-provider org.jboss.as.standalone -Djboss.home.dir=”/Users/novotny/Software/jboss-as-7.1.0.Final”
Help me out!
Thanks!
Hi,
By looking at the path from which JRebel attached from, it seems as you’re using the 4.5.3 version of JRebel?
Could you please verify whether the same issue happens with the latest version of JRebel?
If so, could you please send us the hs_err_pid crash dump file to support@zeroturnaround.com. It’ll provide us a bit more information about this segfault.
All the best,
Tiit
I’m having this anoying issues with JRebel lately. Sudenly I have this message popuping up JRebel: WARN Write failed and the changes are ignored, so i have to restart my server and then it’s working for 3-5 changes and this message apears again and I can’t make it go away, please help me.
Hello!
Could you please send the full error stack trace and your trace level jrebel.log file after reproducing the issue to support@zeroturnaround.com with the link to this forum topic? To generate it just add -Drebel.log=trace to your VM arguments, restart your server and reproduce the issue.
Please also mention the full path and name of the file you are trying to change when that warning pops up!
Kind regards,
Valerie
After upgrading Liberty to 17.0.03, server does not start if JRebel agent (64 bit, ver. 7.1.3 or 7.1.4 or 7.1.6) is configured. Liberty 17.0.0.2 works OK with all versions of JRebel. Java 1.8.0_151
Here is the error stack:
2018-02-09 09:54:14,601 [Default Executor-thread-8] INFO LogHelper – HHH000204: Processing PersistenceUnitInfo [
name: reinsibnr
…]
2018-02-09 09:54:15,541 [Default Executor-thread-8] INFO Version – HHH000412: Hibernate Core {5.0.11.Final}
2018-02-09 09:54:15,552 [Default Executor-thread-8] INFO Environment – HHH000206: hibernate.properties not found
2018-02-09 09:54:15,564 [Default Executor-thread-8] INFO Environment – HHH000021: Bytecode provider name : javassist
2018-02-09 09:54:15,942 [Default Executor-thread-8] INFO Version – HCANN000001: Hibernate Commons Annotations {5.0.1.Final}
[INFO ] FFDC1015I: An FFDC Incident has been created: “java.lang.VerifyError: Stack map does not match the one at exception handler 181
Exception Details:
Location:
com/ibm/ws/classloading/internal/ShadowClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class; @181: aload_2
Reason:
Type top (current frame, locals[2]) is not assignable to ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ (stack map, locals[2])
Current Frame:
bci: @117
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’ }
stack: { ‘java/lang/Throwable’ }
Stackmap Frame:
bci: @181
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’, ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ }
stack: { ‘java/lang/Throwable’ }
Bytecode:
0x0000000: 1100 0057 b801 7d99 002a b200 43c6 0024
0x0000010: b200 43b6 0180 9900 1b2a b200 4313 019e
0x0000020: 1301 82bd 0184 5913 0185 2bb8 01b4 b801
0x0000030: 9d00 2ab8 01d8 1209 b801 bec0 0009 594d
0x0000040: c22a 2bb6 0170 4e2d 01b8 01de 9900 2a2d
0x0000050: 2cc3 b801 7d99 0020 b200 43c6 001a b200
0x0000060: 43b6 0180 9900 1159 2a5f b200 435f 1301
0x0000070: 9e5f b801 8db0 b801 662a 2bb9 0174 0300
0x0000080: 4e2d 01b8 01de 9900 2a2d 2cc3 b801 7d99
0x0000090: 0020 b200 43c6 001a b200 43b6 0180 9900
0x00000a0: 1159 2a5f b200 435f 1301 9e5f b801 8db0
0x00000b0: 2cc3 a700 0c2c c3b8 01d2 c001 78bf 2ab8
0x00000c0: 01c8 2bb6 0023 4d2b 102e b600 243e 1d02
0x00000d0: 9f00 1b2b 031d b600 253a 042a 1904 b600
0x00000e0: 26c7 000a 2a2c 1904 b700 272c b900 2801
0x00000f0: 003a 042a 2b19 0403 1904 beb6 0029 b801
0x0000100: 7d99 0020 b200 43c6 001a b200 43b6 0180
0x0000110: 9900 1159 2a5f b200 435f 1301 9e5f b801
0x0000120: 8db0
Exception Handler Table:
bci [65, 176] => handler: 181
Stackmap Table:
same_frame(@49)
same_locals_1_stack_item_extended(@117,Object[#374])
append_frame(@118,Object[#9],Object[#374])
same_locals_1_stack_item_frame(@175,Object[#374])
same_frame(@176)
full_frame(@181,{Object[#9],Object[#127],Object[#9]},{Object[#376]})
append_frame(@190,Object[#374])
full_frame(@235,{Object[#9],Object[#127],Object[#138],Integer},{})
same_locals_1_stack_item_frame(@289,Object[#374])
com.ibm.ws.container.service.state.internal.ApplicationStateManager 31” at ffdc_18.02.09_09.54.15.0.log
[INFO ] FFDC1015I: An FFDC Incident has been created: “com.ibm.ws.container.service.state.StateChangeException: java.lang.VerifyError: Stack map does not match the one at exception h
andler 181
Exception Details:
Location:
com/ibm/ws/classloading/internal/ShadowClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class; @181: aload_2
Reason:
Type top (current frame, locals[2]) is not assignable to ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ (stack map, locals[2])
Current Frame:
bci: @117
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’ }
stack: { ‘java/lang/Throwable’ }
Stackmap Frame:
bci: @181
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’, ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ }
stack: { ‘java/lang/Throwable’ }
Bytecode:
0x0000000: 1100 0057 b801 7d99 002a b200 43c6 0024
0x0000010: b200 43b6 0180 9900 1b2a b200 4313 019e
0x0000020: 1301 82bd 0184 5913 0185 2bb8 01b4 b801
0x0000030: 9d00 2ab8 01d8 1209 b801 bec0 0009 594d
0x0000040: c22a 2bb6 0170 4e2d 01b8 01de 9900 2a2d
0x0000050: 2cc3 b801 7d99 0020 b200 43c6 001a b200
0x0000060: 43b6 0180 9900 1159 2a5f b200 435f 1301
0x0000070: 9e5f b801 8db0 b801 662a 2bb9 0174 0300
0x0000080: 4e2d 01b8 01de 9900 2a2d 2cc3 b801 7d99
0x0000090: 0020 b200 43c6 001a b200 43b6 0180 9900
0x00000a0: 1159 2a5f b200 435f 1301 9e5f b801 8db0
0x00000b0: 2cc3 a700 0c2c c3b8 01d2 c001 78bf 2ab8
0x00000c0: 01c8 2bb6 0023 4d2b 102e b600 243e 1d02
0x00000d0: 9f00 1b2b 031d b600 253a 042a 1904 b600
0x00000e0: 26c7 000a 2a2c 1904 b700 272c b900 2801
0x00000f0: 003a 042a 2b19 0403 1904 beb6 0029 b801
0x0000100: 7d99 0020 b200 43c6 001a b200 43b6 0180
0x0000110: 9900 1159 2a5f b200 435f 1301 9e5f b801
0x0000120: 8db0
Exception Handler Table:
bci [65, 176] => handler: 181
Stackmap Table:
same_frame(@49)
same_locals_1_stack_item_extended(@117,Object[#374])
append_frame(@118,Object[#9],Object[#374])
same_locals_1_stack_item_frame(@175,Object[#374])
same_frame(@176)
full_frame(@181,{Object[#9],Object[#127],Object[#9]},{Object[#376]})
append_frame(@190,Object[#374])
full_frame(@235,{Object[#9],Object[#127],Object[#138],Integer},{})
same_locals_1_stack_item_frame(@289,Object[#374])
com.ibm.ws.app.manager.module.internal.DeployedAppInfoBase 376” at ffdc_18.02.09_09.54.16.0.log
[INFO ] FFDC1015I: An FFDC Incident has been created: “java.lang.NullPointerException com.ibm.ws.container.service.state.internal.ApplicationStateManager 72” at ffdc_18.02.09_09.54.1
6.1.log
[ERROR ] CWWKZ0106E: Could not start web application reinsibnrEAR.
[ERROR ] CWWKZ0002E: An exception occurred while starting the application reinsibnrEAR. The exception message was: com.ibm.ws.container.service.state.StateChangeException: java.lang.V
erifyError: Stack map does not match the one at exception handler 181
Exception Details:
Location:
com/ibm/ws/classloading/internal/ShadowClassLoader.findClass(Ljava/lang/String;)Ljava/lang/Class; @181: aload_2
Reason:
Type top (current frame, locals[2]) is not assignable to ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ (stack map, locals[2])
Current Frame:
bci: @117
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’ }
stack: { ‘java/lang/Throwable’ }
Stackmap Frame:
bci: @181
flags: { }
locals: { ‘com/ibm/ws/classloading/internal/ShadowClassLoader’, ‘java/lang/String’, ‘com/ibm/ws/classloading/internal/ShadowClassLoader’ }
stack: { ‘java/lang/Throwable’ }
Bytecode:
0x0000000: 1100 0057 b801 7d99 002a b200 43c6 0024
0x0000010: b200 43b6 0180 9900 1b2a b200 4313 019e
0x0000020: 1301 82bd 0184 5913 0185 2bb8 01b4 b801
0x0000030: 9d00 2ab8 01d8 1209 b801 bec0 0009 594d
0x0000040: c22a 2bb6 0170 4e2d 01b8 01de 9900 2a2d
0x0000050: 2cc3 b801 7d99 0020 b200 43c6 001a b200
0x0000060: 43b6 0180 9900 1159 2a5f b200 435f 1301
0x0000070: 9e5f b801 8db0 b801 662a 2bb9 0174 0300
0x0000080: 4e2d 01b8 01de 9900 2a2d 2cc3 b801 7d99
0x0000090: 0020 b200 43c6 001a b200 43b6 0180 9900
0x00000a0: 1159 2a5f b200 435f 1301 9e5f b801 8db0
0x00000b0: 2cc3 a700 0c2c c3b8 01d2 c001 78bf 2ab8
0x00000c0: 01c8 2bb6 0023 4d2b 102e b600 243e 1d02
0x00000d0: 9f00 1b2b 031d b600 253a 042a 1904 b600
0x00000e0: 26c7 000a 2a2c 1904 b700 272c b900 2801
0x00000f0: 003a 042a 2b19 0403 1904 beb6 0029 b801
0x0000100: 7d99 0020 b200 43c6 001a b200 43b6 0180
0x0000110: 9900 1159 2a5f b200 435f 1301 9e5f b801
0x0000120: 8db0
Exception Handler Table:
bci [65, 176] => handler: 181
Stackmap Table:
same_frame(@49)
same_locals_1_stack_item_extended(@117,Object[#374])
append_frame(@118,Object[#9],Object[#374])
same_locals_1_stack_item_frame(@175,Object[#374])
same_frame(@176)
full_frame(@181,{Object[#9],Object[#127],Object[#9]},{Object[#376]})
append_frame(@190,Object[#374])
full_frame(@235,{Object[#9],Object[#127],Object[#138],Integer},{})
same_locals_1_stack_item_frame(@289,Object[#374])
I use Spring Boot and a java library that reads resources. The problem is that when I use jrebel, this library founds resources in two places:
1. URL [jar:file:/app.jar!/BOOT-INF/classes/schema/main.graphqls]
2. file [/root/.jrebel/cache/api/deployment/BOOT-INF/classes/schema/main.graphqls]
here the first location is where resources are actually located, while the second location contains duplicates. It causes errors.
How to avoid this?
I tried to use the following:
<classpath>
<dir name="/project/target/classes">
<exclude name="**/*.graphqls"/>
</dir>
</classpath>but it changes nothing.
