Andreas, I am curious; What is your use-case for requiring JVMs to frequently move between tiers? Generally, tier naming is driven by the logical purpose of the JVM (often, what service it implements for a microservice architecture) and isn’t too volatile for any given JVM It would be helpful to understand how your deployment differs from this model. Warm regards, Peter ... View more

This is a very surprising finding to me. What was your SEP configuration before and after? ... View more

I see nothing obviously wrong in these logs.  The log from the proxy instance servicing the node process would be useful too. I suggest the best way to take this forward is via a support ticket; are you able to open one and attach all the logs? Warm regards, Peter ... View more

Stjin, That is definitely not expected! How is the heap sizing?  If the JVM was operating close to heap capacity before you introduced the agent, maybe the additional agent memory footprint is now causing frequent Garbage collection? If that's not the case, then we need to figure out what is consuming the time.  Can post some agent logs, either here or in a support ticket? Warm regards, Peter ... View more

It looks like the agent is unable to launch its communcation proxy: [2018-03-13 14:12:31.062] [INFO] default - Proxy logging to: /tmp/appd/709d8f016ec1eba1a412d004d957647e/proxy/l [2018-03-13 14:12:31.062] [INFO] default - Proxy spawned! [2018-03-13 14:12:40.855] [ERROR] default - no response on control socket [2018-03-13 14:12:40.888] [ERROR] default - unable to contact proxy Are there any proxy logs?  If so, could you post them?  If not, could you collect debug logs from the agent and post these? Warm regards, Peter ... View more

It is presently still in beta.  We do not yet have a firm release plan. ... View more

What errors do you see in the agent logs? We have many customers monitoring applications deployed in EC2, so there is no fundamental problem with what you are doing. Warm regards, Peter ... View more

Can you please post a full set of agent logs, either here or in a support case. Warm regards, Peter ... View more

Reece, For now, you can configure a method to serve as an asynchronous transaction demarcator (presumably, the method which sends the reply) and that will measure the response time for you. Is your code running in the context of a Spring Boot 2 servlet?  If so, once we have added out of the box configuration for spring boot 2 then the ttransactions should be detected automatically with the correct response times. Warm regards, Peter ... View more

Reece, You can absolutely add custom "POJO" entry points and custom exit points to detect activity within any framework that is not supported out of the box. Exactly what entries and exits is your application using? Warm regards, Peter ... View more

if you run "ps -ef" with your tomcat started, do you see the -javaagent option added to the tomcat JVM command string?  Can you post what you see here? ... View more

Which exception can you see? The one I have pasted below is benign, and you can ignore it.  It will be fixed in the next agent release. [Thread-21] 20 Feb 2018 16:14:02,152  WARN AgentConfigWatchdog - Error in initializing from app-agent-config.xml java.lang.NullPointerException     at com.singularity.ee.agent.appagent.kernel.config.xml.a.a(a.java:474)     at com.singularity.ee.agent.appagent.kernel.config.xml.a.d(a.java:432)     at com.singularity.ee.agent.appagent.kernel.config.xml.a.doOnChange(a.java:123)     at com.singularity.util.org.apache.log4j.helpers.FileWatchdog.checkAndConfigure(FileWatchdog.java:87) ... View more

When you say "unable to get it to work", can you elaborate? Does tomcat start?  If not, does it log any errors? If yes, what does happen?   do you see any agent logs under /home/centos/appagent/ver4.4.1.0/logs? ... View more

Ajay, The exception in your agent log is benign (which is why the fact that it is logged got missed - this is fixed in the next version. The exception in your stdout, however, seems to indicate that the agent cannot obtain the value of the "java.specification.version" system property. Could you please open a support case and support can work through this issue with you in more depth. Warm regards, Peter ... View more

I think I found the problem at line 373 of your new agent log file: [Thread-5] 22 Feb 2018 16:12:58,696  WARN ConfigurationChannel - ResponseReadException creating Response Wrapper [g], : com.singularity.ee.rest.c: Error in controller in processing binary request AppAgent Config Data  - Agent license request denied. Agent type: java-app-agent; Node: sbelt10389; Application: CARMAFE; Host: sbelt10389.devbe.development; Reason: License limit hit for controller ... View more

Ah, I see.  Yes you fixed that after the first boot. Is this all the agent logs that were written?  I do not see any ByteCodeTransformer logs, which would be necessary to dig into this further. I think the most efficient way to root-cause what is going on here would be for you to open a support ticket and dig in with the support guys. Warm regards, Peter ... View more

Have you followed the documentation here with respect to the security requirements? From the log, I guess maybe you missed that step? Warm regards, Peter ... View more

Looking at your agent log, the agent is reporting successfully to the controller. The exception does suggest however that the agent is having trouble parsing its app-agent-config.xml file. Has that file got corrupted in some way?  Can you post it here? Warm regards, Peter ... View more

Reethika, To be clear, using the "request agent log files" facility in the controller UI will retrieve all the agent log files stored by the agent, not just log messages written after the request is made. What Atyuha is saying, however, is that because the agent rolls its log files to ensure they only consume a finite amout of disk space there is no absolute guarantee that ALL information logged by the agent over the previous 2 days will be available since (depending on the volume of data that has been logged) the logs may have rolled. Warm regards, Peter ... View more

What context is the POJO you configured in?  If it is downstream of another entry point (for example, if it's called within a servlet) then you will need an exclude rule to prevent the out of the box servlet rule from naming the transaction before your rule gets hit. Warm regards, Peter ... View more

We could tell for sure with a full transaction snapshot, but it is likely that the wso2 gateway is implemented asynchronously internally, meaning the backend response time that the agent registers reflects the time taken to send the request downstream. You could investigate setting up end to end demarcation to measure the response time. I recommend you work with support via a ticket if you need heklp with this. Warm regards, Peter ... View more

Business Transaction execution within a snapshot is profiled every 10ms, as you state.  In your 18ms snapshot, it is likely that whatever methods within the servlet ran did not individually last long enough to be detected by the profiler. Given the short execution time I would imagine that whatever these methods are, they are unlikely to represent a performance problem. Warm regards, Peter ... View more

This is almost certianly due to additional fork-config configuration being required to track the async transactions within the API gateway, and perhaps some additional entry/exit configuration being required. What version of WSO2 are you using?  The documentation specifically mentions v4.7 in the support matrix. You might be best opening a support ticket so the team can help you investgate this. ... View more