You're going to need to configure a second listen statement on another port, then configure the stats uri on that. RMI will pass directly through your current port, you'll use the other port to monitor the state of haproxy.
-JohnF > -----Original Message----- > From: Barak Yaish [mailto:[email protected]] > Sent: July 15, 2010 11:58 AM > To: [email protected]; John Marrett > Subject: Re: Fronting RMI servers with haproxy > > John (and list), > > Thanks for your last reply, it indeed solved the problem. I > followed the docs for enabling stats, and got that: > > 'stats' statement ignored for proxy 'RMI' as it requires HTTP mode > > Can stats be enabled for mode tcp? > > Thanks. > > > On Thu, Jul 15, 2010 at 4:34 PM, John Marrett > <[email protected]> wrote: > > > Barak, > > > > listen RMI 10.80.0.55:3305 <http://10.80.0.55:3305/> > > > > mode tcp > > > > option httpchk > > > I doubt that your RMI server is responding that well to > your httpchk. > > If you enable the stats page and access it (or perhaps > the control > socket), I suspect that you'll see that your backend > server is marked as > down. Once you have the backend server up things may > work a little > better. > > You'll need to set up the stats socket on another port > from your RMI > port. You should check out the docs [1], search for the > string stats uri > and you'll find a little configuration example. > > [1] http://haproxy.1wt.eu/download/1.4/doc/configuration.txt > > -JohnF > > > > >
