July 2014 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-378) WSRP Producer is missing distributable tag

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-378?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration updated GTNWSRP-378: -------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1115512 > WSRP Producer is missing distributable tag > ------------------------------------------ > > Key: GTNWSRP-378 > URL: https://issues.jboss.org/browse/GTNWSRP-378 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Producer > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > See BZ#1115512 . The WSRP Producer WAR seems to be missing the <distributable/> tag on web.xml , causing session replication to not work for communication between consumer and producer. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-378) WSRP Producer is missing distributable tag

by Juraci Paixão Kröhling (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-378?page=com.atlassian.jira.plugi... ] Juraci Paixão Kröhling updated GTNWSRP-378: ------------------------------------------- Status: Pull Request Sent (was: Open) Git Pull Request: https://github.com/gatein/gatein-wsrp/pull/94 > WSRP Producer is missing distributable tag > ------------------------------------------ > > Key: GTNWSRP-378 > URL: https://issues.jboss.org/browse/GTNWSRP-378 > Project: GateIn WSRP > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Producer > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > > See BZ#1115512 . The WSRP Producer WAR seems to be missing the <distributable/> tag on web.xml , causing session replication to not work for communication between consumer and producer. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-378) WSRP Producer is missing distributable tag

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNWSRP-378: ---------------------------------------------- Summary: WSRP Producer is missing distributable tag Key: GTNWSRP-378 URL: https://issues.jboss.org/browse/GTNWSRP-378 Project: GateIn WSRP Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Producer Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling See BZ#1115512 . The WSRP Producer WAR seems to be missing the <distributable/> tag on web.xml , causing session replication to not work for communication between consumer and producer. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3519) "Import applications" fails when remote portlet name clashes with local portlet

by Juraci Paixão Kröhling (JIRA)

Juraci Paixão Kröhling created GTNPORTAL-3519: ------------------------------------------------- Summary: "Import applications" fails when remote portlet name clashes with local portlet Key: GTNPORTAL-3519 URL: https://issues.jboss.org/browse/GTNPORTAL-3519 Project: GateIn Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Juraci Paixão Kröhling Assignee: Juraci Paixão Kröhling The "import applications" on the application registry fails when there's a remote portlet with the same name as a local portlet, due to "unknown error" on the user interface, and "Cannot create a content with a content id ... with an existing different content id" in the logs. More details on BZ#1117813 . -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3518) Use a variable to enable the sequence

by Nicolas Filotto (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3518?page=com.atlassian.jira.pl... ] Nicolas Filotto updated GTNPORTAL-3518: --------------------------------------- Git Pull Request: https://github.com/gatein/gatein-portal/pull/886 > Use a variable to enable the sequence > ------------------------------------- > > Key: GTNPORTAL-3518 > URL: https://issues.jboss.org/browse/GTNPORTAL-3518 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: JCR integration > Affects Versions: 3.8.2.Final > Reporter: Nicolas Filotto > Fix For: 3.8.5.Final, 3.9.0.Final > > > Starting from eXo JCR 1.16.0 Alpha4, we have an improvement (aka https://jira.exoplatform.org/browse/JCR-2262) that allows to provide a better scalability in term of total amount of sub nodes that a node can have without affecting the performances, indeed with big tables the performances get worse especially when we have a node with a lot of sub nodes so to push the scalability limit, eXo JCR can now rely on sequences. > The sequences can be enabled thanks to a new parameter in the data container configuration of the workspace called {{use-sequence-for-order-number}}, by default it is set to {{auto}} so it will be enabled on all the databases on which we know that the sequences help to improve the performances and the scalability such as on Oracle and PostgreSQL, but also on H2 and HSQLDB. > Unfortunately, this improvement causes a regression which is (https://jira.exoplatform.org/browse/JCR-2322), so as workaround we can configure this parameter using a variable with {{false}} as default value, this way once the bug will be fixed, we will be able to set it back to the default value which is {{auto}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3517) Cannot start Gatein Portal with MySQL in UTF-8

by Nicolas Filotto (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3517?page=com.atlassian.jira.pl... ] Nicolas Filotto commented on GTNPORTAL-3517: -------------------------------------------- The PR needs to be updated according to my remarks that can be found here https://jira.exoplatform.org/browse/EXOGTN-1833?focusedCommentId=316638&p... > Cannot start Gatein Portal with MySQL in UTF-8 > ---------------------------------------------- > > Key: GTNPORTAL-3517 > URL: https://issues.jboss.org/browse/GTNPORTAL-3517 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 3.5.10.Final > Reporter: Tran Trung Thanh > > If we want to use Gatein Portal in UTF-8 mode with MySQL, even if we configure the dialect to mysql-utf8, we get issues of type: > {code} > Caused by: org.jboss.cache.CacheException: Unable to start cache loaders > at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:470) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA] > ... 81 common frames omitted > Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 1000 bytes > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[na:1.6.0_45] > at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39) ~[na:1.6.0_45] > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27) ~[na:1.6.0_45] > at java.lang.reflect.Constructor.newInstance(Constructor.java:513) ~[na:1.6.0_45] > at com.mysql.jdbc.Util.handleNewInstance(Util.java:411) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.Util.getInstance(Util.java:386) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1052) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4098) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4030) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2671) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1749) ~[mysql-connector-java-5.1.19.jar:na] > at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1666) ~[mysql-connector-java-5.1.19.jar:na] > at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42] > at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42] > at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.executeUpdate(DelegatingStatement.java:228) ~[tomcat-dbcp.jar:7.0.42] > at org.jboss.cache.loader.AdjListJDBCCacheLoader.start(AdjListJDBCCacheLoader.java:300) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA] > at org.jboss.cache.loader.JDBCCacheLoader.start(JDBCCacheLoader.java:396) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA] > at org.exoplatform.services.jcr.impl.core.lock.jbosscache.ControllerCacheLoader.start(ControllerCacheLoader.java:312) ~[exo.jcr.component.core-1.15.8-GA-SNAPSHOT.jar:1.15.8-GA-SNAPSHOT] > at org.jboss.cache.loader.CacheLoaderManager.startCacheLoader(CacheLoaderManager.java:464) ~[jbosscache-core-3.2.7.GA.jar:3.2.7.GA] > {code} > NB: The db schema has been created using the next command: > {code} > CREATE DATABASE plf_jcr_utf8 DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_bin; > {code} > To make Gatein Portal work with MySQL in UTF-8, we need [JCR-2312|https://jira.exoplatform.org/browse/JCR-2312] and add new parameter introduced from JCR issue in the configuration of the lock manager which is infinispan-cl-cache.jdbc.dialect in case of infinispan and jbosscache-cl-cache.jdbc.dialect in case of JBC. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3518) Use a variable to enable the sequence

by Nicolas Filotto (JIRA)

Nicolas Filotto created GTNPORTAL-3518: ------------------------------------------ Summary: Use a variable to enable the sequence Key: GTNPORTAL-3518 URL: https://issues.jboss.org/browse/GTNPORTAL-3518 Project: GateIn Portal Issue Type: Enhancement Security Level: Public (Everyone can see) Components: JCR integration Affects Versions: 3.8.2.Final Reporter: Nicolas Filotto Fix For: 3.8.5.Final, 3.9.0.Final Starting from eXo JCR 1.16.0 Alpha4, we have an improvement (aka https://jira.exoplatform.org/browse/JCR-2262) that allows to provide a better scalability in term of total amount of sub nodes that a node can have without affecting the performances, indeed with big tables the performances get worse especially when we have a node with a lot of sub nodes so to push the scalability limit, eXo JCR can now rely on sequences. The sequences can be enabled thanks to a new parameter in the data container configuration of the workspace called {{use-sequence-for-order-number}}, by default it is set to {{auto}} so it will be enabled on all the databases on which we know that the sequences help to improve the performances and the scalability such as on Oracle and PostgreSQL, but also on H2 and HSQLDB. Unfortunately, this improvement causes a regression which is (https://jira.exoplatform.org/browse/JCR-2322), so as workaround we can configure this parameter using a variable with {{false}} as default value, this way once the bug will be fixed, we will be able to set it back to the default value which is {{auto}}. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by Ali Hamdi (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] Ali Hamdi commented on GTNSSO-28: --------------------------------- Here is a Pull request that fixes the issue : https://github.com/gatein/gatein-sso/pull/5 > 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 > Security Level: Public(Everyone can see) > 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 > Fix For: 1.4.3.Final > > > 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 an 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.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by Ali Hamdi (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] Ali Hamdi edited comment on GTNSSO-28 at 7/10/14 7:00 AM: ---------------------------------------------------------- This issue is caused by this bug on OpenAM side : https://bugster.forgerock.org/jira/browse/OPENAM-1539 This was fixed for OpenAM 10.1 and OpenAM 11 was (Author: ali_hamdi): This issue is caused by this bug on OpenAm side : https://bugster.forgerock.org/jira/browse/OPENAM-1539 > 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 > Security Level: Public(Everyone can see) > 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 > Fix For: 1.4.3.Final > > > 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 an 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.6#6264)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (GTNSSO-28) realm is wrong adds an extra g in the realm name with OpenAM 11

by Ali Hamdi (JIRA)

[ https://issues.jboss.org/browse/GTNSSO-28?page=com.atlassian.jira.plugin.... ] Ali Hamdi commented on GTNSSO-28: --------------------------------- This issue is caused by this bug on OpenAm side : https://bugster.forgerock.org/jira/browse/OPENAM-1539 > 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 > Security Level: Public(Everyone can see) > 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 > Fix For: 1.4.3.Final > > > 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 an 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.6#6264)

9 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues July 2014