-
Bug
-
Resolution: Duplicate
-
P2
-
1.3.1_11
-
sparc
-
generic
Productive WLS application server instances keep crashing every few
hours. At least four events today. Had been running fine for months
before this, and customer claimed they hadn't changed anything (well,
maybe not in the setup, but as evidenced by an observation from BEA
support in the old CR#4736567, infinite recursions in WLS can be triggered by a self-referential .jsp's!
The point being to give the customer some indication of where in their code (or possibly in BEA's) they should look for the cause of the excessive recursion.
The customer has already rolled back their latest application software
change to the previous version, and has not seen another stack overflow
since, but has not had any significant client load on that WLS instance
either during the day, so this alone does not imply much. I expect,
however, that the cause (the deep recursion) is absent in this previous
app software version, and thus a debug JVM with this older app software
version running on top would not gather any useful data, and would just
leave both us and the customer in doubt about the definitive cause for
longer. Customer's primary short-term goal is to understand the failure
mechanism before Monday morning (preferably tonight) so that they can
continue production next week without having to worry about crashes every
couple of hours.
###@###.### 2005-2-05 20:18:17 GMT
hours. At least four events today. Had been running fine for months
before this, and customer claimed they hadn't changed anything (well,
maybe not in the setup, but as evidenced by an observation from BEA
support in the old CR#4736567, infinite recursions in WLS can be triggered by a self-referential .jsp's!
The point being to give the customer some indication of where in their code (or possibly in BEA's) they should look for the cause of the excessive recursion.
The customer has already rolled back their latest application software
change to the previous version, and has not seen another stack overflow
since, but has not had any significant client load on that WLS instance
either during the day, so this alone does not imply much. I expect,
however, that the cause (the deep recursion) is absent in this previous
app software version, and thus a debug JVM with this older app software
version running on top would not gather any useful data, and would just
leave both us and the customer in doubt about the definitive cause for
longer. Customer's primary short-term goal is to understand the failure
mechanism before Monday morning (preferably tonight) so that they can
continue production next week without having to worry about crashes every
couple of hours.
###@###.### 2005-2-05 20:18:17 GMT
- duplicates
-
JDK-4402735 [server] stack yellow zone not re-enabled after a StackOverflowError
- Closed