0002098: load-balance failing over from app-tier->0 to app-tier->0

Viewing Issue Advanced Details [ Jump to Notes ]

[ View Simple ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0002098

[Resin]

text

always

10-20-07 10:24

10-24-07 16:07

Reporter

stbu

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Platform

Status

closed

Projection

none

OS Version

ETA

none

Fixed in Version

3.1.4

Product Version

3.1.3

Product Build

Summary

0002098: load-balance failing over from app-tier->0 to app-tier->0

Description

Resin-Professional 3.1.3 in a Load-Balancing configuration

web-a Windows XP, Java 6, 192.168.1.100
app-a Windows XP, Java 6, 192.168.1.100
app-b Linux, Java 6, 192.168.1.141

see also attached resin.conf of all three involved resin instances.

All three instances of Resin are started and I've logged into the php resin-admin application.
From the Summary tab (status.php) I can see that I'm working on app-a.
Now, I've stopped app-a and I'm pressing 'refresh' on status.php and the loadbalancer (web-a) is failing over to app-b. This works great.

But, on the console of web-a (Loadbalancer) there is a confusing message logged:

[14:57:40.718] load-balance failing over from app-tier->0 to app-tier->0

IMHO, the message is a bit unclear and should be something like:

load-balance failing over from app-tier->app-a to app-tier->app-b

Steps To Reproduce

Additional Information

Attached Files

C:\\tmp\\caucho\\resin.conf [^] (10,549 bytes) 10-20-07 10:24

Relationships

Notes
(0002391) ferg 10-24-07 16:07	server/269s

Issue History
Date Modified	Username	Field	Change
10-20-07 10:24	stbu	New Issue
10-20-07 10:24	stbu	File Added: C:\\tmp\\caucho\\resin.conf
10-20-07 10:24	stbu	Issue Monitored: stbu
10-24-07 16:07	ferg	Note Added: 0002391
10-24-07 16:07	ferg	Assigned To	=> ferg
10-24-07 16:07	ferg	Status	new => closed
10-24-07 16:07	ferg	Resolution	open => fixed
10-24-07 16:07	ferg	Fixed in Version	=> 3.1.4

Mantis 1.0.0rc3[^]

31 total queries executed.
26 unique queries executed.