Hi,
I have apache 2.4 setup in a 2 node balancer configuration:
ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
Order allow,deny
Allow from all
BalancerMember ajp://127.0.0.1:8009 route=g1
BalancerMember ajp://127.0.0.1:8010 route=g2
When I
Ah yes, sorry my mistake please ignore!
On Fri, Mar 17, 2017 at 4:46 PM, Eric Covener wrote:
> On Fri, Mar 17, 2017 at 11:46 AM, Wayne W
> wrote:
> > If the servlet container supports JSR356 (ie. tomcat 8) we only need to
> use
> > wicket-native-websocket which compr
Hi,
we are currently using Wicket 6.17 and use a version of Atmosphere jar
libraries (not the wicket version). Its never been great and have had lots
of production issues with it. I'm looking to replace it with straight web
sockets as the fall back long polling etc we never could get to work.
Loo
down it
returned/cut the current connection the proxy and hence the internal server
error message.
On Wed, Apr 20, 2016 at 3:17 PM, Wayne W
wrote:
> I did see the ping parameter for the Balancemember element could be used
> to test the connection - should we be using this? I'm wo
Hmm nothing in the logs.
On Wed, Apr 20, 2016 at 3:18 PM, Wayne W
wrote:
> Ok thanks Eric I will have a look.
>
> On Wed, Apr 20, 2016 at 3:17 PM, Eric Covener wrote:
>
>> On Wed, Apr 20, 2016 at 10:16 AM, Eric Covener wrote:
>> >> how would I check monitor this?
Ok thanks Eric I will have a look.
On Wed, Apr 20, 2016 at 3:17 PM, Eric Covener wrote:
> On Wed, Apr 20, 2016 at 10:16 AM, Eric Covener wrote:
> >> how would I check monitor this? any ideas? I must admit I was
> surprised, but
> >> I was;t sure if mixing ProxyPass and a proxy balancer had some
I did see the ping parameter for the Balancemember element could be used to
test the connection - should we be using this? I'm worried about more load
on the tomcat instances though using this.
On Wed, Apr 20, 2016 at 3:07 PM, Wayne W
wrote:
> Hi Jim,
>
> I did't know
stable but its not long term
solution
thanks
On Wed, Apr 20, 2016 at 2:38 PM, Eric Covener wrote:
> On Mon, Apr 11, 2016 at 11:37 AM, Wayne W
> wrote:
> > I had an issue in production today where the jetty instance became
> > unresponsive (garage collection/out of memory
e httpd side and then bring down the node.
> > On Apr 20, 2016, at 8:10 AM, Wayne W
> wrote:
> >
> > Hi,
> >
> > I'm seeing that with Apache 2.4.12 on Solaris when setup with mod_proxy
> to 2 tomcat instances when we bring down 1 node for maintenance the f
Hi,
I'm seeing that with Apache 2.4.12 on Solaris when setup with mod_proxy to
2 tomcat instances when we bring down 1 node for maintenance the first
client to try and access that node gets a Internal Server Error. Any
requests after that (and for other sessions) are balanced correctly onto
the ot
Hi anyone got any ideas on this?
thanks
On Mon, Apr 11, 2016 at 4:37 PM, Wayne W
wrote:
> Hi,
>
> Perhaps this is default behaviour but its not what I was expecting. I have
> the following conf on Apache 2.4
>
>
> ServerName somedomain.com
> ProxyPass /share htt
Hi,
Perhaps this is default behaviour but its not what I was expecting. I have
the following conf on Apache 2.4
ServerName somedomain.com
ProxyPass /share http://127.0.0.1:8181/share
ProxyPass / balancer://cluster/ stickysession=JSESSIONID nofailover=Off
# define the balancer, with http an
12 matches
Mail list logo
