What steps will reproduce the problem?
1. We had the following code in our system:
reflections = new Reflections(new ConfigurationBuilder()
.useParallelExecutor()
.setUrls(ClasspathHelper.getUrlsForPackagePrefix(""))
.setExecutorServiceSupplier(
new Supplier<ExecutorService>() {
public ExecutorService get() {
return Executors.newFixedThreadPool(Runtime.getRuntime().availableProcessors());
}
}
));
On many machines the code here completely hangs, on some very fast machines it
does not. Removing the .useParallelExecutor() line (which really seems to be
useless given that we provide an ExecutorService) seems to fix the problem.
So while the configuration does not make sense, it probably also should not
hang the JVM.
What version of the product are you using? On what operating system?
Reflections 0.9.5 RC 2, JDK 1.6.0_23, Tomcat 6.0.32, Windows 7, Eclipse Helios
Original issue reported on code.google.com by thomas.b...@gmail.com on 6 Apr 2011 at 9:45
Original issue reported on code.google.com by
thomas.b...@gmail.com
on 6 Apr 2011 at 9:45