We closed this forum 18 June 2010. It has served us well since 2005 as the ALPHA forum did before it from 2002 to 2005. New discussions are ongoing at the new URL http://forum.processing.org. You'll need to sign up and get a new user account. We're sorry about that inconvenience, but we think it's better in the long run. The content on this forum will remain online.
IndexProgramming Questions & HelpOther Libraries › mostpixelsever - drops connections, please help
Page Index Toggle Pages: 1
mostpixelsever - drops connections, please help (Read 622 times)
mostpixelsever - drops connections, please help
Jul 31st, 2009, 8:47am
 
Hello,

We've developed an app using the mostpixelsever library, but we're having some issue with it dropping connections. I've seen it do this with the sample project too. Sometimes it's a couple hundred frames in, and sometimes its many thousands in.

Here is our basic setup:
6 screens, 3 computers - 2 screens per computer, two processing apps per computer.

We're using the latest mpe library and server. Processing 1.0.5, jre6. All on Windows XP.

This is what we see in the logs...
Server goes along fine until we see this:

Server receive: H,3,38454
Server receive: H,2,38454
Server receive: D,1,38454
Server receive: D,0,38454
Server receive: D,3,38454
Server receive: H,2,38454
Server receive: D,1,38454
Server receive: D,0,38454
Server receive: D,2,38454
Sending: /10.200.1.69 9003: G,38454
Sending: /10.200.1.69 9004: G,38454
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Server receive: H,3,38455
Server receive: H,2,38455
Server receive: H,3,38455
Server receive: H,2,38455
Server receive: H,3,38455
Server receive: H,2,38455
Server receive: H,3,38455
Server receive: D,3,38455
Server receive: H,2,38455
Server receive: D,2,38455
Server receive: D,3,38455
Sending: /10.200.1.69 9003: G,38454
Sending: /10.200.1.69 9004: G,38454
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Sending: /10.200.1.69 9003: G,38454
Sending: /10.200.1.69 9004: G,38454
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Removing Connection 0
Removing Connection 1
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: Tmode=3,delayTime=1000 MPEServer: adding message to next frameEvent: Tmode=3,delayTime=1000
Server receive: H,0,38455
Server receive: H,1,38455
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Server receive: D,2,38455
Server receive: D,3,38455
Server receive: H,0,38455
Server receive: H,1,38455
Server receive: D,1,38455
Exception in thread "main" java.lang.NullPointerException
       at mpe.server.UDPServer.setReady(UDPServer.java:277)
       at mpe.server.UDPServer.read(UDPServer.java:350)
       at mpe.server.UDPServer.run(UDPServer.java:101)
       at mpe.server.UDPServer.main(UDPServer.java:265)
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454
Sending: /10.200.1.24 9005: G,38454
Sending: /10.200.1.24 9006: G,38454

It seems like it thinks that Connection 0 and Connection 1 timed out after only a couple frames, but you can see there are Hellos after the connection gets dropped.

In the Processing app we have debugging turned on in the library and we see that the library is sending stuff, but at the time we catch it it seems to always only be D events, and always for the same frame. We put code in the frameEvent to print a line when that function is entered, but eventually that callback is never called:

Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455
Sending: D,0,38455

We also see these at times, and sometimes very frequently:
Server receive: D,3,38448
Sending: /10.200.1.69 9003: G,38448 Extra message, already on to next frame: /10.200.1.24: 9006 38448 server's count: 38449
Sending: /10.200.1.69 9004: G,38448

It's been tricky trying to get messages out of the library and server because they go so fast.

Could this be a network issue? Is the library malfunctioning?
Any advice would be helpful.
Re: mostpixelsever - drops connections, please help
Reply #1 - Aug 4th, 2009, 1:30pm
 
Looks like 25 views on my post... is anyone else experiencing this? I've gone as far as compiling a version of the server from source that forces the connections to always say they're alive, and still the frame update delegate stops getting called eventually.
Page Index Toggle Pages: 1