Discussion Feed

All,   I'm using a v20.5 agent.   I have a transaction snapshot that includes a web service exit call that seems to take 8 seconds.  Between log timestamps, as well as timestamps in the body of the request and response messages themselves, I believe the response time was actually well under 1 second.  The snapshot web service exit call details says "05.JAXBElement."  It says this took 8 seconds.  What is it trying to tell me?  The code uses SpringWsDataProvider.marshalSendAndReceive() and passes in a JAXBElement and a WebServiceMessageCallback.   thanks   ... View more

I'm using agent v20.3 and CXF 3.2.12.   AppD isn't identifying individual web services on the front end.  Instead, it's lumping them all in to a single business transaction named after the url like "/myapp/services."  The java auto discovery rule has "web service transaction monitoring enabled" and "discover transactions automatically for all web service requests" both checked.   What else can I do differentiate the individual services?   thanks ... View more

I'm using 4.5.17.   My SLF4J errors per minute rate is very high.  I see them mainly in two JMS transactions.  One is named MyListener.onMessage.  The other is MyListener:queue:///my.queue.name.   What is the difference between these?  The first one seems clear.  onMessage is the entry point for JMS messages to my application code.  There are some error messages logged there.  However I assume the second one also occurs in the same code.   thanks ... View more

I'm using 4.5.5.   I've defined JMX metrics for a custom MBean but under JMX Metrics I see only 1 of 5 properties that I've defined.  I see all 5 in the MBean browser.  I can't find any typos in the property names.  In the logs, I see "Added new JMX Rule," which looks correct.  It lists the 5 metric names that I defined, though only one of the 5 ever shows up.   FWIW, I also see "Added new JMX Rule," followed by an identical "Deleted JMX Rule," followed again by the same "Added new JMX Rule."   thanks   ... View more

I'm using 4.5.5.   I created an exit point to track calls to java.sql.Connection.isValid() but it doesn't work.  Since then I've been seeing this error in the agent logs:   [Log files redacted]   Any suggestions?   thanks   ^ Post edited by @Ryan.Paredez to remove log files. Please do not share or attach log files to community posts for security and privacy reasons.   ... View more

I'm using 4.5.x.   I have a vendor app that seems to use a combination of Struts and JSPs.  Even with the same code, on some servers the business transactions are named after Struts actions ("someAction.execute") and on others they are named after JSPs (something.jsp.)  In the latter case, if I look at the transaction snapshots, I can see that the URLs are all Struts URLs like someAction.do.  Additionally, different snapshots for the same JSP business transaction will have different Struts action URLs.  That is, someAction.do and someOtherAction.do are both grouped under a business transaction named something.jsp.   As far as I can tell the AppD business transactions are defined the same way in all environments.  So why does AppD seem to focus on JSPs vs Struts actions on different servers?  The inconsistency makes it hard to compare servers and environments.  I don't think I have much of an opinion yet on which way is better, but I want it consistent across servers.   FWIW, nearly all URLs in the access log are Struts actions and not JSPs, so I think the JSPs I'm seeing in the business transactions are Struts action forwards.   Thank you   ... View more

I'm using AppD 4.5.11.3848 and Oracle JDK 1.8.0_231.   I've seen some incorrect process CPU% reported by the java agent.  It appears that the number is being derived as follows:   Process CPU burnt (ms/min)/60000/Runtime.availableProcessors()   In other words, the number of milliseconds of CPU used in a minute, divided by the number of milliseconds in a minute, divided by the result of Runtime.availableProcessors().  So, if there are 4 CPUs and the "cpu burnt" number is 30000, then we'd have 30000/60000/4, which is 12.5%   However, the Runtime.availableProcessors() method doesn't always report the actual number of processors.  Instead, if -XX:ActiveProcessorCount=n is set, it uses that.  In my example, if there were actually 8 CPUs but -XX:ActiveProcessorCount=4 is set, then AppD will report 12.5% when the actual number should be 6.25% (divide by 8 instead of 4.)   The active processor count does not actually limit the number of CPUs the process can use so I think this method of calculating process CPU % fails when the active processor count is set to something other than the actual value.   thanks     ... View more

All, Hopefully this is an easy one.   When I'm looking at a list of recorded business transactions, how can I know which transaction definition each one belongs to?   In particular, I have one whose name appears to be part of the URI + '.' + the soapaction header but I don't know how to find the definition for this transaction.   thanks   ... View more