[
http://jira.dspace.org/jira/browse/DS-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Ackermann updated DS-253:
---------------------------------
Comment: was deleted
(was: Can someone please summarize the patch procedure recommended at this
point in time? Which of the three attachments should someone apply: 152.patch,
dspace-xmlui-servlet.patch, or patch-custom-cocoon-dependency.patch? If someone
could summarize their positive experiences, that would help me. Thanks!)
> NullPointerException in HttpServletResponseBufferingWrapper (Cocoon bug?)
> -------------------------------------------------------------------------
>
> Key: DS-253
> URL: http://jira.dspace.org/jira/browse/DS-253
> Project: DSpace 1.x
> Issue Type: Bug
> Affects Versions: 1.5.2
> Environment: Ubuntu Linux 8.4, Gentoo Linux 2008.0, maybe others.
> Tomcat 5.5, Tomcat 6
> JDK 1.6, maybe others
> AJP or HTTP proxy from Apache HTTPD (mod_jk and mod_proxy_ajp both tried)
> Reporter: Mark Wood
> Assignee: Mark Diggory
> Attachments: 152.patch, dspace-xmlui-servlet.patch,
> jnet-stacktrace.txt, patch-custom-cocoon-dependency.patch
>
>
> Reported by Sean Carte in
> http://sourceforge.net/mailarchive/forum.php?thread_name=5d9253070906110526h5cb0f74cof17ba0c6b4eb449e%40mail.gmail.com&forum_name=dspace-tech
> This seems to leave an "idle in transaction" DBMS connection each time, which
> leads to a long pause followed by an error page in subsequent requests which
> get that connection from the pool. Some requests go through, many do not.
> There was a very likely suggestion that this is described and fixed in
> https://issues.apache.org/jira/browse/COCOON-2217, leaving the problem of how
> to get that Cocoon fix built into DSpace. Adjusting
> dspace-xmlui/dspace-xmlui-webapp/pom.xml to build against
> cocoon-servlet-service-impl-1.2.0 added a new layer of problem: the Cocoon
> servlet:context element in a Spring application context now requires a schema
> name in the context-path attribute.
> Apparently the context-path should now be "blockcontext:/". However this
> adds a third layer of mystery: the blockcontext schema is not recognized,
> even though sample Cocoon 2.2 code at the Cocoon site employs it
> successfully. An additional complication: it appears that an archive
> becomes a Cocoon block by being named via Cocoon-Block-Name in its manifest,
> but I can't find this being done in DS 1.5.2. So even if we could use
> blockcontext: we would have no block context.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel
