Hi everyone,
I have been using AppDynamics Pro for the past 1 week and I was quite satisfied with it, but I wanted to try the Lite version too to see if it can provide me with the information I need. I thought I can change start a LiteViewer and change the Pro agent to the Lite agent, start my JBoss server again and I will be ready to go.
I had some troubles with the Pro agent initially, but I was able to run it after some hours of experimenting just by using the -Djboss.modules.system.pkgs=org.jboss.byteman,com.singularity option.
So I swapped the agent file (created a new directory for it, and changed the path in the -javaagent option) and tried to restart my server. It failed with a nice Caused by: java.lang.VerifyError exception, so I thought I just need to add -XX:SplitVerifier, however as I did that my Oracle DB connection died with a rather nasty exception. After some inspection it turned out to be a known "problem" so I can't use -XX:SplitVerifier.
My question would be I think: now what? 🙂 Obviously you guys have already implemented some kind of workaround in the Pro agent for the VerfiyError problem, but it is not there in the Lite agent. Is there any way I can use the Pro agent with the LiteViewer? Or are there any plans to port this VerifyError-workaround into the Lite agent? Or am I missing something obvious here?
thank you!
I just wanted to tell you that I was lucky today: I have AppDynamics Lite up and running using the -XX:-UseSplitVerifier option and Oracle works too.
The solution was a little bit simpler than I expected: I downloaded OC4J and extracted the missing class (Oracle PKI - oraclepki.jar) from it, put it next to the Oracle driver ($JBOSS_HOME/modules/com/oracle/main/ojdbc6.jar) and edited the module.xml to include both jars. After that even with -XX:-UseSplitVerifier Oracle was able to instantiate the class fixing the problem I had earlier.
I hope this helps some people 🙂
Hi,
We understood that you have used -XX:-UseSplitVerifier option using lite agnet and that does not helps let us know if any disconnect, we see this is a known issue and the fix is to use pro agent which have the fix for the error.
Regarding other query, we recommend to use lite agent to monitor performance data in lite viewer and use pro agent with AD controller. We currently do not have such plans of porting the fix the lite as of now, and we recommend to use Pro agent having the fix, you can try pro trial version which is limited period free version lite lite but with more features.
Let us know if that answers your queries.
Regards,
Arun
Thanks Arun, we already tried the Pro trial but we didn't have enough time to evaluate it, and as far as I can see the Lite version would fit perfectly our needs. I will keep trying to fix the Lite agent somehow and I also emailed your sales personel to get a quote on the Pro version.
It is such a shame that the Lite version isn't usable because of this nasty bug which you said you will not fix :(.
I just wanted to tell you that I was lucky today: I have AppDynamics Lite up and running using the -XX:-UseSplitVerifier option and Oracle works too.
The solution was a little bit simpler than I expected: I downloaded OC4J and extracted the missing class (Oracle PKI - oraclepki.jar) from it, put it next to the Oracle driver ($JBOSS_HOME/modules/com/oracle/main/ojdbc6.jar) and edited the module.xml to include both jars. After that even with -XX:-UseSplitVerifier Oracle was able to instantiate the class fixing the problem I had earlier.
I hope this helps some people 🙂
Glad to hear that you could use Lite version now fine, thanks for sharing the information with us.