Trying to publish a set of a few static/dynamic components in Tridion Sites 9.6 DEV environment. During publishing, receiving the error "creating bean with name 'TridionUnzipStep'" frequently. This issue mostly occurred during the publishing of dynamic components.
I am attaching a sample snippet of error logs below.
ERROR [deployer-combined-service,------,development,live] 14 --- [eue)-6-thread-5] c.s.d.d.w.queue.imp
l.CommandQueuePoller : Could not process command: JSONCommand{verbs=[Content], action='TridionBootstrap', binaryIds=[XXX-XXXXX-XX.Content.zip], executionId='XXX:X-XXXXXX-XXXXX', properties={}}
org.springframework.beans.factory.BeanCreationNotAllowedException: Error creating bean with name 'TridionUnzipStep': Singleton bean cr
eation not allowed while singletons of this factory are in destruction (Do not request a bean from a BeanFactory in a destroy method i
mplementation!)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:220)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:319)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:616)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeansOfType(DefaultListableBeanFactory.java:604)
at org.springframework.context.support.AbstractApplicationContext.getBeansOfType(AbstractApplicationContext.java:1227)
at com.sdl.delivery.deployer.engine.step.SpringAwareExecutableStepFactory.resolveExecutableStep(SpringAwareExecutableStepFactory.java
:49)
at com.sdl.delivery.deployer.engine.step.SpringAwareExecutableStepFactory.create(SpringAwareExecutableStepFactory.java:38)
at com.sdl.delivery.deployer.engine.step.BasicExecutableStepFactoryManager.getStep(BasicExecutableStepFactoryManager.java:44)
at com.sdl.delivery.deployer.engine.pipeline.actor.StepActor.execute(StepActor.scala:67)
at com.sdl.delivery.deployer.engine.pipeline.actor.StepActor.com$sdl$delivery$deployer$engine$pipeline$actor$StepActor$$processStep(S
tepActor.scala:58)
at com.sdl.delivery.deployer.engine.pipeline.actor.StepActor$$anonfun$receive$1.applyOrElse(StepActor.scala:41)
at akka.actor.Actor.aroundReceive(Actor.scala:539)
at akka.actor.Actor.aroundReceive$(Actor.scala:537)
at com.sdl.delivery.deployer.engine.pipeline.actor.StepActor.aroundReceive(StepActor.scala:27)
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:614)
at akka.actor.ActorCell.invoke(ActorCell.scala:583)
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:268)
at akka.dispatch.Mailbox.run(Mailbox.scala:229)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Can someone please suggest any workaround on above issue!.
This issue mostly occurred during the publishing of dynamic components.
is correct - and it's not happening all the time with dynamic components (or batches where dynamic components are included) then I'd be switching up the log-level and looking some more at the deployer. Simple things to test ... is it when publishing over 'x' items; is it when others are publishing so the publish throughput is higher; is it related to the size of the items being published (remembering that DCPs often trigger larger publish tasks);