Hi Bruce, Currently, the NettyEmitter creates all the connections and stores the corresponding channels to be later used by send() calls. The issue seems to be that the send() calls don't wait for the connections to be formed. If the required connection doesn't exist, the message is dropped.
Understandably, the fix would be to have the send() block till the required connection is made. In that case, we might as well create the connections lazily (on first send). That way, the connections will be automatically repaired, in case they break, by subsequent send() invocations. Let me know what you think. Thanks Karthik On Wed, Oct 12, 2011 at 1:51 PM, Leo Neumeyer (Created) (JIRA) < [email protected]> wrote: > Netty initialization > -------------------- > > Key: S4-6 > URL: https://issues.apache.org/jira/browse/S4-6 > Project: Apache S4 > Issue Type: Improvement > Reporter: Leo Neumeyer > > > Wait for Netty layer to be ready before the app init method is called. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators: > https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa > For more information on JIRA, see: http://www.atlassian.com/software/jira > > >
