[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11
by Michael McKinsey (JIRA)
[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ]
Michael McKinsey updated GTNSSO-28:
-----------------------------------
Description:
The realm name is coming up wrong with an extra g which I believe is causing the error #403x
https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
notice realm is ggatein
I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1...
It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;
I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.
was:
The realm name is coming up wrong with an extra g which I believe is causing the error #403x
https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
notice realm is ggatein
I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1...
It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;
I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.
> realm is wrong adds an extra g in the realm name with OpenAM 11
> ---------------------------------------------------------------
>
> Key: GTNSSO-28
> URL: https://issues.jboss.org/browse/GTNSSO-28
> Project: GateIn SSO
> Issue Type: Bug
> Affects Versions: 1.4.0.Beta01
> Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
> Reporter: Michael McKinsey
> Assignee: Marek Posolda
> Priority: Blocker
>
> The realm name is coming up wrong with an extra g which I believe is causing the error #403x
> https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2F...%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
> notice realm is ggatein
> I found a reference to the extra g:
> https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1...
> It says:
> // We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
> String providerId = agentUrl + "/?Realm=g" + openSSORealm;
> I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11
by Michael McKinsey (JIRA)
Michael McKinsey created GTNSSO-28:
--------------------------------------
Summary: realm is wrong adds an extra g in the realm name with OpenAM 11
Key: GTNSSO-28
URL: https://issues.jboss.org/browse/GTNSSO-28
Project: GateIn SSO
Issue Type: Bug
Affects Versions: 1.4.0.Beta01
Environment: Using OpenAM 11 - using the plugin with Exo Platform but imagine this is probably the same for anything using gatein-sso for CDSSO with OpenAM 11
Reporter: Michael McKinsey
Assignee: Marek Posolda
Priority: Blocker
The realm name is coming up wrong with an extra g which I believe is causing the error #403x
https://.../openam/cdcservlet?realm=gatein&goto=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin&ProviderID=https%3A%2F%2Fexo.fr33.co%3A8443%2Fportal%2Finitiatessologin%2F%3FRealm%3Dggatein&RequestID=71288&IssueInstant=2014-05-08T01%3A10%3A30Z&MajorVersion=1&MinorVersion=0
notice realm is ggatein
I found a reference to the extra g:
https://github.com/gatein/gatein-sso/blob/b3b0e3fb9fd5d9498a97e89357603d1...
It says:
// We need to use Realm=g because of bug (or strange behaviour) of OpenAM, which cuts first character of realmName during parsing
String providerId = agentUrl + "/?Realm=g" + openSSORealm;
I am guessing this was needed with OpenAM 10 but is causing and error with OpenAM 11. I was trying to fix this myself but I can't get gatein-sso to build in my environment just yet.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3472) NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3472?page=com.atlassian.jira.pl... ]
Trong Tran resolved GTNPORTAL-3472.
-----------------------------------
Resolution: Done
> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3472
> URL: https://issues.jboss.org/browse/GTNPORTAL-3472
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Trong Tran
> Fix For: 3.5.10.Final, 3.7.2.Final, 3.9.0.Final
>
> Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3472) NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3472?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3472:
----------------------------------
Fix Version/s: 3.5.10.Final
3.7.2.Final
> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3472
> URL: https://issues.jboss.org/browse/GTNPORTAL-3472
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Trong Tran
> Fix For: 3.5.10.Final, 3.7.2.Final, 3.9.0.Final
>
> Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3474) Items in status list are displayed in english
by Vu Viet Phuong (JIRA)
Vu Viet Phuong created GTNPORTAL-3474:
-----------------------------------------
Summary: Items in status list are displayed in english
Key: GTNPORTAL-3474
URL: https://issues.jboss.org/browse/GTNPORTAL-3474
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.8.0.Beta01, 3.7.1.Final
Reporter: Vu Viet Phuong
Assignee: Vu Viet Phuong
Priority: Minor
1- Login as root and set language to French
2- Go to Administration/Users/Group and Roles
3- Choose the tab "User Management"
--> the Enable/Disable/All selectbox is not localized
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3472) NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3472?page=com.atlassian.jira.pl... ]
Trong Tran updated GTNPORTAL-3472:
----------------------------------
Description:
We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
{code}
[jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
java.lang.NullPointerException
at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
{code}
*MBeans which seem to cause this problem :*
- exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=*,service=SessionRegistry
- exo:portal=portal,repository=\*,workspace=\*,service=Cache
- exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
- exo:portal=portal,service=cache,name=*
*How to reproduce :*
- unzip GateIn 3.7.0.Final tomcat distribution
- copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
- start your portal and watch the starup logs
was:
We can't monitor eXo Platform health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
{code}
[jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
java.lang.NullPointerException
at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
{code}
*MBeans which seem to cause this problem :*
- exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
- exo:portal=portal,repository=*,service=SessionRegistry
- exo:portal=portal,repository=\*,workspace=\*,service=Cache
- exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
- exo:portal=portal,service=cache,name=*
*How to reproduce :*
- unzip eXo Platform 4.0.x (or 4.1-M1) tomcat distribution (Community or Express or Enterprise)
- copy the jmxtrans-addon.war war in <PLATFORM_DIR>/webapps/ directory
- start your portal and watch the starup logs
> NPE in PicketLinkIDMServiceImpl.getIdentitySession during startup when eXo MBeans are invoked
> ---------------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-3472
> URL: https://issues.jboss.org/browse/GTNPORTAL-3472
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.7.0.Final
> Reporter: Trong Tran
> Fix For: 3.9.0.Final
>
> Attachments: jmxtrans-addon.war
>
>
> We can't monitor GateIn health in a clean way because if we invoke eXo MBeans during GateIn portal startup, we have dozens of the following NPE which pollute the logs:
> {code}
> [jmxtrans-collect-5] ERROR org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl - null
> java.lang.NullPointerException
> at org.exoplatform.services.organization.idm.PicketLinkIDMServiceImpl.getIdentitySession(PicketLinkIDMServiceImpl.java:211)
> at org.exoplatform.services.organization.idm.PicketLinkIDMOrganizationServiceImpl.endRequest(PicketLinkIDMOrganizationServiceImpl.java:189)
> at org.exoplatform.container.component.RequestLifeCycle.doEnd(RequestLifeCycle.java:71)
> at org.exoplatform.container.component.RequestLifeCycleStack.end(RequestLifeCycleStack.java:101)
> at org.exoplatform.container.component.RequestLifeCycle.end(RequestLifeCycle.java:163)
> at org.exoplatform.container.management.ManagementContextImpl.afterInvoke(ManagementContextImpl.java:381)
> at org.exoplatform.management.jmx.impl.ExoModelMBean.invoke(ExoModelMBean.java:75)
> at javax.management.modelmbean.RequiredModelMBean.getAttribute(RequiredModelMBean.java:1441)
> at javax.management.modelmbean.RequiredModelMBean.getAttributes(RequiredModelMBean.java:1657)
> at com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttributes(DefaultMBeanServerInterceptor.java:725)
> at com.sun.jmx.mbeanserver.JmxMBeanServer.getAttributes(JmxMBeanServer.java:675)
> at org.jmxtrans.embedded.Query.collectMetrics(Query.java:165)
> at org.jmxtrans.embedded.EmbeddedJmxTrans$1.run(EmbeddedJmxTrans.java:145)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
> at java.lang.Thread.run(Thread.java:695)
> {code}
> *MBeans which seem to cause this problem :*
> - exo:portal=portal,repository=\*,workspace=system,cache-type=JCR_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=\*,workspace=system,cache-type=LOCK_CACHE,jmx-resource=CacheMgmtInterceptor
> - exo:portal=portal,repository=*,service=SessionRegistry
> - exo:portal=portal,repository=\*,workspace=\*,service=Cache
> - exo:portal=portal,repository=\*,workspace=\*,service=lockmanager
> - exo:portal=portal,service=cache,name=*
> *How to reproduce :*
> - unzip GateIn 3.7.0.Final tomcat distribution
> - copy the jmxtrans-addon.war war in <tomcat_dir>/webapps/ directory
> - start your portal and watch the starup logs
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-3267) MOP import resource
by Boubaker Khanfir (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-3267?page=com.atlassian.jira.pl... ]
Boubaker Khanfir commented on GTNPORTAL-3267:
---------------------------------------------
If you are searching for the best solution to do this, take a look at:
https://github.com/exo-addons/staging-extension/blob/master/component/sit...
In this file I used the MOP API Marshaller and unmarshaller. In the current situation, you develop your own marshaller and unmarshaller instead of using the default ones. I recommend to use the default provided ones instead of coding and maintaining new one. (Two impls in the same jar for the same behavior).
> MOP import resource
> -------------------
>
> Key: GTNPORTAL-3267
> URL: https://issues.jboss.org/browse/GTNPORTAL-3267
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Java API
> Affects Versions: 3.5.6.Final
> Reporter: Boubaker Khanfir
> Assignee: Trong Tran
> Fix For: 3.9.0.Final
>
> Attachments: portal_mobile_2013-10-01_11-22-50.zip
>
> Original Estimate: 4 hours
> Time Spent: 1 day, 6 hours
> Remaining Estimate: 0 minutes
>
> MOP resource management is based on a custom marshaller/unmarshaller (org.exoplatform.portal.mop.management.binding.xml.*).
> I had used the mop managed resource in a custom case:
> * Create a new site.
> * Add PortalBody in a container.
> * Export site using GateIN management.
> * Re-import exported site.
> => Exception:
> {code}
> Operation exception for operation import-resource and address /mop [org.gatein.management.cli<pool-4-thread-1>]
> org.gatein.management.api.exceptions.OperationException: Exception reading data for import.
> at org.exoplatform.portal.mop.management.operations.MopImportResource.execute(MopImportResource.java:198) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.gatein.management.core.api.controller.SimpleManagementController.execute(SimpleManagementController.java:100) ~[gatein-management-core-1.1.0.Final.jar:1.1.0.Final]
> ...
> Caused by: org.staxnav.StaxNavException: Unexpected element 'page-body' at [row,col]:[167,21]
> at org.gatein.common.xml.stax.navigator.Exceptions.unexpectedElement(Exceptions.java:45) ~[exo.portal.component.common-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.AbstractMarshaller.unmarshalContainer(AbstractMarshaller.java:171) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshalPortalConfig(SiteLayoutMarshaller.java:216) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> at org.exoplatform.portal.mop.management.binding.xml.SiteLayoutMarshaller.unmarshal(SiteLayoutMarshaller.java:80) ~[exo.portal.component.portal-3.5.x-PLF-SNAPSHOT.jar:3.5.x-PLF-SNAPSHOT]
> ... 40 common frames omitted
> {code}
> To fix this I used the *default* MOP marshaller:
> {code}
> import org.exoplatform.portal.config.model.ModelUnmarshaller;
> // ...
> public PortalConfig unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(PortalConfig.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> //...
> public Page.PageSet unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(Page.PageSet.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> //...
> public PageNavigation unmarshal(InputStream inputStream) throws BindingException {
> try {
> return ModelUnmarshaller.unmarshall(PageNavigation.class, inputStream).getObject();
> } catch (Exception e) {
> throw new BindingException(e);
> }
> }
> // ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months
[JBoss JIRA] (GTNPORTAL-511) userPref of gadgets are not sometime not saved correctly
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-511?page=com.atlassian.jira.plu... ]
Trong Tran updated GTNPORTAL-511:
---------------------------------
Fix Version/s: 3.9.0.Final
(was: 3.7.1.Final)
> userPref of gadgets are not sometime not saved correctly
> --------------------------------------------------------
>
> Key: GTNPORTAL-511
> URL: https://issues.jboss.org/browse/GTNPORTAL-511
> Project: GateIn Portal
> Issue Type: Bug
> Components: User Interface
> Affects Versions: 3.0.0-Beta04
> Environment: svn r1330
> Reporter: jerem j
> Assignee: Tuyen Nguyen The
> Fix For: 3.9.0.Final
>
> Attachments: GTNPORTAL-511.js.patch, GTNPORTAL-511.patch, stacktrace.txt
>
> Original Estimate: 2 days
> Time Spent: 2 days, 2 hours
> Remaining Estimate: 0 minutes
>
> Every call to gadgets.Prefs.set generate a call to save the data in the backend (an action in the dashboard portlet). To save we send all the set of preferences.
> The jira gadget call this API multiple times in a very short time. So there is multiple ajax request sent to the backend but not in a precise order. So it might happen that the first request arrive the last one, and so old preferences are saved.
> To fix:
> In the file Gadgets.js, function "gadgets.IfrGadgetService.prototype.setUserPref", prefs is updated with all the name/value, and ALL the prefs object is saved. Instead of saving all the preferences, we should only save the updated preferences.
> In org.exoplatform.portal.pom.spi.gadget.Gadget it will be needed to be able to add preference by name, something like :
> public void setUserPref(String name, String value)
> code :
> Gadgets.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResour...
> ExoBasedUserPrefStore.js: http://fisheye.exoplatform.org/browse/projects/portal/trunk/web/eXoResour...
> links:
> API doc about adgets.Prefs.set: http://code.google.com/apis/gadgets/docs/reference/#gadgets.Prefs.set
> Jira gadget to test: http://jira4j.exoplatform.org/rest/gadgets/1.0/g/com.atlassian.jira.gadge...
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 11 months