You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to subscribe and listen to the ROS topic from a maven project using jrosbridge.
Here's my message handler:
public void handleMessage(Message message)
{
System.out.println(message.toString());
}
I publish messages from ROS side with the 1 kHz rate.
The program crashes with:
[WARNING] thread Thread[Grizzly-kernel(1) SelectorRunner,5,roboy.io.TestVision] was interrupted but is still alive after waiting at least 15000msecs
[WARNING] thread Thread[Grizzly-kernel(1) SelectorRunner,5,roboy.io.TestVision] will linger despite being asked to die via interruption
[WARNING] thread Thread[Grizzly-worker(1),5,roboy.io.TestVision] will linger despite being asked to die via interruption
[WARNING] NOTE: 2 thread(s) did not finish despite being asked to via interruption. This is not a problem with exec:java, it is a problem with the running code. Although not serious, it should be remedied.
[WARNING] Couldn't destroy threadgroup org.codehaus.mojo.exec.ExecJavaMojo$IsolatedThreadGroup[name=roboy.io.TestVision,maxpri=10]
java.lang.IllegalThreadStateException
at java.lang.ThreadGroup.destroy(ThreadGroup.java:778)
at org.codehaus.mojo.exec.ExecJavaMojo.execute(ExecJavaMojo.java:328)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16.162 s
[INFO] Finished at: 2017-03-31T23:46:10+02:00
[INFO] Final Memory: 13M/259M
I've tried -Dexec.cleanupDaemonThreads=false flag for mnv exec:java but the program never reaches the handleMessage function then.
Any suggestions how I could fix it?
UPD: I get the same exception even with ROS message sent once
The text was updated successfully, but these errors were encountered:
I'm trying to subscribe and listen to the ROS topic from a maven project using
jrosbridge
.Here's my message handler:
I publish messages from ROS side with the 1 kHz rate.
The program crashes with:
I've tried
-Dexec.cleanupDaemonThreads=false
flag formnv exec:java
but the program never reaches thehandleMessage
function then.Any suggestions how I could fix it?
UPD: I get the same exception even with ROS message sent once
The text was updated successfully, but these errors were encountered: