[GLASSFISH-15416] [STRESS] specjent2010 run against b36 failed Created: 03/Jan/11 Updated: 05/Jan/11 Resolved: 05/Jan/11
|Affects Version/s:||future release|
|Remaining Estimate:||Not Specified|
|Time Spent:||Not Specified|
|Original Estimate:||Not Specified|
solaris sparc jdk 6u22
The following is the logs and configuration of a faild specjent2010 run against b36.
Please note that there are exceptions which are specj's
Physical location: /net/asqe-logs.us.oracle.com/export1/gms/alacrity.logs_dec_30_solaris_single_run2/results.specjent2010/results_1/driver-results/37/logs/jed-asqe-29/
Please evaluate the logs for addressing possible issues.
This is the log and configuration of a successful 7-day longevity run of specjent10 against b33.
|Comment by Nazrul [ 03/Jan/11 ]|
Amit: Are you seeing this type of issues when you run SPECj?
|Comment by zorro [ 03/Jan/11 ]|
Note: Specj determines pass/fail according to the information in the summary.xml as stated below.
39 passed true
33 passed true
|Comment by Nazrul [ 04/Jan/11 ]|
We are not supposed to run SPECj application in HA mode.
Looking at the server log, it looks like we are running into serialization issues:
[#|2010-12-30T20:15:50.516-0800|INFO|oracle-glassfish3.1|org.apache.catalina.session.ManagerBase|_ThreadID=78;_ThreadName=Thread-1;|PWC2785: Cannot serialize session attribute specUtils for session aa2a28e143662004d431d1cb7a4a
Do you use manual steps to setup the SPECj application?
|Comment by zorro [ 04/Jan/11 ]|
There is no manual setup.
|Comment by amitagarwal [ 05/Jan/11 ]|
First of all I am not seeing this issue in our setup.
Other exceptions are harmless, they are part of specj runs.
I could run specj against b36 on OEL setup without any issues.
|Comment by Nazrul [ 05/Jan/11 ]|
Closing this as a duplicate of