-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP 500 error on job execution: "Typed property Configuration::$executorSettings must not be accessed before initialization" #204
Comments
Just as a hint as it is for sure not the correct solution: If I enhance the original code
in
al least my code from previous version is running again |
Hi @ctippler, would the change described in my last comment be an acceptable fix of the issue? If so, I could create a PR. If not, do you have a better proposal to support start of jobs without predefined configurations? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I run into this issue since migration to pimcore 11 (and therefore ProcessManager 5.x). It seems it's an issue that I do not use predefined configuration but start the job directly and fill some data in the callback function. With ProcessManager 4.x I used parameter
$configId = null
which gave an error in new version so I use empty string now:executeJob
recognizes there is noConfiguration
and creates a new one but with this onegetExecutorClassObject
fails:getExecutorClassObject
(method ofConfiguration
class) is failing on callingsetDataFromResource
by passing its own instance created inexecuteJob
:setDataFromResource
inAbstractExecuter
class tries to get Executer settingsgetExecutorSettings
(method ofConfiguration
class) finally raises the exception as global variable$this->executorSettings
is not initialized yet:I assume, having no predefined configuration is still a valid use case as
executeJob
handles that by creating a newConfiguration
instance. It just seems that this new instance is not initialized in a functional wayThe text was updated successfully, but these errors were encountered: