[JBoss JIRA] (GTNPORTAL-3148) JBAS016060 error on JBoss 7.1.x startup
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3148?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3148:
----------------------------------
Sprint: Sprint 77
> JBAS016060 error on JBoss 7.1.x startup
> ---------------------------------------
>
> Key: GTNPORTAL-3148
> URL: https://issues.jboss.org/browse/GTNPORTAL-3148
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Final
> Environment: OS X 10.8, Java 7, JBoss 7.1.3
> Reporter: Dave Heath
> Attachments: test-ear.zip
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Receive the following exception on startup. My EAR project is based on the sample-portal from the gatein quickstarts.
> {code}
> Caused by: java.lang.RuntimeException: JBAS016060: Could not resolve CDI bean for injection point private org.gatein.cdi.CDIPortletContextExtension org.gatein.cdi.contexts.listeners.CDIServletListener.extension with qualifiers []
> at org.jboss.as.weld.injection.WeldEEInjection.createWeldEEInjection(WeldEEInjection.java:161)
> at org.jboss.as.weld.injection.WeldManagedReferenceFactory.start(WeldManagedReferenceFactory.java:127)
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
> ... 3 more
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-2015) NPE when calling Site.getPriority
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2015?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2015:
----------------------------------
Sprint: Sprint 77
> NPE when calling Site.getPriority
> ---------------------------------
>
> Key: GTNPORTAL-2015
> URL: https://issues.jboss.org/browse/GTNPORTAL-2015
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Reporter: Matt Wringe
> Original Estimate: 2 hours
> Remaining Estimate: 2 hours
>
> When calling site.getPriority() it can fail with an NPE:
> 16:54:01,264 ERROR [STDERR] Caused by: java.lang.NullPointerException
> 16:54:01,264 ERROR [STDERR] at org.gatein.portal.api.impl.portal.SiteImpl.getPriority(SiteImpl.java:114)
> 16:54:01,264 ERROR [STDERR] at org.gatein.api.rest.resource.handler.SitesHandler.toSiteResource(SitesHandler.java:85)
> 16:54:01,264 ERROR [STDERR] at org.gatein.api.rest.resource.handler.SitesHandler.createPortalTypeResource(SitesHandler.java:58)
> 16:54:01,264 ERROR [STDERR] at org.gatein.api.rest.service.SitesService.getSiteType(SitesService.java:91)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3044) Inconsistency in html elements of shared layout/user bar portlets
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3044?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3044:
----------------------------------
Sprint: Sprint 77
> Inconsistency in html elements of shared layout/user bar portlets
> -----------------------------------------------------------------
>
> Key: GTNPORTAL-3044
> URL: https://issues.jboss.org/browse/GTNPORTAL-3044
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta02
> Environment: jboss-jpp-6.1.0.ER1-prod-17052013.zip
> Reporter: Vlastislav Ramik
> Labels: JPP61-Test-dev
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Shared layout/user bar portlets (ie the bar that appears at the top of the page when you are a logged-in user) has following inconsistency:
> Portal Actions (that with the redhat icon): {noformat}<li title="Portal Actions" style="width: 62px" class="UITab portlet-menu-item">{noformat} The is also empty link as a child of the <li> but it has zero length.
> Site: {noformat}<a title="Sites" class="SitesIcon TBIcon" href="javascript:;">Site</a>{noformat}
> Group: {noformat}<span title="Group" class="GroupIcon TBIcon">Group</span>{noformat}
> Dashboard: If the user does not have any dashboard pages there is a link. If the user has a dashboard page there is a span. This is correct in my opinion.
> Site/Group/Dashboard Editor: {noformat}<a title="Site/Group/Dashboard Editor" href="#" class="EditorIcon TBIcon">Site/Group/Dashboard Editor</a>{noformat}
> All this leads to different looking cursors when you hovering the portlet.
> Portal Actions: arrow cursor
> Site: link cursor and text is highlighted
> Group:
> - arrow cursor when you are hovering that "people" icon
> - text cursor when you are hovering Group text
> Dashboard:
> - in case of none dashboard pages - it behaves the same as Site
> - in case on any dashboard pages - it behaves the same as Group
> Site/Group/Dashboard Editor: link cursor and text is highlighted
> The solution can be using css cursor (e.g. cursor: pointer; ) but cleaner solution would be probably unify it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3056) JBossCacheWorkspaceStorageCache has to have a different jbosscache-cluster-name for portal-system workspace
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3056?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3056:
----------------------------------
Sprint: Sprint 77
> JBossCacheWorkspaceStorageCache has to have a different jbosscache-cluster-name for portal-system workspace
> -----------------------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3056
> URL: https://issues.jboss.org/browse/GTNPORTAL-3056
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCR integration
> Affects Versions: 3.6.0.Beta02
> Reporter: Vu Viet Phuong
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> We got the following stacktrace when launshing cluster with PLF-4.0.0:
> {code}
> 2013-05-15 10:00:13,200 | ERROR | Error start repository service [e.j.component.core.RepositoryServiceImpl<Catalina-startStop-1>]
> org.exoplatform.services.jcr.config.RepositoryConfigurationException: Repository container repository was not started.
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.createRepository(RepositoryServiceImpl.java:165) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.init(RepositoryServiceImpl.java:323) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.start(RepositoryServiceImpl.java:279) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_30]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_30]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:100) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.LifecycleVisitor.start(LifecycleVisitor.java:170) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ConcurrentPicoContainer.start(ConcurrentPicoContainer.java:554) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:270) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.PortalContainer.start(PortalContainer.java:679) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:258) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.RootContainer.createPortalContainer(RootContainer.java:678) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.RootContainer.createPortalContainers(RootContainer.java:343) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator$1.run(PortalContainersCreator.java:53) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator$1.run(PortalContainersCreator.java:51) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedAction(SecurityHelper.java:290) [exo.kernel.commons-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator.createPortalContainers(PortalContainersCreator.java:51) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator.lifecycleEvent(PortalContainersCreator.java:40) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1140) [catalina.jar:7.0.39]
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) [catalina.jar:7.0.39]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [na:1.6.0_30]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [na:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_30]
> Caused by: org.picocontainer.PicoIntrospectionException: Failed when calling start on org.exoplatform.services.jcr.impl.WorkspaceContainer@5ff92b8e
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:136) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.LifecycleVisitor.start(LifecycleVisitor.java:170) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ConcurrentPicoContainer.start(ConcurrentPicoContainer.java:554) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:270) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.services.jcr.impl.RepositoryContainer.start(RepositoryContainer.java:575) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl$1.run(RepositoryServiceImpl.java:151) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl$1.run(RepositoryServiceImpl.java:148) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedAction(SecurityHelper.java:290) [exo.kernel.commons-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.createRepository(RepositoryServiceImpl.java:147) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> ... 33 common frames omitted
> Caused by: org.picocontainer.PicoIntrospectionException: Failed when calling start on org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache@3acae083
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:136) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.LifecycleVisitor.start(LifecycleVisitor.java:170) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ConcurrentPicoContainer.start(ConcurrentPicoContainer.java:554) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:270) [exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) ~[na:na]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:100) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> ... 41 common frames omitted
> Caused by: org.jboss.cache.CacheException: java.lang.reflect.InvocationTargetException
> at org.jboss.cache.util.reflect.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:148) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.factories.ComponentRegistry$PrioritizedMethod.invoke(ComponentRegistry.java:1012) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.factories.ComponentRegistry.internalStart(ComponentRegistry.java:778) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.factories.ComponentRegistry.start(ComponentRegistry.java:632) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.jboss.cache.invocation.CacheInvocationDelegate.start(CacheInvocationDelegate.java:345) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> at org.exoplatform.services.jcr.jbosscache.PrivilegedJBossCacheHelper$1.run(PrivilegedJBossCacheHelper.java:49) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedAction(SecurityHelper.java:290) [exo.kernel.commons-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.services.jcr.jbosscache.PrivilegedJBossCacheHelper.start(PrivilegedJBossCacheHelper.java:53) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.BufferedJBossCache.start(BufferedJBossCache.java:745) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache.init(JBossCacheWorkspaceStorageCache.java:716) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache.start(JBossCacheWorkspaceStorageCache.java:749) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) ~[na:na]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:100) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> ... 48 common frames omitted
> Caused by: java.lang.reflect.InvocationTargetException: null
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.6.0_30]
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) ~[na:1.6.0_30]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
> at org.jboss.cache.util.reflect.ReflectionUtil.invokeAccessibly(ReflectionUtil.java:144) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> ... 62 common frames omitted
> Caused by: org.jboss.cache.CacheException: Unable to connect to JGroups channel
> at org.jboss.cache.RPCManagerImpl.start(RPCManagerImpl.java:352) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> ... 67 common frames omitted
> Caused by: org.jgroups.ChannelException: failed to start protocol stack
> at org.jgroups.JChannel.startStack(JChannel.java:1617) ~[jgroups-2.6.20.Final.jar:2.6.20.Final]
> at org.jgroups.JChannel.connect(JChannel.java:366) ~[jgroups-2.6.20.Final.jar:2.6.20.Final]
> at org.jboss.cache.RPCManagerImpl.start(RPCManagerImpl.java:347) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA]
> ... 67 common frames omitted
> Caused by: java.lang.IllegalStateException: cluster 'DefaultPartition-jcr_portal' is already connected to singleton transport: [DefaultPartition-jcr_portal, dummy-1368612013185, DefaultPartition-jcrlock_portal]
> at org.jgroups.stack.Configurator.startProtocolStack(Configurator.java:88) ~[jgroups-2.6.20.Final.jar:2.6.20.Final]
> at org.jgroups.stack.ProtocolStack.startStack(ProtocolStack.java:402) ~[jgroups-2.6.20.Final.jar:2.6.20.Final]
> at org.jgroups.JChannel.startStack(JChannel.java:1614) ~[jgroups-2.6.20.Final.jar:2.6.20.Final]
> ... 69 common frames omitted
> 2013-05-15 10:00:13,212 | INFO | Admin identity is read from configuration file [exo-jcr-services.AuditService<Catalina-startStop-1>]
> 2013-05-15 10:00:13,220 | ERROR | Cannot create the portal container 'portal' . ServletContext: org.apache.catalina.core.ApplicationContextFacade@67b464f4 [exo.kernel.container.RootContainer<Catalina-startStop-1>]
> org.picocontainer.PicoIntrospectionException: Failed when calling start on org.exoplatform.web.security.security.RemindPasswordTokenService@7d91dc83
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:136) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.LifecycleVisitor.start(LifecycleVisitor.java:170) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ConcurrentPicoContainer.start(ConcurrentPicoContainer.java:554) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:270) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.PortalContainer.start(PortalContainer.java:679) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.ExoContainer.start(ExoContainer.java:258) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.RootContainer.createPortalContainer(RootContainer.java:678) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.container.RootContainer.createPortalContainers(RootContainer.java:343) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator$1.run(PortalContainersCreator.java:53) ~[plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator$1.run(PortalContainersCreator.java:51) ~[plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.commons.utils.SecurityHelper.doPrivilegedAction(SecurityHelper.java:290) [exo.kernel.commons-2.4.3-GA.jar:2.4.3-GA]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator.createPortalContainers(PortalContainersCreator.java:51) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.exoplatform.platform.server.tomcat.PortalContainersCreator.lifecycleEvent(PortalContainersCreator.java:40) [plf-shared-tomcat-pc-creator-listener-4.0.0.jar:4.0.0]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:119) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1140) [catalina.jar:7.0.39]
> at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:800) [catalina.jar:7.0.39]
> at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1559) [catalina.jar:7.0.39]
> at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1549) [catalina.jar:7.0.39]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) [na:1.6.0_30]
> at java.util.concurrent.FutureTask.run(FutureTask.java:138) [na:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [na:1.6.0_30]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [na:1.6.0_30]
> at java.lang.Thread.run(Thread.java:662) [na:1.6.0_30]
> Caused by: org.chromattic.api.UndeclaredRepositoryException: javax.jcr.RepositoryException: Repository 'repository' not found.
> at org.chromattic.core.api.ChromatticImpl.openSession(ChromatticImpl.java:62) ~[chromattic.core-1.2.2.jar:na]
> at org.exoplatform.commons.chromattic.AbstractContext.getSession(AbstractContext.java:60) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.web.security.security.CookieTokenService$1.execute(CookieTokenService.java:233) ~[exo.portal.component.web.security-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.web.security.security.CookieTokenService$1.execute(CookieTokenService.java:229) ~[exo.portal.component.web.security-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.commons.chromattic.ContextualTask.executeWith(ContextualTask.java:40) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.web.security.security.CookieTokenService.start(CookieTokenService.java:229) ~[exo.portal.component.web.security-3.5.4-PLF.jar:3.5.4-PLF]
> at sun.reflect.GeneratedMethodAccessor90.invoke(Unknown Source) ~[na:na]
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) ~[na:1.6.0_30]
> at java.lang.reflect.Method.invoke(Method.java:597) ~[na:1.6.0_30]
> at org.exoplatform.container.LifecycleVisitor.traverse(LifecycleVisitor.java:100) ~[exo.kernel.container-2.4.3-GA.jar:2.4.3-GA]
> ... 26 common frames omitted
> Caused by: javax.jcr.RepositoryException: Repository 'repository' not found.
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.getRepository(RepositoryServiceImpl.java:231) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.getDefaultRepository(RepositoryServiceImpl.java:220) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.services.jcr.impl.RepositoryServiceImpl.getCurrentRepository(RepositoryServiceImpl.java:213) ~[exo.jcr.component.core-1.15.4-GA-SNAPSHOT.jar:1.15.4-GA-SNAPSHOT]
> at org.exoplatform.commons.chromattic.AbstractContext.openSession(AbstractContext.java:92) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.commons.chromattic.LocalContext.doLogin(LocalContext.java:44) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.commons.chromattic.ChromatticLifeCycle.doLogin(ChromatticLifeCycle.java:301) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.exoplatform.commons.chromattic.PortalSessionLifeCycle.login(PortalSessionLifeCycle.java:48) ~[exo.portal.component.common-3.5.4-PLF.jar:3.5.4-PLF]
> at org.chromattic.core.api.ChromatticImpl.openSession(ChromatticImpl.java:58) ~[chromattic.core-1.2.2.jar:na]
> ... 35 common frames omitted
> {code}
> In *web/portal/src/main/webapp/WEB-INF/conf/jcr/repository-configuration.xml*
> {code}
> <cache enabled="true"
> class="org.exoplatform.services.jcr.impl.dataflow.persistent.jbosscache.JBossCacheWorkspaceStorageCache">
> <properties>
> <property name="jbosscache-configuration" value="${gatein.jcr.cache.config.workspace.portal-system}"/>
> <property name="jgroups-configuration" value="${gatein.jcr.jgroups.config}"/>
> <property name="jgroups-multiplexer-stack" value="false"/>
> <property name="jbosscache-cluster-name" value="jcr${container.name.suffix}"/>
> <property name="jbosscache-shareable" value="true"/>
> </properties>
> </cache>
> {code}
> The JBossCacheWorkspaceStorageCache has a different configuration for the *portal-system*. In order to avoid conflict with other workspaces (especially in cluster env), the *jbosscache-cluster-name* has to have a different value from the used one for the other workspaces.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-2930) Portal keep session alive property values are confusing
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2930?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2930:
----------------------------------
Sprint: Sprint 77
> Portal keep session alive property values are confusing
> -------------------------------------------------------
>
> Key: GTNPORTAL-2930
> URL: https://issues.jboss.org/browse/GTNPORTAL-2930
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Dominik Pospisil
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> According to documentation, portal "keep seesion alive" property values meaning are as follows:
> never - The session will never timeout, even if an application requests it.
> On-demand - The session will timeout if an application requests it
> Always - The session will time out after a set period
> This is quite confusing. E.g. keep session alive never actually means to keep session alive forever.
> Keep session alive always means to let the session timeout automatically.
> If the documentation is correct, the name of the property or property values should be changed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-2751) <priority> in navigation.xml files ignored for merge importMode
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2751?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-2751:
----------------------------------
Sprint: Sprint 77
> <priority> in navigation.xml files ignored for merge importMode
> ----------------------------------------------------------------
>
> Key: GTNPORTAL-2751
> URL: https://issues.jboss.org/browse/GTNPORTAL-2751
> Project: GateIn Portal
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Steps to reproduce:
> Clone the Portal Extension Quickstart and deploy it changing the {{<priority>}} value in {{war/src/main/webapp/WEB-INF/conf/sample-ext/portal/group/platform/administrators/navigation.xml}}.
> NOT OK: The changes have no effect, because priority is ignored in {{org.exoplatform.portal.mop.importer.NavigationImporter.perform()}} with {{importMode}} {{merge}}.
> h3. Solution Proposal A
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Explicitly state in the documentation [1] that {{<priority>}} is considered only if not already set (first wins).
> h3. Solution Proposal B
> * Make {{<priority>}} optional in {{gatein_objects}} XSD and {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}}
> * Change the behavior of {{NavigationMarshaller.unmarshalNavigation(StaxNavigator<Element>)}} to the effect that {{<priority>}} is handled in the same way as navigation nodes: it is used or ignored according to the chosen {{importMode}}. Esp. for {{importMode}} {{merge}} the last read {{<priority>}} should win.
> * Document it in [1]
> For both A and B the most or all occutences of {{<priority>}} should be removed from Portal Extension Quickstart.
> [1] [https://docs.jboss.org/author/display/GTNPORTAL35/Portal+Navigation+Confi...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3159) Warn when a PortalContainerDef contains a non-existent dependency.
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3159?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3159:
----------------------------------
Sprint: Sprint 77
> Warn when a PortalContainerDef contains a non-existent dependency.
> ------------------------------------------------------------------
>
> Key: GTNPORTAL-3159
> URL: https://issues.jboss.org/browse/GTNPORTAL-3159
> Project: GateIn Portal
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> This is important in a situation when a developer works on a Portal Extension or custom portal and he includes a non-existent dependency in the configuration of {{org.exoplatform.container.definition.PortalContainerDefinitionPlugin}} in {{configuration.xml}} file.
> Currently, the portal does not complain at all, the resource loading does not work as expected by the developer but he has little chance to track down the problem quickly and effectively. The portal should definitely warn when {{PortalContainerDefinition}} contains a non-existent dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months
[JBoss JIRA] (GTNPORTAL-3107) NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3107?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3107:
----------------------------------
Sprint: Sprint 77
> NullPointerException during Portlet Deployment when there is no <display-name> in web.xml
> -----------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3107
> URL: https://issues.jboss.org/browse/GTNPORTAL-3107
> Project: GateIn Portal
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Reporter: Peter Palaga
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> I am not sure if this is a bug or feature. Anyway, GateIn does not like WARs which do not have {{<display-name>}} in their {{web.xml}}. I guess the portal should be able to work around the non-availabbility of an explicit <display-name> through working with the default one?
> Steps to reproduce:
> * Take any quickstart from https://github.com/gatein/gatein-portal-quickstart, e.g. simplest-hello-world-portlet
> * remove {{<display-name>}} from {{web.xml}}
> * Compile & deploy
> * Expected: The portal should swallow the portlet app without any error.
> * Current: The portal throws this NPE
> {code}
> [0m[31m09:20:11,195 ERROR [org.exoplatform.web.application.javascript.JavascriptConfigDeployer] (ServerService Thread Pool -- 93) An error occurs while registering 'Javascript in gatein-resources.xml' from the context 'null': java.lang.IllegalArgumentException: The context name cannot be null
> at org.exoplatform.container.definition.PortalContainerConfig.getPortalContainerNames(PortalContainerConfig.java:502) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.container.PortalContainer.addInitTask(PortalContainer.java:474) [exo.kernel.container-2.4.3-GA-redhat-1.jar:2.4.3-GA-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.add(JavascriptConfigDeployer.java:96) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.exoplatform.web.application.javascript.JavascriptConfigDeployer.onEvent(JavascriptConfigDeployer.java:71) [exo.portal.component.web.resources-3.6.0.Beta02-redhat-1.jar:3.6.0.Beta02-redhat-1]
> at org.gatein.wci.ServletContainer.safeFireEvent(ServletContainer.java:319) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.fireEvent(ServletContainer.java:338) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer.access$400(ServletContainer.java:56) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.ServletContainer$RegistrationImpl.registerWebApp(ServletContainer.java:462) [wci-wci-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.start(JB7ServletContainerContext.java:369) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.gatein.wci.jboss.JB7ServletContainerContext.lifecycleEvent(JB7ServletContainerContext.java:223) [wci-jboss7-2.3.1.CR05-redhat-1.jar:2.3.1.CR05-redhat-1]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.apache.catalina.core.StandardContext.start(StandardContext.java:3772) [jbossweb-7.2.0.Final-redhat-1.jar:7.2.0.Final-redhat-1]
> at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.0.Final-redhat-8.jar:7.2.0.Final-redhat-8]
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) [rt.jar:1.7.0_19]
> at java.util.concurrent.FutureTask.run(FutureTask.java:166) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_19]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_19]
> at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_19]
> at org.jboss.threads.JBossThread.run(JBossThread.java:122)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 4 months