public class TORTest {
public static void main(String [] args) {
JvmGlobalUtil.init();
NetLayer netLayer = NetFactory.getInstance().getNetLayerById(NetLayerIDs.TOR);
JvmGlobalUtil.setNetLayerAndNetAddressNameService(netLayer, true);
}
}
It connects within 5 minutes every time when it is run with Java_6_update_31.
It fails to connect every time when it is run with Java_6_update_34 (the latest Java 6) or Java_7_update_6 (the latest Java).
I haven't tested it with any other versions. The longest that I let it run for was about an hour and it still hadn't connected.
It doesn't seem to matter which JDK the program is compiled with. It only matters which JRE it is run with.
It produces thousands of lines of output each minute so I won't list a whole log file here - just a description and the first 400 lines (see the end).
The "TorNetLayer new status" messages reach 60% by line 102.
It then begins to rapidly cycle between a series of statements of the form:
Sep 02, 2012 11:20:37 PM org.silvertunnel.netlib.api.impl.NetSocket2SocketImpl getOption
INFO: no implementation for getOption(1). List of all options in java.net.SocketOptions. - Log with level=FINER to get call hierarchy.
Sep 02, 2012 11:20:37 PM org.silvertunnel.netlib.layer.tor.circuit.Circuit close
INFO: Circuit.close(): closing 28748 [Pascal3/fingerprintHexWithSpaces=350F 3570 5CDE FC1C 4ED3 18C8 CB7E E493 4211 09CB (--)] (establishing)
Sep 02, 2012 11:20:37 PM org.silvertunnel.netlib.layer.tor.circuit.TLSDispatcherThread run
INFO: TLSDispatcher.run: connection error: Socket closed
Over and over again, very quickly.
The first cycle is different from the rest in that between the "createNewRoute" series and the "Socket closed" series there is the message:
Sep 02, 2012 11:20:34 PM org.silvertunnel.netlib.layer.tor.circuit.TLSDispatcherThread run
INFO: TLSDispatcher.run: connection error: Connection has been shutdown: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: Certificate is not valid yet
Other than that the cycles are all very similar. The 400 lines of output listed below show the first few cycles. The following 10000 thousand lines (not shown) contained many more cycles and there are millions more lines like these if the program keeps running.
BTW SilverTunnel rocks! Thanks for a great library :)
john@JRLaptop:~/bin$ java -version
java version "1.7.0_06"
Java(TM) SE Runtime Environment (build 1.7.0_06-b24)
Java HotSpot(TM) 64-Bit Server VM (build 23.2-b09, mixed mode)
#########################################################################
First 400 lines of program output (Note: this same program works well with Java_6_update_31)
#########################################################################
The next reelase (available in few days) will hopefully fix the problem of new JVM versions.
Christian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-09-03
I have the exact same issue: not connecting indefinitely, same log messages with Java 1.7.0_07-b10.
However it works fine on my laptop with a recent CPU (Core 2 Duo @ 2GHz) but fails on a very old PC (Celeron @ 1.7GHz) so I thought it is a timing issue. Will try on the older JVM suggested.
Andrew
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2012-09-03
Java_6_update_31 works for me as well. Thanks is advance for the fix.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Consider the test program:
public class TORTest { public static void main(String [] args) { JvmGlobalUtil.init(); NetLayer netLayer = NetFactory.getInstance().getNetLayerById(NetLayerIDs.TOR); JvmGlobalUtil.setNetLayerAndNetAddressNameService(netLayer, true); } }It connects within 5 minutes every time when it is run with Java_6_update_31.
It fails to connect every time when it is run with Java_6_update_34 (the latest Java 6) or Java_7_update_6 (the latest Java).
I haven't tested it with any other versions. The longest that I let it run for was about an hour and it still hadn't connected.
It doesn't seem to matter which JDK the program is compiled with. It only matters which JRE it is run with.
It produces thousands of lines of output each minute so I won't list a whole log file here - just a description and the first 400 lines (see the end).
The "TorNetLayer new status" messages reach 60% by line 102.
It then begins to rapidly cycle between a series of statements of the form:
Followed by a series of statements of the form:
Over and over again, very quickly.
The first cycle is different from the rest in that between the "createNewRoute" series and the "Socket closed" series there is the message:
Other than that the cycles are all very similar. The 400 lines of output listed below show the first few cycles. The following 10000 thousand lines (not shown) contained many more cycles and there are millions more lines like these if the program keeps running.
BTW SilverTunnel rocks! Thanks for a great library :)
Regards,
John
#########################################################################
#########################################################################
First 400 lines of program output (Note: this same program works well with Java_6_update_31)
#########################################################################
I should also add that I am using the latest version:
silvertunnel.org_netlib-0.13-beta
The next reelase (available in few days) will hopefully fix the problem of new JVM versions.
Christian
I have the exact same issue: not connecting indefinitely, same log messages with Java 1.7.0_07-b10.
However it works fine on my laptop with a recent CPU (Core 2 Duo @ 2GHz) but fails on a very old PC (Celeron @ 1.7GHz) so I thought it is a timing issue. Will try on the older JVM suggested.
Andrew
Java_6_update_31 works for me as well. Thanks is advance for the fix.
Thanks Christian!
BTW Andrew, the next version works well with Java 7 (I just tested the latest code snapshot) and it should be out in a matter of days.
John
The problem is fixed in the newest release: silvertunnel.org-netlib-0.14-beta
Best regards,
Christian
i have the same problem, mainly when trying to create a server socket