title: Deploying with JBoss 7.1.1.Final on Mac OSX
body: <p>I've installed <code>JBoss-as-7.1.1.Final</code> on <code>Mac OSX Mountain Lion</code> and it seems to be on working order since I can access the management console on <code>localhost 9990</code>.  Unfortunately, any decent tutorials for <code>OSX</code> I've come across end at exactly this point.  I have no idea how to deploy a file.  </p>
  
  <p>I have <code>Eclipse Kepler</code> set up with <code>JBoss</code> tools installed, and that seems to have worked without a hitch. The Eclipse GUI has been changed appropriately.</p>
  
  <p>I have a <code>JBoss</code> project in my workspace which is working on everyone else's (Windows) <code>JBoss</code> configuration, but when I try run as>run on server, here are the first few lines printed to the console:</p>
  
  <pre><code>Unable to set property fileName on class org.jboss.logmanager.handlers.FileHandler: java.lang.reflect.InvocationTargetException
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
  at java.lang.reflect.Method.invoke(Method.java:597)
  at org.jboss.logmanager.PropertyConfigurator.configureProperties(PropertyConfigurator.java:187)
  at org.jboss.logmanager.PropertyConfigurator.configureHandler(PropertyConfigurator.java:312)
  at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:128)
  at org.jboss.logmanager.PropertyConfigurator.configure(PropertyConfigurator.java:86)
  at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:246)
  at org.jboss.logmanager.LogManager.readConfiguration(LogManager.java:231)
  at java.util.logging.LogManager$2.run(LogManager.java:264)
  at java.util.logging.LogManager$2.run(LogManager.java:262)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.util.logging.LogManager.readPrimordialConfiguration(LogManager.java:262)
  at java.util.logging.LogManager.getLogManager(LogManager.java:245)
  at java.util.logging.Logger.&lt;init&gt;(Logger.java:225)
  at java.util.logging.LogManager$RootLogger.&lt;init&gt;(LogManager.java:1295)
  at java.util.logging.LogManager$RootLogger.&lt;init&gt;(LogManager.java:1293)
  at java.util.logging.LogManager$1.run(LogManager.java:176)
  at java.security.AccessController.doPrivileged(Native Method)
  at java.util.logging.LogManager.&lt;clinit&gt;(LogManager.java:153)
  at org.jboss.modules.Main.main(Main.java:275)
  Caused by: java.io.FileNotFoundException: /Users/dannyflynn/Desktop/jboss-as-7.1.1.Final/standalone/log/boot.log (Permission denied)
  at java.io.FileOutputStream.open(Native Method)
  at java.io.FileOutputStream.&lt;init&gt;(FileOutputStream.java:194)
  at org.jboss.logmanager.handlers.FileHandler.setFile(FileHandler.java:152)
  at org.jboss.logmanager.handlers.FileHandler.setFileName(FileHandler.java:183)
  ... 22 more
  </code></pre>
  
  <p>I've also tried running on J2EE preview server, which is normally met with: "Server JBoss 7.1 Runtime Server failed to start."</p>
  
  <p>The screen at localhost 8080 remains unchanged in all cases.  However, this was not happening yesterday.  At least yesterday it changed to a blank screen indicating that it could not access the server whenever I tried to run the program.  I'm not sure what has changed since.</p>
  
  <p>Tried the solution offered <a href="https://stackoverflow.com/questions/19720150/eclipse-cant-start-jboss-as7-1-working-from-command-line">here</a> of using chmod 755 on standalone/boot.log.  It produces the following output to the terminal:</p>
  
  <pre><code>chmod [-fhv] [-R [-H | -L | -P]] [-a | +a | =a  [i][# [ n]]] mode|entry file ...
  chmod [-fhv] [-R [-H | -L | -P]] [-E | -C | -N | -i | -I] file ...
  </code></pre>
  
  <p>The console output seems to be more or less the same, still beginning with a complaint about being unable to set property filename, but now there's a pop-up window stating "Server JBoss 7.1 Runtime Server failed to start."</p>