Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-2876

AbstractComponentRegistry.getComponent can return an incomplete component

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • 5.2.2.Final
    • Transactions
    • None

      AbstractComponentRegistry.getComponent doesn't have any locking, so it's possible for a thread to retrieve a component while another thread is injecting that component's dependencies.

      Normally this isn't a problem, because the global registry is locked during cache manager startup, and the cache registry is locked during cache startup. However, some global components are only created "on-demand", because a cache component depends on them, and this can happen if someone uses getComponent instead of getOrCreateComponent.

              Unassigned Unassigned
              dberinde@redhat.com Dan Berindei (Inactive)
              Archiver:
              rhn-support-adongare Amol Dongare

                Created:
                Updated:
                Resolved:
                Archived: