Uploaded image for project: 'Application Server 3 4 5 and 6'
  1. Application Server 3 4 5 and 6
  2. JBAS-5284

Cannot use a scoped loader repository in deploy-hasingleton deployments

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • JBossAS-4.2.1.GA, JBossAS-4.2.2.GA
    • Clustering
    • None
    • Workaround Exists
    • Hide

      Use the HASingleton barrier controller as discussed on the forum thread. Note that this will not work properly for EJB deployments.

      Show
      Use the HASingleton barrier controller as discussed on the forum thread. Note that this will not work properly for EJB deployments.

      If you try to add a loader-repository element to a deploy-hasingleton deployment, you get something like this:

      Only the root deployment can set the loader repository, ignoring config=LoaderRepositoryConfig(repositoryName: jboss.dataintegration:sar=dataintegration.sar, repositoryClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3, configParserClassName: org.jboss.mx.loading.HeirarchicalLoaderRepository3ConfigParser, repositoryConfig: java2ParentDelegation=false)

      I suspect this is because the deploy-hasingleton dir itself is being treated as the root deployment.

            bstansbe@redhat.com Brian Stansberry
            bstansbe@redhat.com Brian Stansberry
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: