Sorry for my delayed answer. I've tried examples with only futures that you
give and they works really fine, all agent were closed.
And I figured out that this problem arises only when I using datomic.api.
java -version
java version 1.7.0_55
OpenJDK Runtime Environment (IcedTea 2.4.7)
On my Ubuntu 14.04 laptop process doesn't terminates at all. I was waiting
about an hour.
Also this issue affects code which uses datomic.api, which, I think, uses
futures too.
Середа, 30 липня 2014 р. 22:50:11 UTC+3 користувач Andy Fingerhut написав:
Never is an awfully long time :-) If you
Serzh:
Could you give a few details about the software machine where you saw it
not terminate, even after an hour? I may try collecting some info like
this to add to the Clojure ticket. In particular, the outputs of the
following commands.
java -version
uname -a
lsb_release -d
time java -jar
Hello. I have a problems using code with futures. For example, if I run
following code:
java -jar clojure-1.6.0.jar -e (println 1)
the process prints 1 and terminates.
But when I'm trying to run code with futures:
java -jar clojure-1.6.0.jar -e (future 1)
the process doesn't terminates.
This
Never is an awfully long time :-) If you wait about 60 seconds, the
command you gave calling (future 1) does terminate, at least on Mac OS X
10.8.5 where I tested it, and I have seen the same behavior on Linux and I
think Windows.
This version terminates much more quickly:
java -jar
