2 Replies Latest reply on Jan 30, 2013 2:32 PM by sboscarine

    -Dorg.jboss.as.logging.per-deployment=false - Can I set it permanently via CLI?

    sboscarine

      On AS7/EAP6, we've discovered that if we don't set -Dorg.jboss.as.logging.per-deployment=false, all Spring exceptions get swallowed up and no one has a clue why their deploy failed.  We pretty much have to set it on all servers. 

       

      Is there a way to set  -Dorg.jboss.as.logging.per-deployment=false permanently via CLI?

       

      I recently discovered that I can set -b-0.0.0.0 permanently via CLI with:

      /interface=public:write-attribute(name=inet-address,value="${jboss.bind.address:0.0.0.0}")
      

      ...which was a huge game changer for us...made everyone's life easier. 

      Is there something similar for properties? 

      Are properties even stored in standalone/domain.xml?

        • 1. Re: -Dorg.jboss.as.logging.per-deployment=false - Can I set it permanently via CLI?
          jamezp

          You can indeed set it via CLI. You just need to set it as a system property.

           

          /system-property=org.jboss.as.logging.per-deployment:add(value=false)
          

           

          --

          James R. Perkins

          • 2. Re: -Dorg.jboss.as.logging.per-deployment=false - Can I set it permanently via CLI?
            sboscarine

            Thank you so much!  That is a huge help.

             

            For anyone else reading, I run:

             

            #Set your JBoss instance to allow remote requests...so your coworkers can see your applications #Permanently set -b=0.0.0.0
            /interface=public:write-attribute(name=inet-address,value="${jboss.bind.address:0.0.0.0}")
            
            #Set your JBoss Admin GUIto allow remote requests...so your coworkers to help you configure your instance.
            #Permanently set -bmanagement=0.0.0.0
            /interface=management:write-attribute(name=inet-address,value="${jboss.bind.address:0.0.0.0}")
            
            #If you don't set this system property, the output log will swallow Spring exceptions
            #Permanently set -Dorg.jboss.as.logging.per-deployment=false
            /system-property=org.jboss.as.logging.per-deployment:add(value=false)
            
            

             

            On developer and CI machines, and it makes a huge difference.  Now we don't have to remember which params to pass to standalone.sh