java-player-users

[Java-player-users] Complete freeze of stage?

[Anthony H. <ant...@nr...>]

I'm not entirely sure where this problem is being caused, but here's  
the situation:

I've got stage configured with two robots and a connection to the  
simulation interface. After about five minutes stage freezes up  
entirely and the javaclients do as well (freezing on readAll()). (but  
my other code continues to chug along).

What makes this interesting is that after killing the javaclients,  
stage resumes, which leads me to believe a communications buffer might  
be flooded.

Has anyone experienced something similar?

Now I am doing things a tad differently. First, I'm not running  
threaded. Instead I'm using executors to parallelize a large amount of  
the processing. At the top of each iteration, readAll() is called for  
each bot, and then separate executors do the sensor processing. After  
all the sensors are processed then new commands are issued (on the  
same thread that did the reading so there is no concern about sending  
munged commands due to different threads writing to the port).

The PlayerClients are instantiated as normal but I make no calls to  
runThreaded() or setNotThreaded() (since it defaults to not threaded).




  ...
  Anthony M. Harrison, PhD
  Cognitive Robotics & Human-Robot Interaction
  Naval Research Laboratory

Re: [Java-player-users] Complete freeze of stage?

[John O. <joh...@gm...>]

I am afraid I have never experienced anything like this. First question
would be what version of player/stage are you using? If you read back
through the mail archives people have been having issues with player/stage
2.1, so you may want to downgrade your player/stage version until this is
resolved.

Otherwise if there is any more information such as error messages from P/S
you could provide it would be helpful.

I wasn't entirely sure from what you said if multiple executors were reading
from a given port,  since if you have the system in PULL mode multiple
clients reading the same port could also cause issues.

thanks

John


2008/4/30 Anthony Harrison <ant...@nr...>:

> I'm not entirely sure where this problem is being caused, but here's
> the situation:
>
> I've got stage configured with two robots and a connection to the
> simulation interface. After about five minutes stage freezes up
> entirely and the javaclients do as well (freezing on readAll()). (but
> my other code continues to chug along).
>
> What makes this interesting is that after killing the javaclients,
> stage resumes, which leads me to believe a communications buffer might
> be flooded.
>
> Has anyone experienced something similar?
>
> Now I am doing things a tad differently. First, I'm not running
> threaded. Instead I'm using executors to parallelize a large amount of
> the processing. At the top of each iteration, readAll() is called for
> each bot, and then separate executors do the sensor processing. After
> all the sensors are processed then new commands are issued (on the
> same thread that did the reading so there is no concern about sending
> munged commands due to different threads writing to the port).
>
> The PlayerClients are instantiated as normal but I make no calls to
> runThreaded() or setNotThreaded() (since it defaults to not threaded).
>
>
>
>
>  ...
>  Anthony M. Harrison, PhD
>  Cognitive Robotics & Human-Robot Interaction
>  Naval Research Laboratory
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
>
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Java-player-users mailing list
> Jav...@li...
> https://lists.sourceforge.net/lists/listinfo/java-player-users
>