|
| We are experiencing a weird issue in our staging environment with a WebSphere Portal v6.0.1 horizontal cluster. While the main node in the cluster starts up in approximately 5 minutes of CPU time, the secondary nodes take 20+ minutes of CPU time. There ar
e no exceptions in the log files on the secondary nodes that would reasonably explain the additional CPU time during startup. Also once portal starts up, we have not noticed any significant difference in performance between the cluster nodes. We had filed
a PMR with IBM on this issue and they agree with us that this is not normal behavior. However, so far they have been less than helpful - just making us spin cycles on log/trace file collection. I am curious if other folks have experienced similar issues
on a WP6 cluster?
Thanks in advance!
URL: http://vivekagarwal.wordpress.com
|
|