cal 1.11.1 in TYPO3 7.6.22
the backand module cal indexer is working as expected, all recurring events will bi written in the database.
but the scheduler task Indexer for recurring events (cal) does not work. I filled out with all necessairy data: Folder with cal data, page with calendar plugin, index start and stop. When i manuelly start the indexer i get this error:
Execution of task "Indexer for recurring events (cal)" failed with the following message: PHP Warning: Creating default object from empty value in /typo3_src-7.6.22/typo3/sysext/frontend/Classes/ContentObject/ContentObjectRenderer.php line 824
When i change the version to the last master in git, the error message is gone but the task does nothing.
Any idea?
Thanks!
OK, my fault ... but perhaps it is interesting for others because it nearly is a kind of a trap ...
You have to give the scheduler the date or the period, e.g. -1 years and +1 years. I wrote in the second line + 1 years (see the blank between + and 1 ... ) This tiny fault results in the error message because the time period was not defined. Well ...
Now it works.
Related
I have created task on controller and there is loop which is loading for 100 times.
Now I want to load it for 25 times and pause that loop for 1 min and after that it will execute next 25 items same for next 25.
I have checked it with sleep but its not working.
Can you please advise me if is there any way on plugin event or any other method.
Thanks
This is actually unrelated to Joomla! Since you're creating a long running process you need to start it with something else than a browser. A CRON job is a good idea here if you want to execute this operation multiple times. Otherwise it can run via command line. Make sure the max_execution time setting of PHP does not cause any trouble.
If you still need this within Joomla please have a look at the CLI documentation.
https://docs.joomla.org/How_to_create_a_stand-alone_application_using_the_Joomla!_Platform
I have a MFT pipeline as below:
FaceDraw and FaceDetect are custom MFTs. This pipeline is running fine for first few frames and all of sudden it exits.
I tried analyzing it using MFTrace and narrowed to a spurious evenet as below:
CMFPresentationClockDetours::GetTime #0000004BF1114E50 Time 20687020hns
This is not expected and suddently popping up. This event further leading to below set of events that are causing pipe to drain-off
CMFClockStateSinkDetours::OnClockStop #0000004BF98AFE88 System time 668039142ms
CMFClockStateSinkDetours::OnClockStop #0000004BF98AFB28 System time 668039142ms
CMFTransformDetours::ProcessMessage #0000004BF1838970 Message type=0x00000000 MFT_MESSAGE_COMMAND_FLUSH, param=00000000
So the question is, what are the ways to figure out the initiator for this event? Are there any better tools for debugging issues like this?
Initially I suspected EVR, but the removal of EVR from the pipeline is not making any difference.
We are running Algolia 1.5.2 in our Magento store, things seem to have been running fine for months now. On a routine site check I noticed that the algolia.log file and system.log file are growing at an alarming rate. Thousands of errors a day in the system.log. All the same:
2016-04-28T13:51:16+00:00 DEBUG (7): Array to string conversion/mnt/nfs/www.ourdomain.com/files/html/app/code/community/Algolia/Algoliasearch/Helper/Entity/Producthelper.php )
And the algolia.log file is growing at almost the same rate but with this error
2016-04-28T22:18:40+00:00 DEBUG (7): >>>>> BEGIN CREATE RECORD 10512 1 (Our Site)
2016-04-28T22:18:40+00:00 DEBUG (7): Product type (bundle, mapped to: bundle)
2016-04-28T22:18:40+00:00 DEBUG (7): <<<<< END CREATE RECORD 10512 1 (Our Site) (0.10960912704468sec)
2016-04-28T22:18:40+00:00 DEBUG (7): <<<<< END CREATE RECORDS 1 (Our Site) (0.10998892784119sec))
It's unclear to us if this is just a normal feature with the Algolia debug? Is there a way to turn off debug? Is there a "best debug method" for these issues. It seems that thousands of repeated errors a day has to be a problem that needs to be fixed.
I have a few questions regarding quartz.net.
What is it that keeps track of if there has been a missfire situation i Quartz.net?
What happens in the following scenarios:
If a job is run but cannot finnish due to some bug, does that count as a missfire or not?
What happens if i republish the solution, is the tracking reset?
Is there a way to receive information on what the scheduler has done and not been able to do?
I have the following code in my Run method:
IJobDetail dailyUserMailJob = new JobDetailImpl("DailyUserMailJob", null, typeof(Jobs.TestJob));
ITrigger trigger = TriggerBuilder.Create()
.WithIdentity("trigger1", "group1")
.WithCronSchedule("0 0 4 1 * ?", x => x.WithMisfireHandlingInstructionFireAndProceed())
.Build();
this.Scheduler.ScheduleJob(dailyUserMailJob, trigger);
this.Scheduler.Start();
The job is supposed to run the first every month on 4 am.
When testing I have set the system clock so that the jobb is missed for one month. According to the documentation when using WithMisfireHandlingInstructionFireAndProceed the job should be run the first thing that happens, but it dosent. Is there something wrong with the code or could it be some other reason the job is not run when using WithMisfireHandlingInstructionFireAndProceed() ?
If a job is missed, there is logic to bring it back. However, there is a "window" on how far back to go.
<add key="quartz.jobStore.misfireThreshold" value="60000"/>
You can increase this value.
If you have an ADOStore, misfires are persisted. Thus "if the power goes out", when restarting...you can recover from misfires.
If you have a RamStore...if "the power goes out", everything was in memory to begin with..so you won't get mis-fire handling, because everything was "in memory" and the memory is lost.
..
If you use Sql Server (AdoStore) and put a Profiler/Trace on it, you'll see the engine "poll" for misfires.......with a "go back this far in time" based on the misfireThreshold.
See this link:
http://nurkiewicz.blogspot.com/2012/04/quartz-scheduler-misfire-instructions.html
for more detailed info. Which has a "withMisfireHandlingInstructionFireAndProceed" note.
I'm using EF6 rc1 with Code First strategy, without precompiled views and the problem is:
If I compile and run the exe application it takes like 15 seconds to run the first query (that's okay, since I'm still working on the pre-generated views). But if I use Visual Studio 2013 Preview to Debug the exact same application it takes almost 2 minutes BEFORE running the first query:
Dim Context = New MyEntities()
Dim Query = From I in Context.Itens '' <--- The debug takes 2 minutes in here
Dim Item = Query.FirstOrDefault()
Is there a way to remove this extra time? Am I doing something wrong here?
Ps.: The context itself is not complicated, its just full with 200+ tables.
Edit: Found out that the problem is that during debug time the EF appears to be generating the Views ignoring the pre-generated ones.
Using the source code from EF I discovered that the property:
IQueryProvider IQueryable.Provider
{
get
{
return _provider ?? (_provider = new DbQueryProvider(
GetInternalQueryWithCheck("IQueryable.Provider").InternalContext,
GetInternalQueryWithCheck("IQueryable.Provider").ObjectQueryProvider));
}
}
is where the time is being consumed. But this is strange since it only takes time in debug. Am I missing something here?
Edit: Found more info related to the question:
Using the Process Monitor (by Sysinternals) I found out that there its the 'desenv.exe' process that is consuming tons of time. To be more specific its consuming time with an 'Thread Exit'. It repeats the Thread Exit stack 36 times. I don't know if this info is very useful, but I saved a '.cvs' with the stack, here is his body: [...] (edit: removed the '.cvs' body, I can post it again by the comments if someone really think its going to be useful, but it was confusing and too big.)
Edit: Installed VS2013 Ultimate and Entity Framework 6 RTM. Installed the Entity Framework Power Tools Beta 4 and used it to generate the Views. Nothing changed... If I run the exe it takes 20 seconds, if I 'Start' debugging it takes 120 seconds.
Edit: Created a small project to simulate the error: http://sdrv.ms/16pH9Vm
Just run the project inside the environment and directly through the .exe, click the button and compare the loading time.
This is a known performance issue in Lazy (which EF is using) when the debugger is attached. We are currently working on a fix (the current approach we are looking at is removing the use of Lazy). We hope to ship this fix in a patch release soon. You can track progress of this issue on our CodePlex site - http://entityframework.codeplex.com/workitem/1778.
More details on the coming 6.0.2 patch release that will include a fix are here - http://blogs.msdn.com/b/adonet/archive/2013/10/31/ef6-performance-issues.aspx
I don't know if you have found the solution. But in my case, I had similar issue which wasted me close to a week after trying different suggestions. Finally, I found a solution by changing my web.config to optimizeCompilations="true" and performance improved dramatically from 15-30 seconds to about 2 seconds.