weaver | JS library that facilitates concise | Job Scheduling library

You can use subqueries:

Explaining the error

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:

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 your code

This can be accomplished without any additional package. Since NET 5 you have to set two options.

I think you can rely on the regex to get the URL out instead of trying to clean the string manually. The other way would be to use json_decode().

Anyways the idea is to define a variable in extract.php, in this case it is $resp. Doing it via echo as you are now will not make it available in the parent script.

You can then reference that variable in play.php once extract.php has been included.