Randy,
Thanks for your response. I'll test 2.1.3 POST branch and let you know. I've 
attached the exception in this email. I added the following bean definition in 
/assembly/cache.xml, for back backward compatibility of the 'Concurrement 
Modification Exception' change.

pageManagerOidCache
pageManagerPathCache
ehPageManagerOidCache
ehPageManagerPathCache

Regards

Balaji

--- On Tue, 6/2/09, [email protected] <[email protected]> wrote:

From: [email protected] <[email protected]>
Subject: Re: Jira Ticket JS2-761- Portal Fail To Come Up
To: "Jetspeed Users List" <[email protected]>
Date: Tuesday, June 2, 2009, 1:56 PM


Balaji,

I would think that the changes discussed here are complementary. If we were to 
address this by moving 2.2 work to 2.1.X, it would be done in the 2.1.3-POST 
branch. Would you consider using the 2.1.3-POST branch in its entirety?

Also, posting errors you received, both the original CME and bean init errors, 
might be helpul to us.

Randy

--- [email protected] wrote:

From: Balaji Chockalingam <[email protected]>
To: [email protected]
Subject: Jira Ticket JS2-761- Portal Fail To Come Up
Date: Tue, 2 Jun 2009 08:43:03 -0700 (PDT)

Hi,
Recently I received ‘Concurrent Modification exception’ when I tried to export 
psml pages from portal database to file system. I found  a similar  issue 
addressed in JIRA ticket https://issues.apache.org/jira/browse/JS2-761. But 
this fix is applied only to the trunk and I believe it will be available in the 
latest release 2.2. 
 
I'm using Jetspeed portal version 2.1.3 along with the fix from database page 
manager cache where it’s been refactored to use ehcache from 2.1.3-POSTRELEASE. 
To resolve the issue of concurrent modification exception, I downloaded the 
files listed in JIRA ticket JS2-761, and merged it with the version we have. 
After merge, I try to bring up tomcat, found that the changes made to 
fix concurrent modification exception issue are not backward compatible, and so 
the portal fails to come up, since several beans fail to initialize.
 
Please let me know if changes listed in JIRA ticket JS2-761 can work with the 
version I use(2.1.3 + fix from database page manager cache refactored to use 
ehcache from 2.1.3 POSTRELEASE)
 
Thanks & Regards
 
Balaji







      
type Exception report

message

description The server encountered an internal error () that prevented it from 
fulfilling this request.

exception

javax.servlet.ServletException: Fatal error encountered while processing portal 
request: org.apache.jetspeed.pipeline.PipelineException: Falied to create 
capabilitied:  We were unable to build a capability map for the agent, 
Mozilla/4.0.  This might be an indiciation that the capability database has not 
been correctly initialized.
        
org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:251)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        
org.apache.jetspeed.engine.servlet.XXSUrlAttackFilter.doFilter(XXSUrlAttackFilter.java:52)

root cause

org.apache.jetspeed.pipeline.PipelineException: Falied to create capabilitied:  
We were unable to build a capability map for the agent, Mozilla/4.0.  This 
might be an indiciation that the capability database has not been correctly 
initialized.
        
org.apache.jetspeed.capabilities.impl.CapabilityValveImpl.invoke(CapabilityValveImpl.java:69)
        
org.apache.jetspeed.pipeline.JetspeedPipeline$Invocation.invokeNext(JetspeedPipeline.java:167)
        
org.apache.jetspeed.pipeline.JetspeedPipeline.invoke(JetspeedPipeline.java:146)
        
org.apache.jetspeed.engine.JetspeedEngine.service(JetspeedEngine.java:227)
        
org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:242)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        
org.apache.jetspeed.engine.servlet.XXSUrlAttackFilter.doFilter(XXSUrlAttackFilter.java:52)

root cause

org.apache.jetspeed.capabilities.UnableToBuildCapabilityMapException: We were 
unable to build a capability map for the agent, Mozilla/4.0.  This might be an 
indiciation that the capability database has not been correctly initialized.
        
org.apache.jetspeed.capabilities.impl.JetspeedCapabilities.getCapabilityMap(JetspeedCapabilities.java:263)
        sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
        
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
        java.lang.reflect.Method.invoke(Method.java:585)
        
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:304)
        
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:172)
        
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:139)
        
org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:107)
        
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:161)
        
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
        $Proxy10.getCapabilityMap(Unknown Source)
        
org.apache.jetspeed.capabilities.impl.CapabilityValveImpl.invoke(CapabilityValveImpl.java:65)
        
org.apache.jetspeed.pipeline.JetspeedPipeline$Invocation.invokeNext(JetspeedPipeline.java:167)
        
org.apache.jetspeed.pipeline.JetspeedPipeline.invoke(JetspeedPipeline.java:146)
        
org.apache.jetspeed.engine.JetspeedEngine.service(JetspeedEngine.java:227)
        
org.apache.jetspeed.engine.JetspeedServlet.doGet(JetspeedServlet.java:242)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:690)
        javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
        
org.apache.jetspeed.engine.servlet.XXSUrlAttackFilter.doFilter(XXSUrlAttackFilter.java:52)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to