|
| Possible problems with JForex internal jfx memory cache |
|
hyperscalper
|
| Post subject: Possible problems with JForex internal jfx memory cache |
Post rating: 0
|
Posted: Wed 19 Mar, 2014, 17:26
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02
Posts: 656
Location: United States, Durham, NC
|
|
Live platform FXDD ver. 2.32.4
JForex API ver. 2.9.6.2
I don't have a reproducible scenario for this, but have
had problems with JForex platform not using the latest
.jfx compiled versions for Local Run.
I deleted the on-disk .jfx file, then compiled again, but
new version was not run. On full platform restart the
new .jfx version was being run.
I assume the run information is held in an in-memory
cache of some kind, and that cache may not be releasing
older versions under certain circumstances.
If any changes have been made recently in the in-memory
jfx object cache, you might want to review them.
HyperScalper
|
|
|
|
|
 |
|
hebasto
|
| Post subject: Re: Possible problems with JForex internal jfx memory cache |
Post rating: 0
|
Posted: Thu 20 Mar, 2014, 06:23
|
|
User rating: 96
Joined: Mon 09 Sep, 2013, 07:09
Posts: 287
Location: Ukraine, SHostka
|
This topic could regard to your issue.
|
|
|
|
|
|
|
hyperscalper
|
| Post subject: Re: Possible problems with JForex internal jfx memory cache |
Post rating: 0
|
Posted: Fri 28 Mar, 2014, 21:02
|
|
User rating: 98
Joined: Mon 23 Jul, 2012, 02:02
Posts: 656
Location: United States, Durham, NC
|
|
I'll withdraw this, as there is a possibility that Thread issues could
have resulted in residual code not being released on Strategy
close.
I am aware, and others should also be aware, that they MUST
release any created Thread resources, as well as any Swing
GUI components which may have been created by the
Strategy instance, within the onStop() of the Strategy module.
Failure to do this can result in unexpected behavior.
HyperScalper
|
|
|
|
|
|
 
|
Pages: [
1
]
|
|
|
|
|
