|
This problem is caused by something external to Sakai and is not specific to the 2.6 release (problem is now cropping up in 2.5.x as well).
Beth, just so i am clear, this is not really a blocker for 2.6.0 right? As you know we are cutting rc05 hopefully today or tomorrow, so need to make sure.
Given that this issue was not caused by any changes to the Sakai code-base, and that it exists in 2.5.x (and probably 2.4.x), due to external events, I would not consider this a blocker. But it is serious problem, so I've left it as 'critical' -- but feel free to debate the pros/cons of this.
Hi Beth-- We had students who started creating free form portfolios last year. Now, with this error, they are not only unable to continue working on their portfolios, they are also unable to view the work that has been completed to date (they are getting the same stack trace when they click on a portfolio that uses free-form layouts). It is certainly very important that this be fixed.
http://www.w3.org/2005/06/blog/systeam/2008/02/08/w3c_s_excessive_dtd_traffic
http://www.outofcontrol.ca/2009/02/20/w3org-dtdxhtml1-strictdtd-blocks-windows-ie-users/ looks like a temporary work around would be to use something other than IE. No, it happens with any browser.
I think I've got a fix ready, just doing more testing locally.
If you want a quick diff of the changes, you can look at the following commit (committing to IU code, but the changes should be the same anywhere)
http://source.sakaiproject.org/viewsvn/?view=rev&rev=63855 This turns out to only a partial fix. Still working.
Ok, here's a patch (
r64456
Adding a resolver to find dtds in a local catalog. Fix verified -- please merge to 2.6.x
Follow instructions in description to replicate. Seen on 2.6.x Nightly - http://nightly2.sakaiproject.org:8087/portal as well as on 2.5.x - http://nightly2.sakaiproject.org:8081/portal
Stack trace as is same as attached. Why did this get reopened? It's fixed in trunk and has been verified. It just needs to be merged back to 2.6 and/or 2.5.
My mistake, just needed to read ticket.
I've just verified this as working on a 2.6.x local test server, working in a trunk nightly, and broken in stock 2.6.x. Will merge to 2.6.x.
Can we get this merged to the 2.5.x branch also since this bug affects it as well?
I just set up a new install on 09/20/2009 of 2.6.0. This error is occurring as listed above. I see the patch above but I just started learning Sakai and I don't know how to put the patch to work. I have searched as much as I can with no luck. Please excuse my newness and let me know how to put the patch to work or at least point me in the right direction. Thank you
Tagging correct versions and assigning to OSP JIRA Team. This also needs verification on a 2.6.x nightly / qa. It also needs 2.5.x merge.
I merged your patch to our 2.5.x. Everything seems to work for this version as well. I had to change the path in the catalog.xml file though.
I added the patch for 2.5.x to this issue. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Closed
Critical
Free-form Portfolio Tool Stack Trace on Add Page
URL: http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1149)