s***@gmail.com
2009-03-12 04:15:35 UTC
Hey All,
Recently we have started to use WAS 7 instead of WAS 6, and are getting various issues.
I believe all the issues stem from some limitation in how our classes are being loaded (or in fact not being loaded).
Our deployment process uses wsadmin, and at the end of each deployment the nodes are synced and servers are restarted. The issues arise when the servers are being started, there are several possible issues that may arise around FileNotFound / ClassNotFound exceptions and also stack overflows.
The behaviour is weird as it never happened with WAS 6, and manually restarting the servers usually acts as a good remedy. The outcome of a particular deployment seems somewhat luck based.
Does anybody have any suggestions?
(It may or may not be related, but in the ffdc logs there is a constant reference to "depth limit reached")
Thanks
Recently we have started to use WAS 7 instead of WAS 6, and are getting various issues.
I believe all the issues stem from some limitation in how our classes are being loaded (or in fact not being loaded).
Our deployment process uses wsadmin, and at the end of each deployment the nodes are synced and servers are restarted. The issues arise when the servers are being started, there are several possible issues that may arise around FileNotFound / ClassNotFound exceptions and also stack overflows.
The behaviour is weird as it never happened with WAS 6, and manually restarting the servers usually acts as a good remedy. The outcome of a particular deployment seems somewhat luck based.
Does anybody have any suggestions?
(It may or may not be related, but in the ffdc logs there is a constant reference to "depth limit reached")
Thanks