[PLUTO-172] Unexpected test results in new Pluto installation

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Won't Fix
• Affects Version/s: 1.0.1-rc4
• Component/s: portlets-testsuite
• Environment: Windows XP, Tomcat 5.5.9, JDK 1.5.0
• Assignee: Unassigned
• Reporter: Graham klyne
• Created: 05/Oct/05 01:20
• Updated: 22/Feb/07 04:58
• Resolved: 05/Nov/05 07:08

Description

These are some observations which may or may not be bugs.

I have Pluto installed and running on the above configuration. I have edited the Tomcat conf/server.xml to include:

[[
<Connector port="8080"
maxHttpHeaderSize="8192"
maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
enableLookups="false" redirectPort="8443" acceptCount="100"
connectionTimeout="20000" disableUploadTimeout="true"
emptySessionPath="true" />
]]
(and stopped/restarted Tomcat after editing the file.)

Most of the tests pass OK, but a couple are giving unexpected results:

1. The "Application Scoped Session Attributes Test" still fails, despite the server.xml edit noted above

2. The "Security mapping test" shows yellow until I log in to Pluto (or Tomcat?), then shows green. (Using the Pluto login link and entering the Tomcat admin username/password gives an acccess denied message, so I went to to Tomcat status page that usually requires a login, but not in this case. I'm not sure what is significant here.)

3. Click "Dispatcher Render Parameter Test" in portlet 2 - test passes; then "Simple Parameter Test" in portlet 1 - this test passes, but the portlet 2 display changes to failed. Is this a software bug or a test bug?

#g