The Solr core tracker jobs failed to update the Solr index for the Alfresco repositories (alfresco and archive) multiple times between 16:11 and 16:18. Each failure was caused by the GetModelsDiff API call returning a 404 status code, indicating the models could not be retrieved from Alfresco. Error logs provide the stack traces showing where the exception occurred during the core tracking process.
2019 Pune Data Conference
Software smoke testing is a preliminary level of testing. It makes certain that all of the primary components of a system are functioning correctly. For example, when installing a new secured Hadoop cluster, running a series of quick tests to make sure that things like HDFS and MapReduce are operational can save a lot of headache before enabling Kerberos. Smoke tests can also save you time and embarrassment by making sure that things work before you turn the cluster over to your customer.
In this talk, Michael Arnold will explain the utility of testing Hadoop components after cluster builds and software upgrades. Michael will present code examples that you can use to confirm functionality of Spark, Kudu, HBase, Kafka, MapReduce, etc on your cluster.
In this talk we will make a tour through the most important changes and new features in the language and its standard library, such as enums, single-dispatch generic functions, Tulip, yield from, raise from None, contextlib... And yes, we will talk about Python 3.
GitHub repository with the code of the examples: https://github.com/pablito56/coolest_is_yet_to_come
2019 Pune Data Conference
Software smoke testing is a preliminary level of testing. It makes certain that all of the primary components of a system are functioning correctly. For example, when installing a new secured Hadoop cluster, running a series of quick tests to make sure that things like HDFS and MapReduce are operational can save a lot of headache before enabling Kerberos. Smoke tests can also save you time and embarrassment by making sure that things work before you turn the cluster over to your customer.
In this talk, Michael Arnold will explain the utility of testing Hadoop components after cluster builds and software upgrades. Michael will present code examples that you can use to confirm functionality of Spark, Kudu, HBase, Kafka, MapReduce, etc on your cluster.
In this talk we will make a tour through the most important changes and new features in the language and its standard library, such as enums, single-dispatch generic functions, Tulip, yield from, raise from None, contextlib... And yes, we will talk about Python 3.
GitHub repository with the code of the examples: https://github.com/pablito56/coolest_is_yet_to_come
Andrey Adamovich and Luciano Fiandesio - Groovy dev ops in the cloudDevConFu
The talk is focused on open-source Groovy/Java libraries that we have developed in order to solve our daily DevOps problems including SSH connectivity, cloud instance management, OS image management and integration testing of Puppet modules with the help of Groovy and Junit.
OpenWorld 2018 - Common Application Developer DisastersConnor McDonald
Two of the critical requirements of a database are:
- run fast
- data integrity
The database can achieve these things, but only as long as you understand the mechanisms correctly. If you don't, then things can go downhill fast.
Kotlin is a modern programming language that focuses on clarity, code safety and conciseness. Google officially adopted Kotlin by adding support into Android Studio in 2017 and since then has announced it as the preferred language for Android developers. Android app teams have incrementally added Kotlin code to their projects or have elected to start new Android projects in Kotlin moving forward. Having the app code and UI automation code in the same language helps engineering and QA teams level set on the critical user journeys being tested. Here we share the basics of getting started with automating an Appium test in Kotlin.
Backpressure? Resistance is not futile. RxJS Live 2019Jay Phelps
Backpressure—resistance opposing the desired flow of data through software—from massive scale, to death by a thousand cuts, it's something nearly every software engineer will have to deal with at some point. For some, it’s a frequent problem. But the term itself isn’t nearly as understood and recognized as such. In this talk, we'll discover what backpressure really is, when it happens, and the strategies you can apply to deal with it.
Sangam 18 - Great Applications with Great SQLConnor McDonald
Get more out of the database by exploiting the rich suite of features available with the SQL language. We cover pivot, unpivot, rollup, pagination, error logging, query block naming
Salesforce Integration using REST SOAP and HTTP calloutsRAMNARAYAN R
Salesforce Apex development tutorial: https://bit.ly/33zm1eY
Slides about integration (REST api/SOAP api /HTTP callouts from salesforce)
How to create SOAP API in salesforce APEX and test it with
soapui. How to generate enterprise and class WSDL and invoke methods.
To learn complete salesforce development please check out
this url
Salesforce admin and app builder tutorial :https://bit.ly/2OUgnRy
Salesforce lightning component development tutorial:https://bit.ly/33CUIAL
Testing code that accesses AWS can seem impossible, but it’s really not that hard! Let’s take a look at how we can use Go’s features to write useful tests for this kind of code, without a whole lot of work.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
Andrey Adamovich and Luciano Fiandesio - Groovy dev ops in the cloudDevConFu
The talk is focused on open-source Groovy/Java libraries that we have developed in order to solve our daily DevOps problems including SSH connectivity, cloud instance management, OS image management and integration testing of Puppet modules with the help of Groovy and Junit.
OpenWorld 2018 - Common Application Developer DisastersConnor McDonald
Two of the critical requirements of a database are:
- run fast
- data integrity
The database can achieve these things, but only as long as you understand the mechanisms correctly. If you don't, then things can go downhill fast.
Kotlin is a modern programming language that focuses on clarity, code safety and conciseness. Google officially adopted Kotlin by adding support into Android Studio in 2017 and since then has announced it as the preferred language for Android developers. Android app teams have incrementally added Kotlin code to their projects or have elected to start new Android projects in Kotlin moving forward. Having the app code and UI automation code in the same language helps engineering and QA teams level set on the critical user journeys being tested. Here we share the basics of getting started with automating an Appium test in Kotlin.
Backpressure? Resistance is not futile. RxJS Live 2019Jay Phelps
Backpressure—resistance opposing the desired flow of data through software—from massive scale, to death by a thousand cuts, it's something nearly every software engineer will have to deal with at some point. For some, it’s a frequent problem. But the term itself isn’t nearly as understood and recognized as such. In this talk, we'll discover what backpressure really is, when it happens, and the strategies you can apply to deal with it.
Sangam 18 - Great Applications with Great SQLConnor McDonald
Get more out of the database by exploiting the rich suite of features available with the SQL language. We cover pivot, unpivot, rollup, pagination, error logging, query block naming
Salesforce Integration using REST SOAP and HTTP calloutsRAMNARAYAN R
Salesforce Apex development tutorial: https://bit.ly/33zm1eY
Slides about integration (REST api/SOAP api /HTTP callouts from salesforce)
How to create SOAP API in salesforce APEX and test it with
soapui. How to generate enterprise and class WSDL and invoke methods.
To learn complete salesforce development please check out
this url
Salesforce admin and app builder tutorial :https://bit.ly/2OUgnRy
Salesforce lightning component development tutorial:https://bit.ly/33CUIAL
Testing code that accesses AWS can seem impossible, but it’s really not that hard! Let’s take a look at how we can use Go’s features to write useful tests for this kind of code, without a whole lot of work.
Writing concurrent code that is also correct is unbelievably hard. Naturally, humanity has developed a number of approaches to handle concurrency in the code, starting from basic threads that follow the hardware way to do concurrency to higher level primitives like fibers and work-stealing solutions. But which approach is the best for you? In this session, we'll take a look at a simple concurrent problem and solve it using different ways to manage concurrency: threads, executors, actors, fibers, monadic code with completable futures. All these approaches are different from the simplicity, readability, configuration and management point of view. Some scenarios are better modelled with threads, while sometimes you're better off with actors. We'll discuss the benefits of each approach and figure out when it's worth pursuing in your project.
Why is My Spark Job Failing? by Sandy Ryza of ClouderaJack Gudenkauf
Abstract:
You are not a bad person. But your Apache Spark job is failing. It is running out of memory. It is stalled. It is complaining that no executors have registered or spitting out "Filesystem closed" exceptions with lines upon lines of $anon$1's or being consumed by a swarm of locusts the likes of which have not been seen since Moses crossed the Red Sea. Or it's completing -- 20 times as slow as it should reasonably take. Why? In this talk, you'll learn the internals of Spark jobs, the root causes of such ailments, and tuning strategies for avoiding them.
Why is My Spark Job Failing? by Sandy Ryza of ClouderaData Con LA
Abstract:
You are not a bad person. But your Apache Spark job is failing. It is running out of memory. It is stalled. It is complaining that no executors have registered or spitting out "Filesystem closed" exceptions with lines upon lines of $anon$1's or being consumed by a swarm of locusts the likes of which have not been seen since Moses crossed the Red Sea. Or it's completing -- 20 times as slow as it should reasonably take. Why? In this talk, you'll learn the internals of Spark jobs, the root causes of such ailments, and tuning strategies for avoiding them.
Bio:
Sandy Ryza is a data scientist at Cloudera, an Apache Hadoop committer, and a Spark contributor. Sandy is also the co-author of Advanced Analytics with Spark.
Learn the ins and outs of running background tasks with the popular python module Celery. We'll hit the ground running. With everything you need to know to run your first task, to scaling your stack to run millions each day.
Why is web application programming so difficult? Is it javascript fault? Is it our fault? Time to take the red pill and wake up in the real, event driven world. A world where if you can dodge the bullets of skyrocketing complexity, your programs can be made scalable, fault tolerant, extensible and just beautiful.
Why is web application programming so difficult? Is it javascript fault? Is it our fault? Time to take the red pill and wake up in the real, event driven world. A world where if you can dodge the bullets of skyrocketing complexity, your programs can be made scalable, fault tolerant, extensible and just beautiful.
Presented by Rafal Kuć, Consultant and Software engineer, , Sematext Group, Inc.
Even though Solr can run without causing any troubles for long periods of time it is very important to monitor and understand what is happening in your cluster. In this session you will learn how to use various tools to monitor how Solr is behaving at a high level, but also on Lucene, JVM, and operating system level. You'll see how to react to what you see and how to make changes to configuration, index structure and shards layout using Solr API. We will also discuss different performance metrics to which you ought to pay extra attention. Finally, you'll learn what to do when things go awry - we will share a few examples of troubleshooting and then dissect what was wrong and what had to be done to make things work again.
1. 16:11:47,370 WARN [org.apache.solr.handler.component.SpellCheckComponent] No
queryConverter defined, using default converter
16:11:47,729 WARN [org.apache.solr.handler.component.SpellCheckComponent] No
queryConverter defined, using default converter
16:17:31,484 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050000 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:17:31,484 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-archive
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050001 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:17:31,484 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-alfresco
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050000 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050000 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:17:31,484 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-archive
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050001 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
2. org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050001 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:17:45,025 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-archive
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050002 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:17:45,025 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-archive
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050002 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050002 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:17:45,025 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050003 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
3. at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:17:45,025 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-alfresco
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050003 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050003 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:00,017 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050004 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:00,017 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-alfresco
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050004 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050004 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:00,032 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-archive
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050005 GetModelsDiff return
4. status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:00,032 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-archive
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050005 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050005 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:15,024 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-archive
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050006 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:15,024 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-archive
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050006 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050006 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
5. at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:15,024 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050007 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:15,024 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-alfresco
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050007 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050007 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:30,016 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-archive
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050008 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:30,016 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-archive
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050008 GetModelsDiff
6. return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050008 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more
16:18:30,016 ERROR [org.quartz.core.JobRunShell] Job Solr.CoreTracker-alfresco
threw an unhandled Exception:
org.alfresco.error.AlfrescoRuntimeException: 02050009 GetModelsDiff return
status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
16:18:30,016 ERROR [org.quartz.core.ErrorLogger] Job (Solr.CoreTracker-alfresco
threw an exception.
org.quartz.SchedulerException: Job threw an unhandled exception. [See nested
exception: org.alfresco.error.AlfrescoRuntimeException: 02050009 GetModelsDiff
return status is 404]
at org.quartz.core.JobRunShell.run(JobRunShell.java:227)
at
org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)
Caused by: org.alfresco.error.AlfrescoRuntimeException: 02050009 GetModelsDiff
return status is 404
at
org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1036)
at
org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1790)
at
org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1129)
at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:475)
at
org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
... 1 more