java-player-users

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

[Anthony M. H. <amh...@gm...>]

Oops, forgot the details.

Yes, I'm using 2.0.4 (not going near 2.1 until the java client is  
updated). Running on OS X.. (trying to get access to a linux box to  
test it there).

I am running in PUSH mode (default), with only the main thread calling  
readAll() before delegating to the parallelized processors who just  
query the interfaces for their data (if available).

On the error front, player (-d 9) is surprisingly quiet, but the log  
output itself is locked up:

...
playertcp.cc:550 warning : skipping message from 4:0 with unsupported  
type 4:6
playertcp.cc:550 warning : skipping message from 4:0 with unsupported  
type 4:6
playertcp.cc:550 warning : skipping message from 4:0 with unsupported  
type

That warning is repeated numerous times, still tracking down what it  
is.. (interface position2D, message ACK:DATA_FREQ?) - but it's  
interesting that the lock up prevents it from even finishing the last  
line (probably just not flushing the warnings).

With javaclient debugging on:

[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0
[PlayerClient][Debug] Type = PLAYER_MSGTYPE_RESP_ACK/4 , with payload  
size = 0 for 31:0

Which are in response to the positioning of 10 objects through the  
simulation interface (but only 8 of them are acknowledged).

I'm at a loss right now. I'd rather not revert to the threading model  
of javaclient since it's so wasteful of threads (and I'm fighting the  
urge to reimplement the io in a nonblocking manner).



   ...
   Anthony M. Harrison, PhD
   http://anthonymharrison.com/
   http://jactr.org/

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

[Anthony M. H. <amh...@gm...>]

After reverting to the normal threading model of the java-client, I'm  
able to push the simulation past the four minute barrier, but it then  
freezes again after around six minutes.

It looks as though this is a player issue as others have encountered  
it (http://www.nabble.com/Re%3A-request%2C-reg%3A-non-trivial-problem-tt11237170.html#a11241196 
). The fix? Go to 2.1 (argh)

I looked in the public SVN repo and saw that there has been no  
activity related to 2.1, but Leo has commented that work for 2.1  
compat is on going (presumably on local hard drives). If that code  
were to be committed, others who are stuck in a holding pattern might  
be able to assist (myself most definitely included).

Leo, would you mind taking a few moments to bring folks up to date and  
make that code available?

   ...
   Anthony M. Harrison, PhD
   http://anthonymharrison.com/
   http://jactr.org/

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

[Leo N. <leo...@gm...>]

I really would like to but first I need to have a talk with Radu and a few
minutes to organize all the code. Right now it's not usable, neither
integrable as it need a complete rewrite of the player proxies.

We talked about having a new branch where definetly anyone could help to
reach the 2.1 compatibility, leaving the 2.0 branch as is for backwards
compatibility.

I will try to fix some parts and organize all the stuff asap, maybe for the
next week or so.

Sorry for any inconvencience ...

Bests
Leo

2008/5/5 Anthony M. Harrison <amh...@gm...>:

> After reverting to the normal threading model of the java-client, I'm
> able to push the simulation past the four minute barrier, but it then
> freezes again after around six minutes.
>
> It looks as though this is a player issue as others have encountered
> it (
> http://www.nabble.com/Re%3A-request%2C-reg%3A-non-trivial-problem-tt11237170.html#a11241196
> ). The fix? Go to 2.1 (argh)
>
> I looked in the public SVN repo and saw that there has been no
> activity related to 2.1, but Leo has commented that work for 2.1
> compat is on going (presumably on local hard drives). If that code
> were to be committed, others who are stuck in a holding pattern might
> be able to assist (myself most definitely included).
>
> Leo, would you mind taking a few moments to bring folks up to date and
> make that code available?
>
>   ...
>   Anthony M. Harrison, PhD
>   http://anthonymharrison.com/
>   http://jactr.org/
>
>
>
> -------------------------------------------------------------------------
> 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
>



-- 
**************************************
Leonardo Nomdedeu Calvente
leo...@gm...