Hi Team,
We are seeing multiple issues with pulse in latest version of Apache geode.
(It was fine till M3)
1) Unable to login from Firefox,only works with IE
Error:
HTTP ERROR 404
Problem accessing /pulse/j_spring_security_check
Reason:
Not Found
Even within IE, it does not open pulse consistently and we get error 503
sometimes due to issue explained in point 3)
2) Bugs in pulse statistics as per pulse logs,
[INFO 2016/11/10 21:20:40.594 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18882) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: AverageWrites
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.594 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18883) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: DiskWritesRate
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.595 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18884) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: AverageWrites
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.595 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18885) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: AverageReads
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.595 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18886) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: QueryRequestRate
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.595 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18887) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: DiskReadsRate
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.596 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18888) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: DiskWritesRate
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.596 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18889) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: DiskReadsRate
Expected type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.596 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18890) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: CpuUsage Expected
type: java.lang.Double Received type:
java.lang.Float************************
[INFO 2016/11/10 21:20:45.596 IST PULSE-dharam-ThinkPad-Edge-E431:1099:null
tid=0x6d] (msgTID=109 msgSN=18891) [PULSE]
[org.apache.geode.tools.pulse.internal.log.PulseLogWriter]
************************Unexpected type for attribute: AverageReads
Expected type: java.lang.Double Received type:
java.lang.Float************************
3) Related to locator : gfsh disconnects from cluster abruptly
Steps to reproduce:
1) Start simple locator from gfsh
start locator --name=locator1
2) Start server *from spring boot* with minimal configuration
(locators[10334]) and at least 1 region filled with data
3) Kill the server
4) You will see gfsh gets disconnected from cluster
5) And even most of the time locator gets killed
6) Post 7070 for HTTP goes into TIME_WAIT state and you will have to
manually kill PID of process.
Thanks & Regards,
Dharam
