[jboss-jira] [JBoss JIRA] Updated: (JBMESSAGING-979) Servlet transport for JBoss Messaging

Servlet transport for JBoss Messaging ------------------------------------- Key: JBMESSAGING-979 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-979 Project: JBoss Messaging Issue Type: Feature Request Components: JMS Remoting Affects Versions: 1.2.0.SP1 Environment: Windows 2003 with IIS as front-end web server. Reporter: Daniel Weeks Assigned To: Tim Fox Fix For: Unscheduled Although there is an https transport for JBoss Messaging, it does not support going over the same port that Tomcat is using like the JBoss MQ jbossmq-httpil.sar does. This capability is required for environments in which port 443 is the only port that is open for communication. Although url proxying/forwarding could be used under Apache to work around this issue, there is not a good solution for doing this with IIS (or for applications that don't use a front-end web server and are limited to port 443). Many enterprise PKI solutions (such as DoD) favor the use of IIS over Apache due to cost of COTS products, so this is a show stopper for JBoss Messaging in those environments. This issue is preventing us from migrating an enterprise application that runs in the DoD environment to to JBoss Messaging. The application makes heavy use of JMS and would benefit greatly from the improved performance that JBoss Messaging provides. This feature request is originating from a JBoss Customer Support Portal case at the following URL: https://network.jboss.com/jbossnetwork/restricted/caseDetail.html?caseId=...