This is now fixed in 4.1.0-test branch.
On Tue, Dec 9, 2014 at 12:54 PM, Imesh Gunaratne <[email protected]> wrote:
> Found the problem, FaultHandlingWindowProcessor has invoked the member
> fault event constructor with a wrong parameter order:
>
> public MemberFaultEvent(String clusterId, String memberId, String
> partitionId,
> String instanceId, String networkPartitionId,
> float value) {
>
> MemberFaultEvent memberFaultEvent = new
> MemberFaultEvent(member.getClusterId(), member.getInstanceId(),
> member.getMemberId(),
> member.getPartitionId(), member.getNetworkPartitionId(), 0)
>
> On Tue, Dec 9, 2014 at 12:41 PM, Imesh Gunaratne <[email protected]> wrote:
>
>> Hi Devs,
>>
>> I see the below error in autoscaler:
>>
>> [2014-12-09 12:40:02,716] INFO
>> {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} - Faulty
>> member detected [member-id]
>> tom1group6.tomcat1.domain587441ed-2b02-42a9-aec7-77ba0b193d37 with [last
>> time-stamp] 1418108426872 [time-out] 60000 milliseconds
>> [2014-12-09 12:40:02,716] INFO
>> {org.apache.stratos.cep.extension.FaultHandlingWindowProcessor} -
>> Publishing member fault event for [member-id]
>> tom1group6.tomcat1.domain587441ed-2b02-42a9-aec7-77ba0b193d37
>> [2014-12-09 12:40:02,724] ERROR
>> {org.apache.stratos.autoscaler.event.receiver.health.AutoscalerHealthStatEventReceiver}
>> - Member id not found in received message
>>
>> May be CEP is not sending the member id in this event.
>>
>> Thanks
>>
>>
>> --
>> Imesh Gunaratne
>>
>> Technical Lead, WSO2
>> Committer & PMC Member, Apache Stratos
>>
>
>
>
> --
> Imesh Gunaratne
>
> Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Imesh Gunaratne
Technical Lead, WSO2
Committer & PMC Member, Apache Stratos
