autoproxy | 一个用于scrapy爬虫的自动代理中间件

You might be hitting Spring issue #21674 which was fixed in Spring 5.1. You might want to upgrade, if that is an option. It seems there is a fix which ignores those kinds of methods. If that is OK for you or not, I do not know.

Some background information: Your target method is transactional, so Spring tries to create a CGLIB proxy for it. I quickly verified in a simple Spock (Groovy) test that CGLIB seems to be unable to handle methods containing spaces correctly -probably because it is simply unaware of languages like Groovy and Kotlin which allow such things. Here is a proof of concept. I used Groovy and Spock, because I am lazy and did not want to set up a Kotlin project. But I am expecting the result to be identical.

Java class under test:

I cloned your MCVE repository. Thanks, that was helpful.

Please note that Java records are implicitly final. Therefore, Spring AOP cannot subclass them in order to create dynamic proxies.

You need to change

Did you mean test_m = cs_m(1)?

First of all from my experience you have to register a managed class with the manager's class before the manager server is started:

The following configuration would result in NoSuchBeanDefinitionException when attempting to get the bean from context.

I think you are right about the problem. If you were doing build time weaving, it would be totally fine as the modified byte code will be fed into GraalVM native-image for analysis and inclusion in the image. If doing loadtime weaving I believe it can work but haven't confirmed recently if you use loadtime weaving at the point the native-image is being built (via setting the java options to include the aspectjweaver agent), the classes will be woven as they are loaded and the woven form will be included in the image. It can never really work at image runtime because there is no notion of classes any more, and classes cannot be dynamically defined.

So yes, since Spring AOP can be done quite late on, as configuration is resolved, there may be problems. Take a look at the spring native project for the very latest support building your Spring projects into native-images, but we have no samples there for Spring AOP right now as I recall. I'd encourage you to raise issues against that project, including a sample project that show your specific problem can be invaluable. You haven't mentioned how you are creating the native-image right now which may influence my recommendations. I think pushing some analysis/weaving a bit earlier in the process could make it work but haven't been into that space yet.

As @FrankYellin noted, this is due to the fact that None is being put into task_queue before bar can be added.

Assuming that the queue will either be non-empty or waiting for a task to complete during the program (which is true in my case), the join method on the queue can be used. According to the docs:

Blocks until all items in the queue have been gotten and processed.

The count of unfinished tasks goes up whenever an item is added to the queue. The count goes down whenever a consumer thread calls task_done() to indicate that the item was retrieved and all work on it is complete. When the count of unfinished tasks drops to zero, join() unblocks.

Below is the updated code:

Both @EnableAspectJAutoProxy and enable creation of the bean post-processor singleton AnnotationAwareAspectJAutoProxyCreator. This object has an optional property includePatterns for filtering the eligible annotated aspect beans. By default all annotated aspect beans are eligible which means that advisors will be created for their annotated methods and these advisors will later be matched while wrapping the other beans with proxies.

includePatterns is only configurable via the XML tag , there's no annotation equivalent. If you have in one of your XML configs you can't clear includePatterns to make all annotated aspects eligible.

All this makes it pointless to use AspectJ annotations if you want to avoid side effects. To create just one aspect bean without enabling aspectj-autoproxy it's optimal to configure that bean with the tag:

You are creating a new instance of CacheableService in your test, which means it is not managed by Spring and non of the Spring annotations will work in it.

For spring to kick in, you need to get your service as a bean, autowired into your test class

It seems related to pom.xml

Can you try with higher spring boot version? ie 2.1.0.RELEASE

I'm using this release