Using Takipi with Debug mode

Answered

Hi,

I would like to use Takipi (overops.com) with IntelliJ. It requires me to add "-agentlib:TakipiAgent" to the VM Options. That's not a big deal since I can modify the configuration. Running my application with Run mode was good but when running it with Debug mode, the application just hang and wouldn't start. I contacted Takipi support and they suspected the issue was probably because launching with Debug mode added another agentlib  "-agentlib:jdwp=transport=dt_socket,address=127.0.0.1:56048,suspend=y,server=n" to the top of the VM arguments and it likely corrupted with Takipi one.

Is there anyway for me to append Takipi agentlib as the first VM argument? Or is there anyway to get it work?

For your information, below is the command for Run mode (copied from IntelliJ output)

"C:\Program Files\Java\jdk1.8.0_131\bin\java" -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Xdebug -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -DRESIN_HOME=C:\resin-pro-4.0.53 -Djava.library.path=C:\resin-pro-4.0.53/bin -Dresin.server=app-0 "-javaagent:C:\Program Files\JetBrains\IntelliJ IDEA 2017.2.2\lib\idea_rt.jar=56584:C:\Program Files\JetBrains\IntelliJ IDEA 2017.2.2\bin" -agentlib:TakipiAgent -Djava.library.path=C:\resin-pro-4.0.53\win64 -Xms1024m -Xmx5120m -Dfile.encoding=windows-1252 -classpath "C:\resin-pro-4.0.53\lib\activation.jar;C:\resin-pro-4.0.53\lib\eclipselink-2.4.0.jar;C:\resin-pro-4.0.53\lib\j2ee-deploy-10.jar;C:\resin-pro-4.0.53\lib\j2ee-management-10.jar;C:\resin-pro-4.0.53\lib\javaee-16.jar;C:\resin-pro-4.0.53\lib\javaee-api-7.0.jar;C:\resin-pro-4.0.53\lib\javamail-141.jar;C:\resin-pro-4.0.53\lib\javax.faces-2.1.24.jar;C:\resin-pro-4.0.53\lib\jstl-api-1.2.jar;C:\resin-pro-4.0.53\lib\ojdbc14_g.jar;C:\resin-pro-4.0.53\lib\pro.jar;C:\resin-pro-4.0.53\lib\resin-eclipselink.jar;C:\resin-pro-4.0.53\lib\resin.jar;C:\resin-pro-4.0.53\lib\validation-api-1.0.0.GA.jar;C:\resin-pro-4.0.53\lib\webservices-extra-api.jar;C:\resin-pro-4.0.53\lib\webutil.jar;C:\Program Files\Java\jdk1.8.0_131\lib\tools.jar" com.caucho.server.resin.Resin -conf C:\Users\hhoang\AppData\Local\Temp\resin22064.conf -server app-0

 

And this one is for Debug mode.

"C:\Program Files\Java\jdk1.8.0_131\bin\java" -agentlib:jdwp=transport=dt_socket,address=127.0.0.1:56993,suspend=y,server=n -Djava.util.logging.manager=com.caucho.log.LogManagerImpl -Djavax.management.builder.initial=com.caucho.jmx.MBeanServerBuilderImpl -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.port=9999 -Dcom.sun.management.jmxremote.authenticate=false -Dcom.sun.management.jmxremote.ssl=false -DRESIN_HOME=C:\resin-pro-4.0.53 -Djava.library.path=C:\resin-pro-4.0.53/bin -Dresin.server=app-0 -agentlib:TakipiAgent -Djava.library.path=C:\resin-pro-4.0.53\win64 -Xms1024m -Xmx5120m -Dfile.encoding=windows-1252 -classpath "C:\resin-pro-4.0.53\lib\activation.jar;C:\resin-pro-4.0.53\lib\eclipselink-2.4.0.jar;C:\resin-pro-4.0.53\lib\j2ee-deploy-10.jar;C:\resin-pro-4.0.53\lib\j2ee-management-10.jar;C:\resin-pro-4.0.53\lib\javaee-16.jar;C:\resin-pro-4.0.53\lib\javaee-api-7.0.jar;C:\resin-pro-4.0.53\lib\javamail-141.jar;C:\resin-pro-4.0.53\lib\javax.faces-2.1.24.jar;C:\resin-pro-4.0.53\lib\jstl-api-1.2.jar;C:\resin-pro-4.0.53\lib\ojdbc14_g.jar;C:\resin-pro-4.0.53\lib\pro.jar;C:\resin-pro-4.0.53\lib\resin-eclipselink.jar;C:\resin-pro-4.0.53\lib\resin.jar;C:\resin-pro-4.0.53\lib\validation-api-1.0.0.GA.jar;C:\resin-pro-4.0.53\lib\webservices-extra-api.jar;C:\resin-pro-4.0.53\lib\webutil.jar;C:\Program Files\Java\jdk1.8.0_131\lib\tools.jar;C:\Program Files\JetBrains\IntelliJ IDEA 2017.2.2\lib\idea_rt.jar" com.caucho.server.resin.Resin -conf C:\Users\hhoang\AppData\Local\Temp\resin76517.conf -server app-0

 

Thanks!

0
4 comments

It may be hard to find the problem without a reproducible test case. I recommend reporting an issue at https://youtrack.jetbrains.com/issues/IDEA with the small sample project attached.

0

two agentlibs should not be a problem, can you take the app thread dump during the hang?

0

Just an update. I tried to use Takipi with the debug mode again today and it worked. The differences are:

1. IntelliJ 2017.2.2 (before) vs 2017.3

2. Resin 4.0.53 (before) vs 4.0.55

Cheers.

0

Please try disabling "instrumenting agent" in Settings | Build, Execution, Deployment | Debugger | Async Stacktraces

0

Please sign in to leave a comment.