7 Replies Latest reply on Feb 2, 2010 4:41 PM by clebert.suconic

    Address Setting issue on deployement packages

    clebert.suconic

      When we get integrated on the application server, users will be able to deploy destinations, security settings, and destination settings with their packages.

       

       

      To explain what I think is an issue, let me user an example:

       

      Developer A created a project, containing a bunch of stuff and:

      - JMS Destination Orders

      - Address Setting on /jms/Orders, setting page-size to 10 MiB

       

       

      Developer B copied that project (to his initial version) and will package a bunch of stuff and:

      -JMS Destination ManufacturingOrder

      - Address Setting on /jms/Orders, setting page-size to 100 Kib (The user forgot to edit the name here)

       

       

      As a result you have two distinct applications on the same application server,

      however the setting on B will affect the setting on A.

       

      In the end the user will be complaining about an eventual bug that will only happen in production. Unless he's able to look at the other application it will be kind of hard to discover what's going on.

       

       

      And that's the reason I don't like how address-settings would be deployed on the user's jars.

       

       

      I'm ok with the address-settings in a centralized place. Thinking as an user I actually like it, as it's easy to look at it and debug configuration issues.

       

      But letting independent application affecting each other settings is an issue IMO and it might be hard to identify issues on large instalations when lots of application developers start to step on each other's feet.

       

       


        • 1. Re: Address Setting issue on deployement packages
          ataylor

          I think the altrenative, that you suggested, was to associate address settings with a queue, similar to how JBM 1.4 is used. I think this is wrong, firstly we should only have a different way to deploy stuff in the AS than in Standalone. secondly, these settings are on an address not a queue. adding it to queue will only confuse users more.

           

          I think most users will just use default settings anyway.

          • 2. Re: Address Setting issue on deployement packages
            clebert.suconic

            To avoid this, I wouldn't let users to deploy queues.xml on the MDB jar.

             

            And I would add an queue-seeting and security setting on the JMS element, such as:

             


               <queue name="exampleQueue">
                  <entry name="/queue/exampleQueue"/>
                  <security>
                       ...blablablabla...
                  </security>
                  <settings>
                      <page-max-size/>
                      <whatever-else-is-needed-here/>
                  </settings>
               </queue>
            
            

             

            This way the user would be locked with his settings and his queues.

             

            At the implementation those settings would be applied towards the address of the JMS queue (or topic)

            • 3. Re: Address Setting issue on deployement packages
              clebert.suconic

              My concern is, the user has the power to do something hard to catch.

              Murphy says it will eventually happen.

               

              I'm just raising my concern. If everybody thinks this is not an issue (as long as  you guys understand what I'm raising here), I will just accept it.

              • 4. Re: Address Setting issue on deployement packages
                ataylor

                My main issue are

                 

                1.) it implies that the settings are associated with queues which will only confuse users.

                2.) it is different to how we deploy standalone.

                • 5. Re: Address Setting issue on deployement packages
                  clebert.suconic

                  1) We would do it only to JMS Users. If users want to deploy a generic config they should do it on the main config file, not individually on JARs messing with other applications.

                   

                  2) we would also let standalone users to deploy JMS destinations this way if we get into an agreement.

                  • 6. Re: Address Setting issue on deployement packages
                    timfox

                    We shouldn't have any different config in JBoss AS compared to standalone.

                     

                    Let's keep this simple, address settings is fine

                    • 7. Re: Address Setting issue on deployement packages
                      clebert.suconic

                      I don't want to create a different way for JBAS. I would change the jms-queue on both standalone and application server.

                       

                      I'm raising an issue with multiple applications messing up with address-settings, and I don't think the user should be able to mess with that.

                       

                       

                      If you don't think that's an issue, fine... I don't like it but I will accept it.