This content has been marked as final.
Show 2 replies
-
1. Re: -Dorg.jboss.as.logging.per-deployment=false - Can I set it permanently via CLI?
jamezp Jan 30, 2013 2:00 PM (in response to sboscarine)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 Jan 30, 2013 2:32 PM (in response to jamezp)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