You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
getExecutorClassObject (method of Configuration class) is failing on calling setDataFromResource by passing its own instance created in executeJob:
public function getExecutorClassObject(): AbstractExecutor
{
if (!isset($this->executorClassObject)) {
$className = $this->getExecutorClass();
$class = new $className();
$class->setDataFromResource($this);
setDataFromResource in AbstractExecuter class tries to get Executer settings
public function setDataFromResource(Configuration $configuration): Configuration
{
$settings = $configuration->getExecutorSettings();
getExecutorSettings (method of Configuration class) finally raises the exception as global variable $this->executorSettings is not initialized yet:
public function getExecutorSettings(): string
{
return $this->executorSettings;
}
I assume, having no predefined configuration is still a valid use case as executeJob handles that by creating a new Configuration instance. It just seems that this new instance is not initialized in a functional way
The text was updated successfully, but these errors were encountered:
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?
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: