weave | Simple , resilient multi-host containers | Continuous Deployment library

You can do this

As described in the AspectJ 1.9.7 release notes, due to JEP 396 you need to add --add-opens java.base/java.lang=ALL-UNNAMED to your Java command line.

The problem you have when running your runMainWithError.sh script is documented in AspectJ issue #563710. There is an advice which ought to be inlined, but is not.

Looking at your around advice, I see that it proceeds, but it does not actually change any parameters or return values. So you can simply split it into a before/after-advice pair. Actually, you are not even doing anything after proceeding, so even a simple before-advice would suffice:

There is a subtle error in your aop.xml:

You are using an incorrect syntax. payload.rates is an object so you can just use the dynamic selector:

Sorry, this is going to be a lengthy answer, because there is so much wrong or problematic with your own aspect code, I could not resist to suggest how to fix it. But we are going to do that step by step.

Two dependencies in your POM are not publicly available, others like io.github.cdimascio:dotenv-java are missing completely, or you are relying on them to be transitive dependencies of the non-public ones, which is a Maven anti-pattern. I fixed that locally, created missing classes like the SLA annotation and EnvironmentConsumer, added a .env file containing a Timeout variable and also a TestNG test. Now I can compile and run the project. All of this would have been your job. Because you are a newbie and I needed a puzzle with my morning tea, I did it for you this time. This was your free shot. Next time, please do that by yourself. Thank you. 🙂

BTW, you also forgot to post your NullPointerException including stack trace.

As for Maven Surefire logging the AspectJ weaver info messages as [ERROR], you can ignore that. Probably Surefire thinks they are errors, because it does not expect any log output before the test has started running. I had discussions with the Surefire maintainers about this issue before, they do not really understand Java agents, but that is a topic for another day.

What I can say is that in simple cases, i.e. the intercepted method is directly annotated with something like @SLA(tiempoEsperado = 2), the method does not throw any errors. Even if the annotated method is from a super class, it works as expected. The method as such is unnecessary, as I am going explain at the end of this long answer, because AspectJ has a much more elegant way of fetching the annotation from an intercepted method or class. But let us keep that for later.

When testing your aspect, I see that java.lang.Exception: Step timeout is always thrown, which is a bug. You have to change the faulty logic

In true Stack-Overflow-as-rubber-duck fashion, the solution became obvious while writing my best attempt at an answer within the question, so obvious that I almost didn't bother posting.

With GNU sed's R command:

I am not an active Spring user, but I know that Spring supports annotation- or XML-configured agent hot-attachment and has some container-specific classes for that according to its documentation. It does not seem to work reliably in all situations, though, especially when running a Spring Boot application from an IDE or so.

Anyway, the AspectJ weaver 1.8.7 and more recent can be hot-attached. I explained how to do that in a Spring setup here. If you want a simpler solution with less boilerplate but one more dependency to a tiny helper library called byte-buddy-agent, you can use this solution as a shortcut. I have not tried it, but I know the helper library and am using it myself in other contexts when hot-attaching bytecode instrumentation agents, avoiding the fuss to cater to different JVM versions and configuration situations. But in order for that to work on JVM 9+, you might need to manually activate auto-attachment for the JVM, which would be another modification for your start-up script, and you would be back to square 1.

No. MuleSoft only distributes patches for the Enterprise Edition (ie the commercial version). The reason you can not use the link is that you need to be a customer of the Enterprise Edition. Even if you could access it, trying to use a patch for a different version or edition may cause unexpected failures.