Simulator Crashing

Issue #8 closed
Dave Kotfis created an issue

I recently tried using the simulator again after upgrading to Ubuntu 14.04 and ROS Indigo, and it doesn't seem to work for me anymore. I can start it up and see LIDAR scans in RViz, but the boxStep.py script throws an error:

String failed to covert message to packet! see exception below. java.lang.IllegalAccessException: Class us.ihmc.utilities.ros.msgToPacket.converter.ROSMessageConverter can not access a member of class org.ros.internal.message.$Proxy4 with modifiers "public final" at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:101) at java.lang.reflect.AccessibleObject.slowCheckMemberAccess(AccessibleObject.java:295) at java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:287) at java.lang.reflect.Method.invoke(Method.java:476) at us.ihmc.utilities.ros.msgToPacket.converter.ROSMessageConverter.convertToPacket(ROSMessageConverter.java:573) at us.ihmc.utilities.ros.msgToPacket.converter.ROSMessageConverter.convertToPacket(ROSMessageConverter.java:358) at us.ihmc.utilities.ros.subscriber.IHMCMsgToPacketSubscriber.onNewMessage(IHMCMsgToPacketSubscriber.java:25) at us.ihmc.utilities.ros.subscriber.IHMCMsgToPacketSubscriber.onNewMessage(IHMCMsgToPacketSubscriber.java:10) at org.ros.internal.transport.queue.MessageDispatcher$1.run(MessageDispatcher.java:94) at org.ros.internal.transport.queue.MessageDispatcher$1.run(MessageDispatcher.java:91) at org.ros.concurrent.EventDispatcher.loop(EventDispatcher.java:43) at org.ros.concurrent.CancellableLoop.run(CancellableLoop.java:56) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)

Comments (3)

  1. Dave Kotfis reporter

    It looks like this is related to our use of Oracle Java 8. Using OpenJDK 7 seems to work just fine. Maybe this is worth clarifying in the README.md.

  2. DouglasS

    @dkotfis Thanks for the feedback. We're in the midst of a documentation overhaul and we'll definitely address this.

  3. Log in to comment