On 04.03.2014 23:09, Doug Strick wrote:
The F5 issues were just due to poor environment configuration. Each F5 VIP
was sending traffic to the same pool and that pool was only configured for
1 member. That 1 member IP/port was used by several apache virtual hosts.
So basically I never knew
I went over the documentation multiple times and the light bulb finally
went on after everyone's input. Most of the mod_jk configs were built by
the Coldfusion web server config tool so that's why it's so cluttered. I
made the configuration work by putting the below in httpd.conf:
IfModule
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Doug,
On 3/4/14, 11:51 AM, Doug Strick wrote:
I went over the documentation multiple times and the light bulb
finally went on after everyone's input. Most of the mod_jk configs
were built by the Coldfusion web server config tool so that's why
The F5 issues were just due to poor environment configuration. Each F5 VIP
was sending traffic to the same pool and that pool was only configured for
1 member. That 1 member IP/port was used by several apache virtual hosts.
So basically I never knew which virtual host was getting the request
Hello,
I'm currently working on a project where we're migrating from Adobe
Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the underlying server
and mod_jk is the standard connector used. On our test environment we have
a single apache httpd instance serving multiple domains with each
Doug Strick wrote:
Hello,
I'm currently working on a project where we're migrating from Adobe
Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the underlying server
and mod_jk is the standard connector used. On our test environment we have
a single apache httpd instance serving multiple
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
André,
On 3/3/14, 4:57 PM, André Warnier wrote:
Doug Strick wrote:
Hello,
I'm currently working on a project where we're migrating from
Adobe Coldfusion 8 to CF 10. Adobe CF10 now uses tomcat as the
underlying server and mod_jk is the
