Hi Igor,
Interesting to find out how you disabled it. I am myself facing issues with
C2.2 and RCL. This might have been caused by upgrading to Maven3 which again
seems to have issues with the maven-jetty-plugin. So after some googling
yesterday I switched to a newer jetty-maven-plugin (yes... it's renamed ;-))
but this gave me following stack trace:
[INFO] Webapp source directory =
C:\development\workspaces\intellij11\CTPI-PX\spider2\shared\target\rcl\webapp
[INFO] Reload Mechanic: automatic
[INFO] Classes =
C:\development\workspaces\intellij11\CTPI-PX\spider2\shared\target\classes
[INFO] Context path = /
[INFO] Tmp directory =
C:\development\workspaces\intellij11\CTPI-PX\spider2\shared\target\tmp
[INFO] Web defaults = org/eclipse/jetty/webapp/webdefault.xml
[INFO] Web overrides = none
[INFO] web.xml file =
file:/C:/development/workspaces/intellij11/CTPI-PX/spider2/shared/target/rcl/webapp/WEB-INF/web.xml
[INFO] Webapp directory =
C:\development\workspaces\intellij11\CTPI-PX\spider2\shared\target\rcl\webapp
2012-03-14 16:32:33.863:INFO:oejs.Server:jetty-8.1.0.RC5
2012-03-14 16:32:35.421:INFO:oejpw.PlusConfiguration:No Transaction manager
found - if your webapp requires one, please configure one.
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingClassloaderCreationException:
Error while creating the URLClassLoader from
context://WEB-INF/cocoon/rclwrapper.urlc
l.conf
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingClassloaderManager.createURLClassLoader(ReloadingClassloaderManager.java:101)
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingClassloaderManager.getClassLoader(ReloadingClassloaderManager.java:50)
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.invoke(ReloadingListener.java:148)
at
org.apache.cocoon.tools.rcl.wrapper.servlet.ReloadingListener.attributeAdded(ReloadingListener.java:283)
at
org.eclipse.jetty.server.handler.ContextHandler$Context.setAttribute(ContextHandler.java:2040)
at org.apache.jasper.runtime.TldScanner.onStartup(TldScanner.java:241)
at
org.eclipse.jetty.plus.annotation.ContainerInitializer.callStartup(ContainerInitializer.java:100)
at
org.eclipse.jetty.annotations.ServletContainerInitializerListener.contextInitialized(ServletContainerInitializerListener.java:99)
at
org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:764)
at
org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:406)
Does anyone know if the latest jetty plugin supports a nice reload mechanism as
I noticed this INFO message:
[INFO] Reload Mechanic: automatic
Robby
-----Original Message-----
From: Igor Malinin [mailto:igor...@gmail.com]
Sent: Thursday, March 15, 2012 9:13 AM
To: dev@cocoon.apache.org
Subject: Re: [C3] Concurrency issues with ComponentProvider
On 2012-03-15 4:25, Thorsten Scherler wrote:
> I think the key is the <map:match pattern="**.*"> which is a welcome
> door for concurrency issues. You need to request the page around 10
> times and you see image glitches.
>
> I started a small testing project but will need to finish it later.
> BTW I created https://issues.apache.org/jira/browse/COCOON3-93 to keep
> track of the issue.
By the way, do you use Reloading Classloader (RCL) in your application?
I've had too many issues with it totally breaking Spring context... If
you use it it would be good to confirm that the problem exists without it.
