2 Replies Latest reply on Oct 10, 2013 8:43 AM by Vikram Murugesan

    org.jboss.boot.log.file and logging.configuration system properties in VM arguments

    Vikram Murugesan Newbie



      I am trying to setup a standalone 2 node cluster. So I copied the standalone directory in my jboss installation directory and created two copies namely 'nodeA' and 'nodeB'. Then I created servers for these two nodes in my IDE, After creating these two servers, I checked the VM arguments (via 'Open Launch Configuration') of each server and I noticed that the system properties -Dorg.jboss.boot.log.file and -Dlogging.configuration are defaulted to a location relative to the standalone directory. This is completely valid because, JBoss Tools assumes we are creating the server for 'standalone'. So I manually edited these two properties and replaced 'standalone' with 'nodeA' and 'nodeB' one my two servers.


      The below screenshot shows these two properties (the last 5 properties were manually added by me)


      But I notice that even if I apply and save my changes to my Server, when I open the launch configuration screen again, that values of these two properties reverts back to its old value (path relative to standalone directory)


      Has anyone seen this issue before? Or please let me know if I am missing something doing something wrong here.


      Here are the version details,


      Eclipse : Kepler Release, Build id: 20130614-0229

      JBoss Tools :

      JDK : 1.7.0 Update 25

      OS : Windows 7 Professional, 32 bit

      JBoss : JBoss EAP 6.0.1