Meeting minute for July,12 2007 Attendes:Anissa, Sreenivas, Mike, Senthil, Steve, Judy, Anissa, Ken, Ana Agenda for 7/12/2007
- Status and issues relating to Doc.
- QE status
I want to discuss the memory issue that QE run into when running the automated test Developer status
Meeting Detail DOC
- Rajeev is not able to dial in. Here is the status report from him.
1. Search related bugs are fixed. I checked the builds for both Solarisand Windows 2000 and found the Search working. I do not have an XPmachine and hence haven't tested it there. But it should have got fixedbecause this problem seems to have been caused by a file binary calledDOCS.TAB, which was not checked in as a binary.
2. There was a bug to create Index entries for JBI terms. This has alsobeen fixed.
3. We are going thru all the screens again and checking if there any broken links. We found a couple of them and I have sent the screennames to Senthil. The mapping is correct in Helplinks.properties andthe corresponding html files have been checked in.
4. Regression bug 6532532: For now, I have added a note in the help forthe Physical Destinations page. I have mentioned this in the bug description.
- Mike is meeting with the doc writer as he is aware of 2 screens content not correct. Happy with the overall OLH for JBI screen, not great, but fine. There are some bugs relating to JBI runtime, he is trying to document the different use cases that work.
- Anissa checked the OLH.
- Judy request gui team to review Admin Guide. Anissa will contact Rajeev to see if he needs the team to review it.
HIE
- Mike has been testing with IE6, product name is still broken in mashhead, relating to transparency file issue in IE6. IE6 is white text on white background. Mike will file an issue. We will see if we get a new gif and whether checked in.
- Inform Steve that we may need screens for cert. management, but no action needed from Steve till GUI team has decided that will be the one of the new feature for next release.
QE
- Judy mentioned the issue the QE team runs into when doing automated testing. This prevents them to generate complete test report in a timely manner.
1. When running the test continuously, involving deploy/undeploy/redeploy app, they frequently see the out of memory problem. Sujatha has filed a bug reporting this before. 6573563:b50e-promoted EE build: Server crashes and server.log shows NullPointerException
2. Another issue is after running the test for sometims, and did a lot of start/stop domain/cluster/instance etc. the server stopped response, and seems to hang.
Sent the above question to Kedar who suggested to increase heap size and capture server.log when it happened.
There is not much GUI can do in this case, but will keep an eye on it. Developer
- Mike reported that he still sees problem in being logged out of the console randomly. Not easy to reproduce, but will request Priti to do some Selinum test case to see if reproduce consistently.
- Ana also sees the logout problem, and it seems only occurs when running on Window.
- GUI never invalidate the session exception when user specifically logged out, and Ana has confirmed that part of the code was never called. Ken speculates that maybe some limit is reached and causes that.
- Mike also experienced problem when logout button doesn't function properly. After pressing logout, he got a blank screen, and refreshing the browser showed he is still logging in. This is a concern since the JBI code uses a lot of session variable.
- Probably will change the code in the next release to not rely on session variable unless really need to.
|
