[JBoss JIRA] (GTNPORTAL-3368) CDI Portlet Deployment is not working anymore in latest master
by Trong Tran (JIRA)
Trong Tran created GTNPORTAL-3368:
-------------------------------------
Summary: CDI Portlet Deployment is not working anymore in latest master
Key: GTNPORTAL-3368
URL: https://issues.jboss.org/browse/GTNPORTAL-3368
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Trong Tran
Assignee: Peter Palaga
Fix For: 3.7.0.Final
Today I have tried to deploy cdi-generic-portlet and cdi-scopes-portlet examples from gatein-portal-quickstarts on latest GateIn master. Then I have got following error in console log during startup:
{code}
13:55:16,715 INFO [org.jboss.weld.deployer] (MSC service thread 1-7) JBAS016005: Starting Services for CDI deployment: cdi-generic-portlet.war
13:55:16,755 INFO [org.jboss.weld.Version] (MSC service thread 1-7) WELD-000900 1.1.5 (AS71)
13:55:16,775 INFO [org.jboss.weld.deployer] (MSC service thread 1-1) JBAS016008: Starting weld service for deployment cdi-generic-portlet.war
13:55:17,103 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1767) [jboss-msc-1.0.2.GA.jar:1.0.2.GA]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_21]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_21]
at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_21]
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
13:55:17,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "cdi-generic-portlet.war" was rolled back with failure message {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}
13:55:17,327 INFO [org.jboss.weld.deployer] (MSC service thread 1-5) JBAS016009: Stopping weld service for deployment cdi-generic-portlet.war
13:55:17,340 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015877: Stopped deployment cdi-generic-portlet.war in 22ms
13:55:17,341 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: org.jboss.msc.service.StartException in service jboss.deployment.unit."cdi-generic-portlet.war".component."org.gatein.cdi.contexts.listeners.CDIServletListener".WeldInstantiator: Failed to start service
13:55:17,344 ERROR [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) {"JBAS014653: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"cdi-generic-portlet.war\".component.\"org.gatein.cdi.contexts.listeners.CDIServletListener\".WeldInstantiator: Failed to start service"}}}}
{code}
I confirm that it is still working well in latest gatein 3.7.0.Alpha01.
--
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
12 years, 2 months
[JBoss JIRA] (GTNPORTAL-3366) [IE8, IE9] Can not rename Dashboard tab if name contains accent chars
by Tran Trung Thanh (JIRA)
Tran Trung Thanh created GTNPORTAL-3366:
-------------------------------------------
Summary: [IE8, IE9] Can not rename Dashboard tab if name contains accent chars
Key: GTNPORTAL-3366
URL: https://issues.jboss.org/browse/GTNPORTAL-3366
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.5.8.Final
Reporter: Tran Trung Thanh
Steps to reproduce:
- Login
- Create a Dashboard page
- Go to that page, create a new tab of which name contains accent chars (i.e. sổ mũi khéo dài)
- Edit name of that tab by deleting some chars in the name (i.e.: sổ mũi)
- Hit Enter
>>> Result: can not rename
--
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
12 years, 2 months
[JBoss JIRA] (GTNPORTAL-2801) Add eviction to indexer-config.xml
by Marek Posolda (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2801?page=com.atlassian.jira.pl... ]
Marek Posolda commented on GTNPORTAL-2801:
------------------------------------------
Update: It seems that my previous comment could be ignored. The whole issue is eXo JCR bug, which causes that JBC items with index changes are not properly purged on slave nodes after applying (just on master node). There is eXo JCR jira here: https://jira.exoplatform.org/browse/JCR-2269 . After fixing this and update JCR, we won't need any eviction configuration in JBC config or some hack setups to be documented in performance guide.
> Add eviction to indexer-config.xml
> ----------------------------------
>
> Key: GTNPORTAL-2801
> URL: https://issues.jboss.org/browse/GTNPORTAL-2801
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: JCR integration
> Affects Versions: 3.5.0.Final
> Reporter: Toshiya Kobayashi
>
> gatein.ear/portal.war/WEB-INF/conf/jcr/jbosscache/cluster/indexer-config.xml doesn't have eviction configuration. It may cause a memory leak in slave nodes.
> {code:xml}
> <jbosscache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:jboss:jbosscache-core:config:3.1">
> <locking useLockStriping="false" concurrencyLevel="64" lockParentForChildInsertRemove="false"
> lockAcquisitionTimeout="20000"/>
> <!-- Configure the TransactionManager -->
> <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup"/>
> <clustering mode="replication" clusterName="${jboss.partition.name:DefaultPartition}-${jbosscache-cluster-name}">
> <stateRetrieval timeout="20000" fetchInMemoryState="false"/>
> <jgroupsConfig configFile="jgroups/gatein-${gatein.default.jgroups.stack:udp}.xml"/>
> <sync/>
> </clustering>
> </jbosscache>
> {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
12 years, 2 months