[Spread-users] "connection clsoed" problem

Brian Moseley bcm at maz.org
Wed Sep 22 00:43:23 EDT 2004

Ryan Caudy wrote:
> I wouldn't recommend disconnecting after every multicast.  Reasons why
> this is a bad idea were included in another recent post of mine.  I
> would recommend another potential workaround -- try having each of
> your threads connect to spread at startup, but delay it to avoid any
> potential race conditions (e.g. thread 1 connects right away, 2
> connects after 1 second, and so on...).

hm, i don't think this would be a great solution for me. these threads 
are managed by the servlet container itself (tomcat), and i'm not sure 
there are any hooks for me to have them execute code at startup. i'd 
probably have to do some customization of tomcat itself, which is 
something i'd prefer to avoid. but maybe it's a fallback option if i 
can't figure this problem out.

> The only drawback I see with sharing a single connection is the
> potential synchronization overhead, which could hurt throughput by
> decreasing your degree of concurrency.  Are there others that concern
> you?

nope, that's the one. your comment makes me wonder, tho, what kind of 
concurrency does spread itself have?

thanks for the comments.

More information about the Spread-users mailing list