Error Invoking Method & Failed to launch JVM

[FRCAluminati3555]

Downloaded Grip for windows 7 64 bit, and it will not launch; it crashes on startup. Any advise to fix this issue? It puts those errors on the screen, the ones in the title. Thanks.

[JLLeitschuh]

Can you supply the error message?

Also, if you could upload your GRIP.log file you can find in your $HOME directory that would be really useful.

[nitzanbueno]

Our team has also gotten the same issue - we installed versions 1.5.0rc1, 1.5.0rc2 and 1.5.0rc3 and all showed the same result, though 1.4.0 worked just fine. Also happens with 1.5.0rc3 on Windows 10 64-bit.

I ran the .jar file from the command line and it printed this:

CONFIG: Configuration done.
≡σß 28, 2016 7:56:37 PM java.util.logging.LogManager$RootLogger log
CONFIG: GRIP Version: 1.5.0-rc3
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
platform: /Windows/amd64/
Exception in Application init method
java.lang.reflect.InvocationTargetException
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.sun.javafx.application.LauncherImpl.launchApplicationWithArgs(Unknown Source)
        at com.sun.javafx.application.LauncherImpl.launchApplication(Unknown Source)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at sun.launcher.LauncherHelper$FXHelper.main(Unknown Source)
Caused by: java.lang.RuntimeException: Exception in Application init method
        at com.sun.javafx.application.LauncherImpl.launchApplication1(Unknown Source)
        at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$155(Unknown Source)
        at java.lang.Thread.run(Unknown Source)
Caused by: edu.wpi.grip.core.exception.GripServerException: Could not start Jetty server
        at edu.wpi.grip.core.http.GripServer.start(GripServer.java:158)
        at edu.wpi.grip.ui.Main.init(Main.java:100)
        ... 3 more
Caused by: java.net.BindException: Address already in use: bind
        at sun.nio.ch.Net.bind0(Native Method)
        at sun.nio.ch.Net.bind(Unknown Source)
        at sun.nio.ch.Net.bind(Unknown Source)
        at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)
        at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)
        at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:326)
        at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80)
        at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:244)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at org.eclipse.jetty.server.Server.doStart(Server.java:384)
        at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68)
        at edu.wpi.grip.core.http.GripServer.start(GripServer.java:156)
        ... 4 more
Exception running application edu.wpi.grip.ui.Main

Here is the log file, although it doesn't seem too helpful:

נוב 28, 2016 7:56:37 PM java.util.logging.LogManager$RootLogger log
CONFIG: Configuration done.
נוב 28, 2016 7:56:37 PM java.util.logging.LogManager$RootLogger log
CONFIG: GRIP Version: 1.5.0-rc3
נוב 28, 2016 7:56:37 PM com.google.inject.internal.util.Stopwatch resetAndLog
FINE: Module execution: 290ms
(SamCarlberg: this goes on for several hundred lines)

Also when running netstat, I saw that every time I ran GRIP, a new port was taken at around 49970, and ascending in order each consecutive time. This may or may not be related, as a similar thing seemed to happen even when I wasn't running GRIP.

[SamCarlberg]

@nitzanbueno You either have another instance of GRIP running without changing the HTTP port in the settings, or there's another app using that port.

[nitzanbueno]

I ran GRIP first thing after a restart and on two different computers and the same problem arose, so I doubt that's the reason. Maybe the code accidentally starts the server twice?

[SamCarlberg]

Then an app starts on login that uses port 8080. You should be able to go to http://localhost:8080 in a browser and see a webpage.

[SamCarlberg]

I'm going to delete the log text, there's nothing useful and it makes the page very difficult to read.

GRIP defaults to port 8080, whatever's running on 49970 isn't us.

[FRCAluminati3555]

Go for it, and going to http://localhost:8080 results in a 404 error message

[SamCarlberg]

What's the message/can you post a screenshot? I want to see if it's GRIP's 404 or a different one. And if you could run the GRIP jar from the command line and post the console output, that would also be a big help

[FRCAluminati3555]

[FRCAluminati3555]

[FRCAluminati3555]

I wasn't sure if this was what you were looking for, but running these will just bring up the loading bar, they don't bring up the error panels, but nothing else happens, nothing else is brought up.

[SamCarlberg]

You need to run the jar with java -jar C:\Users\frcAluminati\...\GRIP-1.5.0-rc3-x64.jar. But another app (I don't know what) is running on port 8080 and is blocking GRIP from using it.

The master branch has support for setting the HTTP port from the command line. You can download or clone it, then run gradlew :ui:run -Pargs="--port <port number>" in the root GRIP folder.

You can also change the server port in the save file, there should be an entry for it near the bottom of the file

[FRCAluminati3555]

Which file do I go to to change the server port, and what should I change it to?

[SamCarlberg]

You need to set it on the command line

1. Run powershell (Windows key -> type "powershell")
2. Run cd and give it the path to the GRIP folder you downloaded (e.g. cd C:\Users\frcAluminati\Downloads\GRIP-master)
3. Run gradlew :ui:run -Pargs="--port 3555" (or whatever port number you want)

[FRCAluminati3555]

Okay I did that, but then how do I run it?

[SamCarlberg]

The gradlew command runs it.

[FRCAluminati3555]

It says that gradlew isn't a recognized name of cmdlet, I don't have much experience with running things through the command line.

[SamCarlberg]

Sorry, I meant to use the old command line. Run "cmd" instead of "poewrshell" in step 1 and that should work for you.

[FRCAluminati3555]

Thanks, it worked and is now running, do we have to run that command every time to use this?

[SamCarlberg]

For now, yes. You can write a batch script that will run GRIP with command line arguments so you don't have to run it from the command line every time.

We might add a configuration file at some point, but that wouldn't happen for a while.

For the batch script:

C:\Users\frcAluminati\AppData\Local\GRIP\GRIP.exe --port 3555

Should run GRIP on port 3555. Just create a GRIP.bat file and paste that line into it and you should be good to go. Just run that GRIP.bat file (double-click).

[FRCAluminati3555]

Thanks for the help!

…

On Nov 28, 2016 5:39 PM, "Sam Carlberg" ***@***.***> wrote: For now, yes. You can write a batch script that will run GRIP with command line arguments so you don't have to run it from the command line every time. We might add a configuration file at some point, but that wouldn't happen for a while. For the batch script: C:\Users\frcAluminati\AppData\Local\GRIP\GRIP.exe --port 3555 Should run GRIP on port 3555. Just create a GRIP.bat file and paste that line into it and you should be good to go. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#719 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHKvLMaLY6Y5_MhMe0h-IgKvMZJm0tPnks5rC1gKgaJpZM4K8BuV> .