autoproxy | Public proxy farm that automatically records and queues suitable proxy servers for web crawling | Proxy library

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

Ok, so I found the culprit, turns out it was the Java 9 module-info.java, I encountered an issue making RabbitMq work, all files were imported correctly but it was pointing to say the error was coming from my module-info.java so I removed it, after removing it I have not had this problem (and RabbitMq worked too), from my understanding, their are internal classes that were not put on the allow list that need to access my classes and because of that the app kept failing, the app has been working since then without any problems.

Short answer is: no

Spring Batch will use the transaction manager defined as part of your JobRepository by default. This will allow it to roll back the whole chunk when an error has been encountered and then retry each item individually in its own transaction.

You have a strange web site for downloading JARs there. I recommend not to download dependency JARs manually but to use a build tool like Maven to take care of that for you. Anyway, if you want to make your life as a developer harder, you can do it manually. You can search for and download dependencies here:

https://mvnrepository.com/artifact/org.aspectj/aspectjweaver

Just search, select the version you need and then download.

The reason for your problem is that, guessing by your link URL, you downloaded the AspectJ runtime library aspectjrt.jar, but that one is the smallest one there is and meant to be used with ApsectJ compile-time weaving. You are using Spring AOP, which depends on the AspectJ load-time weaving library aspectjweaver.jar. Put that one on your classpath, then your error should go away. BTW, the weaver library contains a superset of the runtime classes, so you do not need the runtime anymore in this case.

I also recommend to read some more documentation. The Spring manual tells you to use the weaver, not the runtime, see chapter Enabling @AspectJ Support.

It was a dependency issue. The problem was that the dependency spring-boot-startet-jersey includes an older version of spring-aop so I excluded it:

Use 127.0.0.1 instead of localhost, Hazelcast does not resolve hostname/DNS while forming a cluster.