Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runbroker.cmd throws error #39

Open
nithinkrishnan opened this issue Mar 25, 2019 · 2 comments
Open

runbroker.cmd throws error #39

nithinkrishnan opened this issue Mar 25, 2019 · 2 comments

Comments

@nithinkrishnan
Copy link

Getting the following error when trying to execute runbroker.cmd command

Usage: java [-options] class [args...]
           (to execute a class)
   or  java [-options] -jar jarfile [args...]
           (to execute a jar file)
where options include:
    -d32          use a 32-bit data model if available
    -d64          use a 64-bit data model if available
    -server       to select the "server" VM
                  The default VM is server.

    -cp <class search path of directories and zip/jar files>
    -classpath <class search path of directories and zip/jar files>
                  A ; separated list of directories, JAR archives,
                  and ZIP archives to search for class files.
    -D<name>=<value>
                  set a system property
    -verbose:[class|gc|jni]
                  enable verbose output
    -version      print product version and exit
    -version:<value>
                  Warning: this feature is deprecated and will be removed
                  in a future release.
                  require the specified version to run
    -showversion  print product version and continue
    -jre-restrict-search | -no-jre-restrict-search
                  Warning: this feature is deprecated and will be removed
                  in a future release.
                  include/exclude user private JREs in the version search
    -? -help      print this help message
    -X            print help on non-standard options
    -ea[:<packagename>...|:<classname>]
    -enableassertions[:<packagename>...|:<classname>]
                  enable assertions with specified granularity
    -da[:<packagename>...|:<classname>]
    -disableassertions[:<packagename>...|:<classname>]
                  disable assertions with specified granularity
    -esa | -enablesystemassertions
                  enable system assertions
    -dsa | -disablesystemassertions
                  disable system assertions
    -agentlib:<libname>[=<options>]
                  load native agent library <libname>, e.g. -agentlib:hprof
                  see also, -agentlib:jdwp=help and -agentlib:hprof=help
    -agentpath:<pathname>[=<options>]
                  load native agent library by full pathname
    -javaagent:<jarpath>[=<options>]
                  load Java programming language agent, see java.lang.instrument
    -splash:<imagepath>
                  show splash screen with specified image
See http://www.oracle.com/technetwork/java/javase/documentation/index.html for more details.

The build was successful but unable to run the broker. Is there anything that we may be missing in execution steps?

@Cicizz
Copy link
Owner

Cicizz commented Mar 29, 2019

I will check and fix it later,thanks a lot

@BEWINDOWEB
Copy link
Contributor

Hi, nithinkrishnan: Have you solved your problem?

Maybe you can try running jmqttstart.cmd instead of runbroker.cmd, and if it doesn't work, follow this guide in ReadMe:

Running locally

  • Download the release version or clone this project.
  • Execute in the root directory:mvn -Ppackage-all -DskipTests clean install -U
  • (there's a bug in v1.1.0 script, so we have to handle it manually) add a system environment variable, key=JMQTT_HOME, value=YOUR_PATH_TO_JMQTT\jmqtt-distribution\target\jmqtt. The purpose of the configuration is to specify the address where the jmqtt configuration file and log configuration file are located.
  • Run the jmqttstart script directly in the jmqtt-distrubution/target/jmqtt/bin directory.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants