Mantis Bugtracker
  

Viewing Issue Simple Details Jump to Notes ] View Advanced ] Issue History ] Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0001259 [Resin] minor always 07-19-06 09:06 05-24-07 09:50
Reporter ferg View Status public  
Assigned To ferg
Priority normal Resolution fixed  
Status closed   Product Version
Summary 0001259: disable selected ports for Resin
Description (rep by Bryan Choate)

Is there a ways to take a node out of the cluster definition, such that it?s still accessible through its own http port but not via the LoadBalanceServlet running on a front end instance? Basically, we have a cluster with multiple front-end instances and multiple back-end instances, and when starting nodes we?d like to be able to test the functionality on each node ourselves, and then flip a switch to release it to the world, so to speak. Is there a built-in method of doing this?
 
Additional Information
Attached Files

- Relationships

- Notes
(0001950)
ferg
05-24-07 09:50

server/269q

PortMXBean.stop() and start()
 

- Issue History
Date Modified Username Field Change
07-19-06 09:06 ferg New Issue
05-24-07 09:50 ferg Note Added: 0001950
05-24-07 09:50 ferg Assigned To  => ferg
05-24-07 09:50 ferg Status new => closed
05-24-07 09:50 ferg Resolution open => fixed
05-24-07 09:50 ferg Fixed in Version  => 3.1.2
05-24-07 09:50 ferg Description Updated


Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed.
25 unique queries executed.
Powered by Mantis Bugtracker