Details

    • Type: Sub-task Sub-task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 4.0
    • Fix Version/s: 4.0_b84_RC1
    • Component/s: docs
    • Labels:
      None

      Description

      I added a new boolean option,

      long --dry-run
      short -n

      to start-local-instance and start-domain

      ========

      What it does is do everything EXCEPT actually creating and running the JVM. Instead it returns the HUGE commandline that it WOULD have used to start the server.

      Example output:

      D:\gf\v3>asadmin start-local-instance -n i1
      C:\jdk\bin\java.exe
      -cp
      D:/glassfish3/glassfish/modules/glassfish.jar
      -XX:+UnlockDiagnosticVMOptions
      -XX:MaxPermSize=192m
      -XX:NewRatio=2
      -Xmx512m
      -javaagent:/glassfish3/glassfish/lib/monitor/btrace-agent.jar=unsafe=true,noServer=true
      -server
      -Dosgi.shell.telnet.maxconn=1
      -Dfelix.fileinstall.disableConfigSave=false
      -Djdbc.drivers=org.apache.derby.jdbc.ClientDriver
      -Dfelix.fileinstall.dir=D:\glassfish3\glassfish/modules/autostart/
      -Djavax.net.ssl.keyStore=D:\glassfish3\glassfish\nodes\localhost-domain1\i1/config/keystore.jks
      -Dosgi.shell.telnet.port=26666
      -Djava.security.policy=D:\glassfish3\glassfish\nodes\localhost-domain1\i1/config/server.policy
      -Djava.awt.headless=true
      -Dfelix.fileinstall.log.level=3
      -Dfelix.fileinstall.poll=5000
      -Dcom.sun.aas.instanceRoot=D:\glassfish3\glassfish\nodes\localhost-domain1\i1
      -Dosgi.shell.telnet.ip=127.0.0.1
      -Dcom.sun.enterprise.config.config_environment_factory_class=com.sun.enterprise.config.serverbeans.AppserverConfigEnvironmentFactory
      -Djava.endorsed.dirs=D:\glassfish3\glassfish/modules/endorsed;D:\glassfish3\glassfish/lib/endorsed
      -Dcom.sun.aas.installRoot=D:\glassfish3\glassfish
      -Dfelix.fileinstall.bundles.startTransient=true
      -Djava.ext.dirs=C:\jdk/lib/ext;C:\jdk/jre/lib/ext;D:\glassfish3\glassfish\nodes\localhost-domain1\i1/lib/ext
      -Dfelix.fileinstall.bundles.new.start=true
      -Djavax.net.ssl.trustStore=D:\glassfish3\glassfish\nodes\localhost-domain1\i1/config/cacerts.jks
      -Dorg.glassfish.additionalOSGiBundlesToStart=org.apache.felix.shell,org.apache.felix.gogo.runtime,org.apache.felix.gogo.shell,org.apache.felix.gogo.command,org.apache.felix.fileinstall
      -Dcom.sun.enterprise.security.httpsOutboundKeyAlias=s1as
      -Djava.security.auth.login.config=D:\glassfish3\glassfish\nodes\localhost-domain1\i1/config/login.conf
      -DANTLR_USE_DIRECT_CLASS_LOADING=true
      Dgosh.args=-noshutdown -c noop=true
      -Djava.library.path=D:/glassfish3/glassfish/lib;C:/jdk/bin;D:/gf/v3;C:/Windows/Sun/Java/bin;C:/Windows/System32;C:/Windows;D:/glassfish3/glassfish/bin;C:/Windows/System32/wbem;C:/Windows/System32/WindowsPowerShell/v1.0;C:/Program Files/WIDCOMM/Bluetooth Software;C:/Program Files/WIDCOMM/Bluetooth Software/syswow64;C:/bin;C:/d/b;C:/bin/apache-maven-2.2.1/bin;C:/bin/ant/bin;C:/Program Files/7-Zip;C:/Program Files (x86)/Mozilla Firefox;C:/bin/mks/mksnt;C:/bin/git/cmd;C:/bin/git/bin;C:/bin/svn;C:/Program Files/MySQL/MySQL Server 5.5/bin;C:/bin/vim/vim73;C:/bin/ruby/bin
      com.sun.enterprise.glassfish.bootstrap.ASMain
      -asadmin-args
      -host,,,localhost,,,port,,,4848,,,user,,,admin,,,secure=false,,,terse=true,,,echo=false,,,interactive=false,,,start-local-instance,,,verbose=false,,,-debug=false,,,i1
      -instancename
      i1
      -verbose
      false
      -debug
      false
      -asadmin-classpath
      D:/glassfish3/glassfish/modules/admin-cli.jar
      -asadmin-classname
      com.sun.enterprise.admin.cli.AsadminMain
      -upgrade
      false
      -type
      INSTANCE
      -instancedir
      D:/glassfish3/glassfish/nodes/localhost-domain1/i1
      -read-stdin
      true

        Issue Links

          Activity

          Hide
          Mike Fitch added a comment -

          Added writeups to start-domain and start-local-instance.

          These additions were included in main-docs build 4.0-b27, which started getting picked up by GlassFish builds as of revision 61152 (03-Apr-2013).

          Show
          Mike Fitch added a comment - Added writeups to start-domain and start-local-instance. These additions were included in main-docs build 4.0-b27, which started getting picked up by GlassFish builds as of revision 61152 (03-Apr-2013).
          Hide
          Byron Nevins added a comment -

          That's because the official name of the option is

          _dry-run

          I'll change it to "dry-run" right now. It should be working in the next build you get.
          Thanks for reminding me!

          Show
          Byron Nevins added a comment - That's because the official name of the option is _dry-run I'll change it to "dry-run" right now. It should be working in the next build you get. Thanks for reminding me!
          Hide
          Mike Fitch added a comment -

          Byron,

          Neither start-domain nor start-local-instance show these options in their usage message:

          asadmin> start-domain --usage
          Invalid option: --usage
          Usage: asadmin [asadmin-utility-options] start-domain
          [v|-verbose[=<verbose(default:false)>]]
          [--upgrade[=<upgrade(default:false)>]]
          [w|-watchdog[=<watchdog(default:false)>]]
          [d|-debug[=<debug(default:false)>]] [--domaindir <domaindir>]
          [?|-help[=<help(default:false)>]] [domain_name]
          Command start-domain failed.
          asadmin> start-local-instance --usage
          Invalid option: --usage
          Usage: asadmin [asadmin-utility-options] start-local-instance
          [v|-verbose[=<verbose(default:false)>]]
          [w|-watchdog[=<watchdog(default:false)>]]
          [d|-debug[=<debug(default:false)>]] [--sync <sync(default:normal)>]
          [--nodedir <nodedir>] [--node <node>]
          [?|-help[=<help(default:false)>]] [instance_name]
          Command start-local-instance failed.

          Both commands appear to accept -n, but neither will accept --dry-run (or --dryrun for that matter).

          Please let me know how to proceed. Should we document just the -n option?

          Thanks,
          --Mike

          Show
          Mike Fitch added a comment - Byron, Neither start-domain nor start-local-instance show these options in their usage message: asadmin> start-domain --usage Invalid option: --usage Usage: asadmin [asadmin-utility-options] start-domain [ v| -verbose [=<verbose(default:false)>] ] [--upgrade [=<upgrade(default:false)>] ] [ w| -watchdog [=<watchdog(default:false)>] ] [ d| -debug [=<debug(default:false)>] ] [--domaindir <domaindir>] [ ?| -help [=<help(default:false)>] ] [domain_name] Command start-domain failed. asadmin> start-local-instance --usage Invalid option: --usage Usage: asadmin [asadmin-utility-options] start-local-instance [ v| -verbose [=<verbose(default:false)>] ] [ w| -watchdog [=<watchdog(default:false)>] ] [ d| -debug [=<debug(default:false)>] ] [--sync <sync(default:normal)>] [--nodedir <nodedir>] [--node <node>] [ ?| -help [=<help(default:false)>] ] [instance_name] Command start-local-instance failed. Both commands appear to accept -n, but neither will accept --dry-run (or --dryrun for that matter). Please let me know how to proceed. Should we document just the -n option? Thanks, --Mike

            People

            • Assignee:
              Mike Fitch
              Reporter:
              Byron Nevins
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: