[JBoss JIRA] Created: (GTNPORTAL-539) Can not login to another configured portal when upgrate to Gatein Beta05
by Hung Nguyen (JIRA)
Can not login to another configured portal when upgrate to Gatein Beta05
------------------------------------------------------------------------
Key: GTNPORTAL-539
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-539
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta05
Reporter: Hung Nguyen
I configured ksdemo portal and it is working well with Gatein Beta04 but when upgrade to Beta05 I got the exception when starting server and can not login to ksdemo portal. The default portal is still working
The exception when starting Tomcat:
org.picketlink.idm.common.exception.IdentityException: Cannot find configured realm with a given nam
e: realm_ksdemo
at org.picketlink.idm.impl.api.IdentitySessionFactoryImpl.createIdentitySession(IdentitySess
ionFactoryImpl.java:70)
at org.picketlink.idm.impl.api.IdentitySessionFactoryImpl.getCurrentIdentitySession(Identity
SessionFactoryImpl.java:97)
at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(Pic
ketLinkIDMServiceImpl.java:143)
at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.startReque
st(PicketLinkIDMOrganizationServiceImpl.java:136)
at org.exoplatform.container.component.RequestLifeCycle.doBegin(RequestLifeCycle.java:55)
at org.exoplatform.container.component.RequestLifeCycleStack.begin(RequestLifeCycleStack.jav
a:57)
at org.exoplatform.container.component.RequestLifeCycle.begin(RequestLifeCycle.java:127)
at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.start(Pick
etLinkIDMOrganizationServiceImpl.java:93)
at sun.reflect.GeneratedMethodAccessor44.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.picocontainer.defaults.LifecycleVisitor.traverse(LifecycleVisitor.java:75)
at org.picocontainer.defaults.LifecycleVisitor.start(LifecycleVisitor.java:113)
at org.picocontainer.defaults.DefaultPicoContainer.start(DefaultPicoContainer.java:369)
at org.exoplatform.container.PortalContainer.start(PortalContainer.java:537)
at org.exoplatform.container.RootContainer.createPortalContainer(RootContainer.java:349)
at org.exoplatform.container.RootContainer.createPortalContainers(RootContainer.java:243)
at org.exoplatform.container.web.PortalContainerCreator.contextInitialized(PortalContainerCr
eator.java:55)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3843)
......
The Exception when login ksdemo portal
INFO: Parameter concurrency-level was not found in configuration, default 16 will be used.
org.picketlink.idm.common.exception.IdentityException: Cannot find configured realm with a given nam
e: realm_ksdemo
at org.picketlink.idm.impl.api.IdentitySessionFactoryImpl.createIdentitySession(IdentitySess
ionFactoryImpl.java:70)
at org.picketlink.idm.impl.api.IdentitySessionFactoryImpl.getCurrentIdentitySession(Identity
SessionFactoryImpl.java:97)
at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(Pic
ketLinkIDMServiceImpl.java:143)
at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.startReque
st(PicketLinkIDMOrganizationServiceImpl.java:136)
at org.exoplatform.container.component.RequestLifeCycle.doBegin(RequestLifeCycle.java:55)
at org.exoplatform.container.component.RequestLifeCycleStack.begin(RequestLifeCycleStack.jav
a:57)
at org.exoplatform.container.component.RequestLifeCycle.begin(RequestLifeCycle.java:127)
at org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl.begin(Organizati
onAuthenticatorImpl.java:144)
at org.exoplatform.services.organization.auth.OrganizationAuthenticatorImpl.validateUser(Org
anizationAuthenticatorImpl.java:130)
at org.exoplatform.services.security.jaas.SharedStateLoginModule.login(SharedStateLoginModul
e.java:68)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:363)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
58)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
va:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
20-01-2010 11:06:25 org.exoplatform.services.security.jaas.DefaultLoginModule login
SEVERE: Cannot find configured realm with a given name: realm_ksdemo
20-01-2010 11:06:25 org.apache.catalina.realm.JAASRealm authenticate
WARNING: Login exception authenticating username "root"
javax.security.auth.login.LoginException: Cannot find configured realm with a given name: realm_ksde
mo
at org.exoplatform.services.security.jaas.SharedStateLoginModule.login(SharedStateLoginModul
e.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769)
at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186)
at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680)
at javax.security.auth.login.LoginContext.login(LoginContext.java:579)
at org.apache.catalina.realm.JAASRealm.authenticate(JAASRealm.java:363)
at org.apache.catalina.authenticator.FormAuthenticator.authenticate(FormAuthenticator.java:2
58)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:417)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.ja
va:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
at java.lang.Thread.run(Thread.java:619)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-273) Still edit navigation of portal which was deleted
by Hang Nguyen (JIRA)
Still edit navigation of portal which was deleted
-------------------------------------------------
Key: GTNPORTAL-273
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-273
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta02
Reporter: Hang Nguyen
Fix For: 3.0.0-Beta03
Steps:
- Go to Portal navigation --> create new portal: aaa --> click delete this portal --> continue click edit navigation --> portal has been deleted --> and show Navigation Management form --> click save button --> unknown error.
Show exception:
java.lang.IllegalArgumentException: Cannot insert page navigation as the corresponding portal aaa
ith type ObjectType[interface org.gatein.mop.api.workspace.Site] does not exist
at org.exoplatform.portal.pom.config.tasks.PageNavigationTask$Save.run(PageNavigationTask.ja
va:171)
at org.exoplatform.portal.pom.config.POMSession.execute(POMSession.java:373)
at org.exoplatform.portal.pom.config.ExecutorDispatcher.execute(ExecutorDispatcher.java:41)
at org.exoplatform.portal.pom.config.TaskExecutionDecorator.execute(TaskExecutionDecorator.j
ava:36)
at org.exoplatform.portal.pom.config.cache.DataCache.write(DataCache.java:84)
at org.exoplatform.portal.pom.config.cache.DataCache.execute(DataCache.java:58)
at org.exoplatform.portal.pom.config.POMDataStorage.execute(POMDataStorage.java:122)
at org.exoplatform.portal.pom.config.POMDataStorage.save(POMDataStorage.java:181)
at org.exoplatform.portal.config.DataStorageImpl.save(DataStorageImpl.java:122)
at org.exoplatform.portal.config.UserPortalConfigService.update(UserPortalConfigService.java
:411)
at org.exoplatform.portal.webui.navigation.UINavigationManagement$SaveActionListener.execute
(UINavigationManagement.java:98)
at org.exoplatform.webui.event.Event.broadcast(Event.java:89)
at org.exoplatform.webui.core.lifecycle.Lifecycle.processAction(Lifecycle.java:56)
at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:124)
at org.exoplatform.webui.core.lifecycle.UIApplicationLifecycle.processAction(UIApplicationLi
fecycle.java:58)
at org.exoplatform.webui.core.UIComponent.processAction(UIComponent.java:124)
at org.exoplatform.webui.core.UIApplication.processAction(UIApplication.java:112)
at org.exoplatform.webui.application.portlet.PortletApplication.processAction(PortletApplica
tion.java:167)
at org.exoplatform.webui.application.portlet.PortletApplicationController.processAction(Port
letApplicationController.java:80)
at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerI
mpl.java:557)
at org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:109)
at org.gatein.pc.portlet.impl.jsr168.api.FilterChainImpl.doFilter(FilterChainImpl.java:72)
at org.gatein.pc.portlet.impl.jsr168.PortletContainerImpl.dispatch(PortletContainerImpl.java
:505)
at org.gatein.pc.portlet.container.ContainerPortletDispatcher.invoke(ContainerPortletDispatc
her.java:42)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.EventPayloadInterceptor.invoke(EventPayloadInterceptor.java
:196)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.RequestAttributeConversationInterceptor.invoke(RequestAttri
buteConversationInterceptor.java:119)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.CCPPInterceptor.invoke(CCPPInterceptor.java:65)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor.access$001(ContextDispatcherIn
terceptor.java:49)
at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor$1.doCallback(ContextDispatcher
Interceptor.java:123)
at org.gatein.wci.command.CommandDispatcher$CallbackCommand.execute(CommandDispatcher.java:8
2)
at sun.reflect.GeneratedMethodAccessor72.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.gatein.wci.command.CommandServlet.doGet(CommandServlet.java:135)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j
ava:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:646)
at org.apache.catalina.core.ApplicationDispatcher.doInclude(ApplicationDispatcher.java:551)
at org.apache.catalina.core.ApplicationDispatcher.include(ApplicationDispatcher.java:488)
at org.gatein.wci.command.CommandServlet.include(CommandServlet.java:84)
at org.gatein.wci.command.CommandDispatcher.include(CommandDispatcher.java:58)
at org.gatein.wci.tomcat.TC6ServletContainerContext.include(TC6ServletContainerContext.java:
86)
at org.gatein.wci.impl.DefaultServletContainer.include(DefaultServletContainer.java:190)
at org.gatein.pc.portlet.impl.spi.AbstractServerContext.dispatch(AbstractServerContext.java:
69)
at org.gatein.pc.portlet.aspects.ContextDispatcherInterceptor.invoke(ContextDispatcherInterc
eptor.java:77)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.SecureTransportInterceptor.invoke(SecureTransportIntercepto
r.java:69)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.ValveInterceptor.invoke(ValveInterceptor.java:75)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.container.ContainerPortletInvoker.invoke(ContainerPortletInvoker.ja
va:117)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.state.producer.ProducerPortletInvoker.invoke(ProducerPortletInvoker
.java:230)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.PortletCustomizationInterceptor.invoke(PortletCustomization
Interceptor.java:76)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.portlet.aspects.ConsumerCacheInterceptor.invoke(ConsumerCacheInterceptor.ja
va:229)
at org.gatein.pc.portlet.PortletInvokerInterceptor.invoke(PortletInvokerInterceptor.java:87)
at org.gatein.pc.federation.impl.FederatedPortletInvokerService.invoke(FederatedPortletInvok
erService.java:152)
at org.gatein.pc.federation.impl.FederatingPortletInvokerService.invoke(FederatingPortletInv
okerService.java:173)
at org.exoplatform.portal.webui.application.UIPortlet.invoke(UIPortlet.java:837)
at org.exoplatform.portal.webui.application.UIPortletActionListener$ProcessActionActionListe
ner.execute(UIPortletActionListener.java:98)
at org.exoplatform.webui.event.Event.broadcast(Event.java:89)
at org.exoplatform.portal.webui.application.UIPortletLifecycle.processAction(UIPortletLifecy
cle.java:118)
at org.exoplatform.portal.webui.application.UIPortletLifecycle.processAction(UIPortletLifecy
cle.java:54)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-506) Performance tuning of navigation portlet
by Marek Posolda (JIRA)
Performance tuning of navigation portlet
----------------------------------------
Key: GTNPORTAL-506
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-506
Project: GateIn Portal
Issue Type: Task
Affects Versions: 3.0.0-Beta04
Environment: Ubuntu linux,
Sun JDK 1.6,
EAP5 with GateIn from trunk (revision 1165) deployed
Reporter: Marek Posolda
Fix For: 3.0.0-CR01
There is small performance degradation for each visible page on navigation portlet (navigation bar). Since method getPage from UserPortalConfigService is called for each visible page on navigation bar and it costs some time even if pages are cached. so rendering of UINavigationPortlet costs more time.
Degradation is not big. When the request is sent to page on portal with only 2 visible pages on navigation bar, then maximum throughput was 527.8 requests/s. If there are 6 visible pages on navigation bar, then maximum throghput is 491.9 requests/s. So small difference but it's here.
Performance degradation is not here, when pages are configured to be non-visible in portal.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month
[JBoss JIRA] Created: (GTNPORTAL-338) tune getAllPortalNames method in UserPortalConfigService
by Prabhat Jha (JIRA)
tune getAllPortalNames method in UserPortalConfigService
--------------------------------------------------------
Key: GTNPORTAL-338
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-338
Project: GateIn Portal
Issue Type: Bug
Affects Versions: 3.0.0-Beta03
Reporter: Prabhat Jha
Fix For: 3.0.0-Beta04
Related jira is https://jira.jboss.org/jira/browse/JBQA-2887 which may not be accessible to all of you so here are details:
I did some profiling with JProfiler. There is no difference between the case with different users and same users test. The biggest bottleneck is the "getAllPortalNames" bottleneck. During processing of HTTP request to the sample page, then about 90% of time is spent in method "getAllPortalNames" from class "org.exoplatfrom.portal.config.UserPortalConfigService". Each call to this method performs several calls to eXo JCR DB. There is no caching here.
Please let me know if a separate jira is needed for following profiling:
I tried to do the test and profiling with Chromattic options disabled and enabled. Chromattic options are four JVM options which can be added to server JVM args to optimize Chromattic library to use caching and avoid calls to eXo JCR DB. Namely these options are here:
-Dorg.chromattic.api.Option.optimize.jcr.enabled=true
-Dorg.chromattic.api.Option.optimize.jcr.has_property.enabled=true
-Dorg.chromattic.api.Option.optimize.jcr.has_node.enabled=true
-Dorg.chromattic.api.Option.cache.state.enabled=true
I verified that there is no any performance improvement with these options enabled and calls to eXo JCR SB are still here. I did some profling and debugging and here are the more detailed results:
1) Significant amount of time is spent in the method getProperty in class org.chromattic.core.jcr.SessionWrapperImpl.
public Property getProperty(Node node, String relPath) throws RepositoryException {
if (hasPropertyOptimized) {
return node.getProperty(relPath);
} else {
if (node.hasProperty(relPath)) {
return node.getProperty(relPath);
}
1.a) if chromattic options are disabled (hasPropertyOptimized==false to be more precise), then method node.hasProperty(relPath) performs call to eXo DB but method node.getProperty(relPath) doesn't perform any additional calls to DB, because data are cached inside of cache in org.exoplatform.services.jcr.impl.dataflow.persistent.CacheableWorkspaceDataManager.
1.b) if chromattic options are enabled, then only method node.getProperty(relPath) is called but this method performs calls to DB because these data are not cached inside CacheableWorkspaceDataManager.
So the conclusion is, that there is no any benefit when hasPropertyOptimized is true.
2) If cacheState is enabled (option -Dorg.chromattic.api.Option.cache.state.enabled=true) then there is non-null variable "propertyCache" inside "org.chromattic.core.PersistentEntityContextState". When method "getPropertyValue" on class "PersistentEntityContextState" is called, then nothing is found inside the cache and founded items are not saved to propertyCache.
New items are put to propertyCache only when "setPropertyValue" is called, but this method is not called during HTTP request processing. So the propertyCache is always empty.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 1 month