[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-92) Integrate and enable multiplex transport

Integrate and enable multiplex transport ---------------------------------------- Key: JBMESSAGING-92 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-92 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Remoting Reporter: Ovidiu Feodorov Assigned To: Ron Sigal Priority: Critical Fix For: 1.2.0.Alpha1 Original Estimate: 1 week Remaining Estimate: 1 week Replace "Connector per Consumer" solution with a Remoting UIL2-like transport The ConsumerInterceptor creates a new Connector instance per each Consumer, and associates maintains a reference to it as transitory metadata, so it can shut it down when the Consumer closes. The Connector is necessary as a callback server for asynchronous notifications. The MessageCallbackHandler instance is registered to it. Maintaining an instance per Consumer is necessary to avoid port conflicts. This is a temporary solution until JBoss Remoting gets an UIL2-like transport. As long as we maintain a server socket per consumer, it won't be possbile to receive asynchronous notifications over firewalls. until multiplex performance is better it should not be the default tranport but should be available nevertheless