Uploaded image for project: 'Weld'
  1. Weld
  2. WELD-1067

Thread safety issue in BeansClosure

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 1.1.6.Final, 2.0.0.Alpha2
    • 1.1.4.Final
    • None
    • None
    • Hide

      See linked issue.

      Show
      See linked issue.

    Description

      The getClosure() method does not synchronize on get. This leads to multiple Weld deployments on AS7 calling the get method, all at once and leads to the following error:

      java.lang.NullPointerException
      at org.jboss.weld.manager.BeanManagerImpl.getMostSpecializedBean(BeanManagerImpl.java:931)
      at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:605)
      at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:228)
      at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:207)
      at org.jboss.weld.bootstrap.events.AbstractContainerEvent.fire(AbstractContainerEvent.java:75)
      at org.jboss.weld.bootstrap.events.AbstractDefinitionContainerEvent.fire(AbstractDefinitionContainerEvent.java:46)
      at org.jboss.weld.bootstrap.events.BeforeBeanDiscoveryImpl.fire(BeforeBeanDiscoveryImpl.java:46)
      at org.jboss.weld.bootstrap.WeldBootstrap.startInitialization(WeldBootstrap.java:322)
      at org.jboss.as.weld.WeldContainer.start(WeldContainer.java:80)
      at org.jboss.as.weld.services.WeldService.start(WeldService.java:89)
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1824)
      at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1759)
      at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
      at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
      at java.lang.Thread.run(Unknown Source)

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-10116 Issues that affect AS7/EAP integration to tools

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. JBIDE-11317 When deploying the GWT Kitchensink project to EAP6 Beta1, a NullPointerException occurs.

          • 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.
          • Closed

          Activity

            People

              ajustin@redhat.com Ales Justin
              mageshbk_jira Magesh Bojan (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: