I used the cloud based Dynatrace service and it all seemed to work really well. I've been trying to get the local running version going but having some problems. I've followed the instructions online and looks like I have all the correct services running and ports open on my local server. My Dynatrace client can technically connect to it.
- Wildfly 10 Java application (multiple wars)
- latest Dynatrace 6.5 version
- Java 8
- Everything is inside a vagrant linux (CentOS) box
I added the necessary config to my standalone.conf file and it looks like it's being picked up correctly but when wildfly comes to deploy the war files it fails with the error below. If I take away the JAVA_OPTS agentpath reference for dynatrace in my standalone.conf file the server does start up fine:
Caused by: java.lang.VerifyError: (class: metrics/MetricsAdminServlet$Proxy$_$$_WeldSubclass, method: doGet signature: (Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V) Inconsistent stack height 0 != 1 ...
I've attached my server.log file
Any pointers would be greatly appreciated.
I would suggest you create an exclusion rule for that specific class. There seems to be a problem with the instrumentation of the reported class.
To do this, and ensure we get this issue resolved properly, i suggest you open a support case. Be sure to include a full support archive to get your case moving along as quickly as possible.
Thanks for the advice. I've just tried to create a support ticket but the page isn't working for me. Not sure if this is a known issue or just me?
2. clicked on AppMon
3. Error as below
Log's referral number: 9f291ebe-e2c0-475d-98b5-21e611a097b1
Referer URL: https://www.dynatrace.com/support/contact-support/
at shibauth.jira.authentication.shibboleth.RemoteUserAuthenticator.createUser(RemoteUserAuthenticator.java:452) [jiraRemoteUserAuth-2.0.0.jar:?]
at shibauth.jira.authentication.shibboleth.RemoteUserAuthenticator.getUser(RemoteUserAuthenticator.java:921) [jiraRemoteUserAuth-2.0.0.jar:?]
at com.atlassian.seraph.filter.SecurityFilter.doFilter(SecurityFilter.java:168) [atlassian-seraph-3.0.3.jar:?]
Afraid that didn't do the trick. I also tried it from an incognito tab to rule out the history. I've just created a community account using my work email so hopefully that'll do the trick. The email says "We will notify you by email regarding the status of your request within two business days."
No major rush
With regards to the error you got when you originally tried to create a support ticket, it sounds like, at the time, you weren't registered in the Community with an email account that was associated with a company that has active maintenance. However, once you did that, you were able to do so. Can you confirm if this is the case? If so, this is expected behavior. There are public forums that you can browse even without a Community account that is linked to a company with active maintenance, but you have to have maintenance in order to be able to create a support ticket.
Not sure exactly what the problem was with me logging into the support portal but seems fine now, I've created a ticket.
@Christian S. I tried shutting down the front end server (assuming this is what you mean) but still had the same issue
@Joseph H. I tried defining an exclusion rule for that package in AppMon but must be doing something wrong since it's still having the same issue.
not sure what you mean by "shutting down the front end server" ... which server are you referring to?
I meant really unplacing the "UEM Sensor" in the System Profile -> Agent Group -> Sensor Placement. I saw a similar issue in our issue tracking system and this UEM sensor was the reason back then. So I just wanted to confirm this behavior.
can you tell me the SUP case number so I can take a look at it, please.
Unfortunately I can't see an option for: "System Profile -> Agent Group -> Sensor Placement" using AppMon 6.5.
The problem was solved by excluding some of our conflicting proxy classes from being instrumented. The case number is SUPDT-33031
Link to docs for the fix: