One of my clients sent this. There is a simple, tested strategy running with
nothing unusual going on.

Somehow, the JForex platform got itself into a situation where task execution
queue got "stuck". I'm sure this is just an unusual situation which I've
never observed before.

I'm just reporting this, but I wonder don't those queues have "time out"
and self-cleaning characteristics?

I have no other information concerning how/why this would have occurred.
If there is some logfile we should submit, let me know.

HyperScalper

Apparently there is something holding up the onBar execution such that the incoming bars get queued up.

Thanks for the clue.

Well, as I said, it's thoroughly tested code, but I suspect there may be some "cleaning"
needed on the client's machine.

We'll nuke out the tick/bar caches and JForex entirely, and check over the system.

I run the same code for days on end and never see any issues.

He does use a few more currency pairs, but I can't otherwise see any reason for this.

He repeated that the problem has come back and I said we should tidy up his system
before reporting anything back to this forum.

HyperScalper

OK, forgot to tell you what we had to do.

The JForex tick/bar cache was so huge that JForex was unable to clear it out.

So we manually nuked the entire .cache area. It was like 10gb or so...

After that, restarted JForex platform, which returned to normal.

So I can only say that the tick/bar cache must have been "corrupted"
in such a way that the onBar callback was frozen.

Oh, well, as they say "sh***t happens" All's well that ends well.

HyperScalper