[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-52) in TC6 jk connection does work with mod_cluster

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-52.
------------------------------------



Closing. Clean-up.
At least one of the following applies:

  * the issue has been thoroughly tested as a part of one of the current releases
or
  * it hasn't occurred in ~2 years
or
  * it's utterly harmless

> in TC6 jk connection does work with mod_cluster
> -----------------------------------------------
>
>                 Key: MODCLUSTER-52
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-52
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.Beta3
>         Environment: When using TC6 and org.jboss.modcluster.ModClusterListener ajp connector are handle as http.
>            Reporter: Jean-Frederic Clere
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.0.0.Beta4
>
>
> Just use tc6 and add JVMRoute in the engine and the listener. Look to the mod_cluster status page.... The AJP connector is display as HTTP and handled like HTTP so it doesn't work. Note that using protocol="org.apache.coyote.ajp.AjpProtocol" doesn't help the connector is ignored but mod_cluster.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)