Every time I start JForex I get this, and it seems
at first glance to be unnecessary downloading due
to an apparent IP mismatch from one run of JForex to
a restart of JForex.

While I don't know what it's doing, it seems unnecessary
and it seems like it's downloading Tick data, which
should really not be necessary.

This makes it very resource intensive to restart the
JForex platform. These are not just a "few" entries, but
thousands of such entries indicating historical tick
downloading. No strategies are running at this point.

This goes on in the background for something like an
hour.... If it's a question of attaching to a specific
historical "tick backfill server",
then please allow us to specify which one we
want so we don't have this IP mismatch and overhead...

Thanks,
HyperScalper

network: Downloading resource: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/16h_ticks.bi5
   Content-Length: 17,994
   Content-Encoding: null
network: Wrote URL https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/16h_ticks.bi5 to File C:\Users\Brent\AppData\Local\Sun\Java\Deployment\cache\6.0\1\28894901-6974ca8c-temp
cache: Adding MemoryCache entry: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/16h_ticks.bi5
network: Cache entry not found [url: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/17h_ticks.bi5, version: null]
network: Connecting https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/17h_ticks.bi5 with proxy=DIRECT
network: Connecting socket://www.dukascopy.com:80 with proxy=DIRECT
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
network: Downloading resource: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/17h_ticks.bi5
   Content-Length: 13,465
   Content-Encoding: null
network: Wrote URL https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/17h_ticks.bi5 to File C:\Users\Brent\AppData\Local\Sun\Java\Deployment\cache\6.0\12\12f8df4c-4da29efc-temp
cache: Adding MemoryCache entry: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/17h_ticks.bi5
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
network: Cache entry not found [url: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/18h_ticks.bi5, version: null]
network: Connecting https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/18h_ticks.bi5 with proxy=DIRECT
network: Connecting socket://www.dukascopy.com:80 with proxy=DIRECT
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
cache: CacheEntry IP mismatch: 194.8.15.113 != 194.8.15.131
network: Downloading resource: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/18h_ticks.bi5
   Content-Length: 8,935
   Content-Encoding: null
network: Wrote URL https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/18h_ticks.bi5 to File C:\Users\Brent\AppData\Local\Sun\Java\Deployment\cache\6.0\51\7dc9f073-5f90cf7f-temp
cache: Adding MemoryCache entry: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/18h_ticks.bi5
network: Cache entry not found [url: https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/19h_ticks.bi5, version: null]
network: Connecting https://www.dukascopy.com/datafeed/CADJPY/2014/08/19/19h_ticks.bi5 with proxy=DIRECT
network: Connecting socket://www.dukascopy.com:80 with proxy=DIRECT

This looks like some kind of bug with JVM caching. We will investigate this case.

You can try to disable Java's temporary internet files: Control Panel -> Java -> General -> Settings -> uncheck "Keep temporary files on mu computer". Maybe it will serve as a workaround.

I'm running the Oracle Java 7 Update 51
32-bit SERVER VM
on my Windows 7 64-bit client, which is what I have
always done for performance. The CLIENT VM is
removed, and replaced by the SERVER VM so that's
the only VM on the system.

Thanks,
HyperScalper

As an extra piece of information, I don't run
the .jnlp directly from a Web Browser.

I just download the jnlp fresh on each launch,
rename it, and and then have a simple shortcut
on Windows to launch, like this:

C:\Windows\SysWOW64\javaws.exe C:\HyperScalper\dukaslive.jnlp

since it's 32-bit Java.

Thanks,
HyperScalper

[cs@devcore ~]$ nslookup dukascopy.com

Non-authoritative answer:
Name: dukascopy.com
Address: 194.8.15.131
Name: dukascopy.com
Address: 194.8.15.113

dukascopy.com resolves to two different addresses via DNS. The DNS cache in your particular JVM isn't happy that the same set of tick data files placed into the cache from the same URL string is coming in on two different IP addresses. It seems to be re-caching the files under the new IP everytime it has a mismatch.

Have you upgraded your JVM recently?
It's either that or the dual DNS resolution is new at dukascopy.
(or you've introduced a new setting within an existing JVM installation)

Thanks for that info, I took your disable cache suggestion...
No, I haven't updated my Java VM version in many weeks...

I'm not seeing the IP != IP any more since taking your
suggestion and disabling the cache in the Java
Control panel.

HyperScalper