[WG: Sakai QA] [Building Sakai] Webdav protocol inconsistencies between QA servers.
Stephen Marquard
stephen.marquard at uct.ac.za
Thu Jan 7 06:47:43 PST 2010
Hi,
Correctly guessed, the Fatal Error is from the XML parser. I'm not sure
how to make it log to log4j (if that's even possible).
It's probably related to the locking and/or properties code. It's a
result of the litmus test feeding it invalid data to check correct error
handling (though the locks and props code are both known to be
incomplete anyway).
Cheers
Stephen
>>> Jean-Francois Leveque <jean-francois.leveque at upmc.fr> 2010/01/07
04:42 PM >>>
Hi all,
I would guess the "[Fatal Error]" isn't related to SAK-5075.
Looks like an XML error message. See what google has to say about "XML
document structures must start and end within the same entity".
Where and when does it happen?
Anyone more knowledgeable?
Cheers,
J-F
Berg, A.M. a écrit :
> Hi Jean Francois,
>
> I believe you said that sak-5075 was added to trunk. I just tested
trunk
> behind Apache and it passed one more litmus test (copymove 10)
compared
> to 2-7.0 M2. There was also mentioned some logging for Fatal, but
that
> feels like it is using stdout rather than log4j.
>
> Find enclosed results. At the very least the Fatal error should give
> more context information for system admins.
>
> qa1-nl column are the old results. new:8080 is without Apache on
qa1-nl
> trunk and mod_jk is with Apache.
>
> 2010-01-06 17:07:36,561 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:36,568 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> [Fatal Error] :1:6: XML document structures must start and end within
> the same entity.
> [Fatal Error] :1:57: The value of the attribute
> "prefix="xmlns",localpart="bar",rawname="xmlns:bar"" is invalid.
> Prefixed namespace bindings may not be empty.
> 2010-01-06 17:07:37,308 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:37,433 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:37,886 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:38,304 WARN http-8080-Processor19
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:38,328 WARN http-8080-Processor19
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> [Fatal Error] :1:1: Premature end of file.
> 2010-01-06 17:07:38,756 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:38,982 WARN http-8080-Processor19
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,129 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,169 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,276 WARN http-8080-Processor21
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,552 WARN http-8080-Processor20
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,919 WARN http-8080-Processor19
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> 2010-01-06 17:07:39,955 WARN http-8080-Processor19
> org.sakaiproject.content.impl.BaseContentService - SiteService could
not
> find the site type
> [Fatal Error] :1:1: Premature end
of file.
> [Fatal Error] :1:1: Premature end of file.
>
> Alan
>
> Alan Berg
> Interim QA Director - The Sakai Foundation
>
> Senior Developer / Quality Assurance
> Group Education and Research Services
> Central Computer Services
> University of Amsterdam
>
> http://home.uva.nl/a.m.berg
>
>
>
>
> -----Original Message-----
> From: Jean-Francois Leveque [mailto:jean-francois.leveque at upmc.fr]
> Sent: Tue 1/5/2010 11:06
> To: Berg, A.M.
> Cc: Charles Hedrick; Sakai QA; Sakai Mailing List Dev
> Subject: Re: [WG: Sakai QA] Webdav protocol inconsistencies between
QA
> servers.
>
> Hi all,
>
> Alan, I think one of the differences related to mod_jk may come from
the
> fact that the fix for http://jira.sakaiproject.org/browse/SAK-5075
has
> not been included yet even if reviewed and used by others than the
lead
> for Webdav.
>
> I've been using it since 2.4.x without problems in Apache HTTPD
versions
> older than 2.2.8 (I currently use 2.2.3 with mod_proxy_ajp). Others
than
> myself have commented that it's safe and advocated for its
inclusion.
>
> Is there any reason not to include this fix?
>
> Maybe the Sakai version, Mod_jk and SSL information could be added
with
> each server ID and we could sort by most failure-related parameters
to
> get a better picture. What do you think, Alan?
>
> Cheers,
>
> J-F
>
> Berg, A.M. a écrit :
> > Hi all,
> >
> > More for background information: I have checked various Sakai Qa
servers
> > including nightly for webdav protocol compatibility via the litmus
tool
> > and then parsed the results into an HTML table
> > (http://builds.sakaiproject.org/litmus/2010/1/). There is some
variation
> > between servers due to what I assume is Sakai version, Mod_jk and
SSL
> > connections and other unknown factors. Therefore, if you are
debugging
> > webdav/browser issues it is well worth checking across a range of
> > relevant servers.
> >
> > I will write a Jira that is unassigned and if anyone works
towards
> > improving protocol consistency can then use it to act as an
umbrella.
> >
> > Alan
> >
> > Alan Berg
> > Interim QA Director - The Sakai Foundation
> >
> > Senior Developer / Quality Assurance
> > Group Education and Research Services
> > Central Computer Services
> > University of Amsterdam
> >
> > http://home.uva.nl/a.m.berg
>
>
>
>
------------------------------------------------------------------------
>
> TEST qa1-nl.sakaiproject.org new_mod_jk new:8080
> basic_0 pass pass pass
> basic_1 pass pass pass
> basic_2 pass pass pass
> basic_3 pass pass pass
> basic_4 pass pass pass
> basic_5 pass pass pass
> basic_6 pass pass pass
> basic_7 pass pass pass
> basic_8 pass pass pass
> basic_9 FAILED FAILED pass
> basic_10 pass pass pass
> basic_11 pass pass pass
> basic_12 pass pass pass
> basic_13 pass pass pass
> basic_14 pass pass pass
> basic_15 pass pass pass
> copymove_0 pass pass pass
> copymove_1 pass pass pass
> copymove_2 pass pass pass
> copymove_3 pass pass pass
> copymove_4 pass pass pass
> copymove_5 pass pass pass
> copymove_6 pass pass pass
> copymove_7 pass pass pass
> copymove_8 pass pass pass
> copymove_9 pass pass pass
> copymove_10 FAILED pass pass
> copymove_11 pass pass pass
> copymove_12 pass pass pass
> http_0 pass pass pass
> http_1 pass pass pass
> http_2 pass pass pass
> http_3 pass pass pass
> locks_0 pass pass pass
> locks_1 pass pass pass
> locks_2 pass pass pass
> locks_3 pass pass pass
> locks_4 pass pass pass
> locks_5 pass pass pass
> locks_6 pass pass pass
> locks_7 pass pass pass
> locks_8 pass pass pass
> locks_9 pass pass pass
> locks_10 pass pass pass
> locks_11 pass pass pass
> locks_12 pass pass pass
> locks_13 pass pass pass
> locks_14 pass pass pass
> locks_15 SKIPPED SKIPPED SKIPPED
> locks_16 SKIPPED SKIPPED SKIPPED
> locks_17 pass pass pass
> locks_18 FAILED FAILED FAILED
> locks_19 SKIPPED SKIPPED SKIPPED
> locks_20 SKIPPED SKIPPED SKIPPED
> locks_21 pass p
ass pass
> locks_22 FAILED FAILED FAILED
> locks_23 pass pass pass
> locks_24 pass pass pass
> locks_25 pass pass pass
> locks_26 pass pass pass
> locks_27 FAILED FAILED FAILED
> locks_28 pass pass pass
> locks_29 pass pass pass
> locks_30 pass pass pass
> locks_31 pass pass pass
> locks_32 pass pass pass
> locks_33 pass pass pass
> locks_34 FAILED FAILED FAILED
> locks_35 pass pass pass
> locks_36 FAILED FAILED FAILED
> locks_37 pass pass pass
> locks_38 pass pass pass
> locks_39 pass pass pass
> locks_40 pass pass pass
> props_0 pass pass pass
> props_1 pass pass pass
> props_2 pass pass pass
> props_3 pass pass pass
> props_4 pass pass pass
> props_5 pass pass pass
> props_6 pass pass pass
> props_7 FAILED FAILED FAILED
> props_8 pass pass pass
> props_9 pass pass pass
> props_10 FAILED FAILED FAILED
> props_11 pass pass pass
> props_12 FAILED FAILED FAILED
> props_13 pass pass pass
> props_14 FAILED FAILED FAILED
> props_15 pass pass pass
> props_16 FAILED FAILED FAILED
> props_17 pass pass pass
> props_18 FAILED FAILED FAILED
> props_19 pass pass pass
> props_20 FAILED FAILED FAILED
> props_21 pass pass pass
> props_22 FAILED FAILED FAILED
> props_23 pass pass pass
> props_24 pass pass pass
> props_25 pass pass pass
> props_26 FAILED FAILED FAILED
> props_27 FAILED FAILED FAILED
> props_28 pass pass pass
> props_29 pass pass pass
>
_______________________________________________
sakai-dev mailing list
sakai-dev at collab.sakaiproject.org
http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
TO UNSUBSCRIBE: send email to
sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
"unsubscribe"
More information about the sakai-qa
mailing list