Uploaded image for project: 'Jopr (CLOSED)'
  1. Jopr (CLOSED)
  2. JOPR-425

Better support for management of applications outside the deploy directory

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Plugin - JBoss AS 5
    • Labels:
      None

      Description

      Raising this feature request based on the original problem at the bottom of this mail thread

      ----- Original Message -----
      From: "Emanuel Muckenhuber" <emuckenh@redhat.com>
      To: "Mike M. Clark" <miclark@redhat.com>
      Cc: "Ian Springer" <ian.springer@redhat.com>, jboss-support-jbnem@redhat.com
      Sent: Thursday, December 3, 2009 3:12:57 AM GMT -06:00 US/Canada Central
      Subject: Re: Admin-console management of applications outside the deploy directory

      On 12/02/2009 11:19 PM, Mike M. Clark wrote:
      > Hey guys,
      >
      > Haven't looked at the code, but it appears that the last uploadURIs value listed wins. I get the same problem as described in the case if I have a testappdir and testappdir2 updating a deployment in testappdir. The updated deployment ends up in testappdir2.
      >
      > So, only one upload directory allowed?
      >

      Hmm, yeah more or less. In general there should be up to 3 available
      "profiles" where you can distribute (upload) content to. The
      "deployers", "applications" and "farm". But you can only pick one of the
      "applicationURIs" and set it as uploadURI so far.

      We are are working on a better configuration for this, although this is
      currently scheduled for AS6.

      > Cheers,
      > Mike C.
      >
      >
      > ----- Original Message -----
      > From: "Ian Springer"<ian.springer@redhat.com>
      > To: "Emanuel Muckenhuber"<emuckenh@redhat.com>
      > Cc: "Mike M. Clark"<miclark@redhat.com>, jboss-support-jbnem@redhat.com
      > Sent: Wednesday, December 2, 2009 3:17:58 PM GMT -06:00 US/Canada Central
      > Subject: Re: Admin-console management of applications outside the deploy directory
      >
      > Thanks, Emanuel.
      >
      > For 2), what happens if you specify more than one URL. Will the
      > deployment manager handle this situation gracefully, or will it try to
      > deploy both apps, even though they're identical?
      >
      > On 12/2/2009 3:58 PM, Emanuel Muckenhuber wrote:
      >> Well this was more a problem of configuration. There should be 2 ways
      >> to change this behavior though:
      >>
      >> 1) change the ordering of the applicationURIs
      >>
      >> 2) There is a property on the DeploymentRepositoryFactory (in
      >> profile.xml) where you should be able specify uploadURIs as well:
      >>
      >> <bean name="DefaultDeploymentRepositoryFactory"
      >> class="org.jboss.system.server.profileservice.repository.DefaultDeploymentRepositoryFactory">
      >>
      >> <!-- .... -->
      >> <property name="uploadURIs">
      >> <list elementClass="java.net.URI">
      >> <value>file:///home/miclark/testappdir</value>
      >> </list>
      >> </property>
      >> </bean>
      >>
      >>
      >> Emanuel
      >>
      >> On 12/02/2009 09:29 PM, Ian Springer wrote:
      >>> I think that may actually be the expected behavior. I remember asking
      >>> Emanuel about this a while back, and I think he said that when there are
      >>> multiple deploy dirs defined and you update a deployment, the first
      >>> deploy dir in the list is always used. Emanuel, can you confirm this?
      >>>
      >>> On 12/2/2009 10:38 AM, Mike M. Clark wrote:
      >>>> Hey guys,
      >>>>
      >>>> Have a case [1] where the customer is using a secondary applicationURI
      >>>> in his profile.xml by adding a second value in the<applicationURIs>
      >>>> list. For example,
      >>>>
      >>>> <bean name="BootstrapProfileFactory"
      >>>> class="org.jboss.system.server.profileservice.repository.StaticProfileFactory">
      >>>>
      >>>>
      >>>> <property
      >>>> name="bindingsURI">${jboss.server.home.url}conf/bindingservice.beans</property>
      >>>>
      >>>>
      >>>> <property
      >>>> name="bootstrapURI">${jboss.server.home.url}conf/jboss-service.xml</property>
      >>>>
      >>>>
      >>>> <property
      >>>> name="deployersURI">${jboss.server.home.url}deployers</property>
      >>>> <property name="applicationURIs">
      >>>> <list elementClass="java.net.URI">
      >>>> <value>${jboss.server.home.url}deploy</value>
      >>>> <value>file:///home/miclark/testappdir</value> <!-- Added -->
      >>>> </list>
      >>>> </property>
      >>>> <property
      >>>> name="attachmentStoreRoot">${jboss.server.data.dir}/attachments</property>
      >>>>
      >>>>
      >>>> <property name="profileFactory"><inject bean="ProfileFactory"
      >>>> /></property>
      >>>> </bean>
      >>>>
      >>>> He is able to see the application in the Admin console. However, when
      >>>> he tries to update the application, the updated version is placed in
      >>>> the deploy directory (the old is removed from the secondary
      >>>> directory). The location of the update appears to be dependent on the
      >>>> order of the elements in the applicationURIs property. If you reverse
      >>>> the order, updates work fine for the testappdir, but no longer for the
      >>>> deploy directory.
      >>>>
      >>>> So, finally, my question, is this by design? Is it assumed that all
      >>>> applications managed should be in the first applicationURIs element
      >>>> (deploy, normally)? If not, I'll open a jira, if so, we'll need to get
      >>>> that in the documentation.
      >>>>
      >>>> Cheers,
      >>>> Mike C.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  ccrouch Charles Crouch
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated: