synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiranya Jayathilaka (JIRA)" <>
Subject [jira] Assigned: (SYNAPSE-383) AJP 1.3 Transport Listener/Sender
Date Mon, 20 Sep 2010 06:36:33 GMT


Hiranya Jayathilaka reassigned SYNAPSE-383:

    Assignee: Supun Kamburugamuva

> AJP 1.3 Transport Listener/Sender
> ---------------------------------
>                 Key: SYNAPSE-383
>                 URL:
>             Project: Synapse
>          Issue Type: New Feature
>          Components: Transports
>         Environment: Apache front end with Tomcat connected via the AJP protocol.
>            Reporter: Jonathan Holmes
>            Assignee: Supun Kamburugamuva
> 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
> 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:
For additional commands, e-mail:

View raw message