Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-9219

JBERET000013: Failed to destroy artifact Proxy for view class

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.1.0.DR14
    • 7.1.0.DR13
    • Batch
    • None
    • Hide

      Deploy batchlet-example.jar which is attached
      Run the job using CLI:

      /deployment=batchlet-example.jar/subsystem=batch-jberet:start-job(job-xml-name=ejb-batchlet)

      Look into the server log

      Show
      Deploy batchlet-example.jar which is attached Run the job using CLI: /deployment=batchlet-example.jar/subsystem=batch-jberet:start-job(job-xml-name=ejb-batchlet) Look into the server log

    Description

      I'm not sure what exactly are the conditions when this appears, but when a batchlet instance is being discarded after a job execution doesn't need it anymore, I often see this warning:

      15:19:06,736 WARN  [org.jberet] (Batch Thread - 8) JBERET000013: Failed to destroy artifact Proxy for view class: PrintInjectedPropertyBatchlet of EJB: PrintInjectedPropertyBatchlet: java.lang.NullPointerException
	at org.jberet.creation.AbstractArtifactFactory.invokeAnnotatedLifecycleMethod(AbstractArtifactFactory.java:99)
	at org.jberet.creation.AbstractArtifactFactory.destroy(AbstractArtifactFactory.java:44)
	at org.jberet.runtime.context.JobContextImpl.destroyArtifact(JobContextImpl.java:205)
	at org.jberet.runtime.runner.BatchletRunner.run(BatchletRunner.java:115)
	at org.jberet.runtime.runner.StepExecutionRunner.runBatchletOrChunk(StepExecutionRunner.java:229)
	at org.jberet.runtime.runner.StepExecutionRunner.run(StepExecutionRunner.java:147)
	at org.jberet.runtime.runner.CompositeExecutionRunner.runStep(CompositeExecutionRunner.java:164)
	at org.jberet.runtime.runner.CompositeExecutionRunner.runFromHeadOrRestartPoint(CompositeExecutionRunner.java:88)
	at org.jberet.runtime.runner.JobExecutionRunner.run(JobExecutionRunner.java:60)
	at org.wildfly.extension.batch.jberet.deployment.BatchEnvironmentService$WildFlyBatchEnvironment$1.run(BatchEnvironmentService.java:185)
	at org.wildfly.extension.requestcontroller.RequestController$QueuedTask$1.run(RequestController.java:497)
	at org.jberet.spi.JobExecutor$3.run(JobExecutor.java:161)
	at org.jberet.spi.JobExecutor$1.run(JobExecutor.java:99)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:745)
	at org.jboss.threads.JBossThread.run(JBossThread.java:320)

      Attachments

        Issue Links

          is blocked by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-9249 Upgrade JBeret from 1.2.2.Final to 1.2.3.Final

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBERET-248 NullPointerException when using artifacts with default-package

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              cfang@redhat.com Cheng Fang
              jmartisk@redhat.com Jan Martiska
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: