synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Holmes (JIRA)" <j...@apache.org>
Subject [jira] Commented: (SYNAPSE-383) AJP 1.3 Transport Listener/Sender
Date Thu, 12 Mar 2009 00:55:50 GMT

    [ https://issues.apache.org/jira/browse/SYNAPSE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681121#action_12681121
] 

Jonathan Holmes commented on SYNAPSE-383:
-----------------------------------------

Interestingly enough the new 2.0.1 has solved this issue as explained.  You are now able to
deploy the ESB to your own tomcat server with an apache front end and instead of using the
NIO adapters extend the org.apache.axis2.transport.http.CommonsHTTPTransportSender transport
to use the apache httpd certificates.  This can be done buy adding your own protocal in the
init method.  

Now with that said Andreas bring up a very good point when saying "Why would writing an AJP
listener automatically imply having a blocking HTTP transport? Can you substantiate that claim
based on your knowledge of the architecture of Apache HTTPD and the way the AJP protocol works?"

Thanks,
J

> AJP 1.3 Transport Listener/Sender
> ---------------------------------
>
>                 Key: SYNAPSE-383
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-383
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Transports
>         Environment: Apache front end with Tomcat connected via the AJP protocol.
>            Reporter: Jonathan Holmes
>
> understanding that this is not support but it does open the ESB up for different uses
and different configurations.  I guess the ultimate problem I'm having is that I have an apache
front end which interfaces with Tomcat via AJP 1.3... Being able to just use the ESB admin
port to see/execute the proxy services I create just as if it were running through the NIO
listener/sender would allow me to not have to open another port or proxy in the requests through
apache...
> This is essential because when trying to proxy in a PKI SSL request it is extremely slow.
 I have tested this by opening up the admin port and there is a huge increase in performance...
> I guess based on what I explained if the ESB's admin port was not opened is there a way
to add an AJP listener/sender?  This would solve my problem and still keeps the admin UI/port
doing only admin stuff.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org


Mime
View raw message