I believe that the issue points to a project settings -> Scheduling, where you might have activated a threshold box but not entered a value or the value is exceeded. These could be 'Critical Path Threshold' or 'Effort on Task Exceeds Threshold' without a valid value or the value HAS been exceeded for this project (workplan).
I'd check my projects to make sure which one(s) is or are affected and adjust values accordingly.
Hmm i understand now, going to check later, thank you very mutch for the awnser.
Now is happing another problem :( . Is not any port problem or configuration we check then all.
ERROR server:ClusterMonitor.HeartbeatThread:com.kintana.core.server.cluster.MulticastCommsFailureMonitor:2013/06/07-06:14:31.527 EDT: No multicast traffic has been heard from node PPMPR3 on the MULTICAST_PORT port for over 3 minutes even though the node appears to be up. Please check your multicast routing, server.conf settings, and/or firewall settings. ERROR server:MulticastAgent.ListenerThread:com.kintana.core.server.cluster.MulticastAgent:2013/06/07-06:14:51.528 EDT: WARNING: MulticastAgent.ListenerThread Overload ERROR server:MulticastAgent.ListenerThread:com.kintana.core.server.cluster.MulticastAgent:2013/06/07-06:14:51.528 EDT: Message queue processed slowly which can cause failover conflicts
ERROR JSESSIONID=B536EA39A4B591C52DD1F8389320E61D.PPMPR6,USERNAME=C0223586:TP-Processor22:org.apache.jsp.arch.Error_jsp:2013/06/07-08:11:26.207 EDT: at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
multicast issues are communication poblems between the nodes and can generally be solved with a fix / SP depending on your current version. You need to log a case for that - it's not somethng that we can do between 'here and the door'.
Dunno about the other lines - maybe you should also create a new ticket for that.