July 2014 - gatein-issues - Jboss List Archives

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

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3517?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3517: ---------------------------------------- Description: 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. was: 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 to [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. > 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)

10 years, 5 months

1
0
0 / 0

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

by Tran Trung Thanh (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3517?page=com.atlassian.jira.pl... ] Tran Trung Thanh updated GTNPORTAL-3517: ---------------------------------------- Affects Version/s: 3.5.10.Final > 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 to [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)

10 years, 5 months

1
0
0 / 0

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

by Tran Trung Thanh (JIRA)

Tran Trung Thanh created GTNPORTAL-3517: ------------------------------------------- Summary: 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) 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 to [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)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-376) Different Portlet preference for remote portlets added on the same page

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-376?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-376: ------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1094772|https://bugzilla.redhat.com/show_bug.cgi?id=1094772] from MODIFIED to ON_QA > Different Portlet preference for remote portlets added on the same page > ----------------------------------------------------------------------- > > Key: GTNWSRP-376 > URL: https://issues.jboss.org/browse/GTNWSRP-376 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 2.2.11.Final > Environment: Tested with : > JBoss Portal Platform - 6.1.1 (GateIn Portal 3.6.5) and > GateIn-3.8.0.Beta01 > Reporter: Anurag Debnath > Assignee: Juraci Paixão Kröhling > Attachments: PortletPreferencesPortlet.war.zip > > > When two instances of the same remote portlet is added to the same page, changes made to the preferences of one portlet is picked up by the other portlet as well. > Ideally, portlets should get their own preference/s. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3505) WSRP Producers behind Load Balancers get wrong endpoint URL

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3505?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3505: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1102733|https://bugzilla.redhat.com/show_bug.cgi?id=1102733] from MODIFIED to ON_QA > WSRP Producers behind Load Balancers get wrong endpoint URL > ----------------------------------------------------------- > > Key: GTNPORTAL-3505 > URL: https://issues.jboss.org/browse/GTNPORTAL-3505 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.8.3.Final, 3.9.0.Final > > > When the WSRP producers are behind a cluster, the address generated on the SOAP message is based on the node's address/port, and not the cluster's. BZ 880729 and BZ 1102733. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3506) Allow multiple apps registering the very same AMD paths

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3506?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3506: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1110406|https://bugzilla.redhat.com/show_bug.cgi?id=1110406] from MODIFIED to ON_QA > Allow multiple apps registering the very same AMD paths > ------------------------------------------------------- > > Key: GTNPORTAL-3506 > URL: https://issues.jboss.org/browse/GTNPORTAL-3506 > Project: GateIn Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Peter Palaga > Fix For: 3.8.3.Final, 3.9.0.Final > > > h4. Current state > GTNPORTAL-3502 introduced a common deployer for JavaScript and skin services with the following characteristics: when an app attempts to add an AMD path mapping that is available in the portal already, > all JS and CSS resources from that app are rejected. The path mapping comparison is done on path prefixes only, the target paths are not inspected at all. > Example: > * Application {{app.war}} wants to register the AMD module ID prefix > {{/dojo}} to be mapped to target path {{http://fastcdn.com/dojo/1.7.0}} > * But the prefix {{/dojo}} was registered already for > {{http://othercdn.com/dojo/1.9.1}} by some other application. > * All JS and CSS resources from {{app.war}} are rejected by skin and JSConfig services. > h4. Proposed change > The above approach is unnecessarily restrictive, because it rejects also applications that want to register the very same target path for a given prefix as is registered in the portal already. > Example: > * Application {{app2.war}} wants to register the AMD module ID prefix > {{/dojo}} to be mapped to target path {{http://fastcdn.com/dojo/1.7.0}} > * The prefix {{/dojo}} was previously registered by some other application {{app1.war}} to point to the very same target path {{http://fastcdn.com/dojo/1.7.0}}. > * JS and CSS resources from {{app2.war}} should be accepted by the portal because no inconsistency is introduced by {{app2.war}}. > * However, having accepted two or more apps relying on one path mapping, the portal must reject all changes that could break any of the affected applications. E.g. the portal may not remove the mapping on {{app1.war}} undeploy or it may not allow for re-deploying {{app1.war}} with a modified path mapping while {{app2.war}} is still active. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3500) testMemoryLeakWithMultiThread fails sometimes

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3500?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3500: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1103304|https://bugzilla.redhat.com/show_bug.cgi?id=1103304] from MODIFIED to ON_QA > testMemoryLeakWithMultiThread fails sometimes > --------------------------------------------- > > Key: GTNPORTAL-3500 > URL: https://issues.jboss.org/browse/GTNPORTAL-3500 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > Assignee: Trong Tran > Fix For: 3.9.0.Final > > Attachments: TestDownloadService.java > > Original Estimate: 1 day, 4 hours > Time Spent: 1 day > Remaining Estimate: 0 minutes > > Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1103304 > org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread() fails in some cases. The stack trace: > junit.framework.AssertionFailedError > at junit.framework.Assert.fail(Assert.java:48) > at junit.framework.Assert.assertTrue(Assert.java:20) > at junit.framework.Assert.assertTrue(Assert.java:27) > at org.exoplatform.download.TestDownloadService.testMemoryLeakWithMultiThread(TestDownloadService.java:109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > ... > The line where it fails is > assertTrue(cache.getCacheSize() <= 10); > Version-Release number of selected component (if applicable): > GateIn 3.8.x or 3.9.x > Reproducible sometimes: 1/10 or even less. Happens both on Jenkins and desktop. > Steps to Reproduce: > Not sure. It happens randomly. Perhaps overloading the machine with some CPU-intensive task might help. Just build the exo.portal.component.web.server artifact with tests repeatedly until it fails. > Actual results: > Test fails > Expected results: > Not sure if the subject under the test is broken or the test itself. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3494) Names of imported applications in Application Registry are not localized

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3494?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3494: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1107566|https://bugzilla.redhat.com/show_bug.cgi?id=1107566] from MODIFIED to ON_QA > Names of imported applications in Application Registry are not localized > ------------------------------------------------------------------------- > > Key: GTNPORTAL-3494 > URL: https://issues.jboss.org/browse/GTNPORTAL-3494 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: WebUI > Affects Versions: 3.8.1.Final > Reporter: Lucas Ponce > Assignee: Lucas Ponce > Fix For: 3.8.3.Final, 3.9.0.Final > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3509) [Application Registry] Missing validator when importing applications

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3509?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3509: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 1107566|https://bugzilla.redhat.com/show_bug.cgi?id=1107566] from MODIFIED to ON_QA > [Application Registry] Missing validator when importing applications > -------------------------------------------------------------------- > > Key: GTNPORTAL-3509 > URL: https://issues.jboss.org/browse/GTNPORTAL-3509 > Project: GateIn Portal > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Affects Versions: 3.5.10.Final, 3.7.1.Final, 3.8.2.Final > Reporter: H. Trang Vu > Assignee: Lucas Ponce > Priority: Minor > Fix For: 3.8.3.Final, 3.9.0.Final > > Attachments: SiteRedirectsAndImportExportAdminPortlet-TooLongAppName-DisplayName.png > > > When applications are added by configuration or by importing automatically all applications, there isn't any check of application name while its value is read-only after the creation. These validators (length and pattern) however existent when adding or editing an application. As a consequence, some imported applications cannot be changed (Display Name, Description, Access Permission). > Steps to reproduce: > # Login as root > # Go to Application Registry > # Click *Site Redirects and Import/Export* (the last item of *Administration* category). > # Change nothing. Click Save. Warning message appears as follows. > {noformat} > The length of the text in field "Application Name" must be between "3" and "30" characters. > The length of the text in field "Display Name" must be between "3" and "30" characters. > {noformat} > * It is feasible to reduce "Display Name" but not "Application Name" at run time. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-3363) Provide feedback on logs when gadget is not white-listed

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-3363?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-3363: ---------------------------------------------------- Honza Fnukal <hfnukal(a)redhat.com> changed the Status of [bug 794468|https://bugzilla.redhat.com/show_bug.cgi?id=794468] from MODIFIED to ON_QA > Provide feedback on logs when gadget is not white-listed > -------------------------------------------------------- > > Key: GTNPORTAL-3363 > URL: https://issues.jboss.org/browse/GTNPORTAL-3363 > Project: GateIn Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Juraci Paixão Kröhling > Assignee: Juraci Paixão Kröhling > Fix For: 3.7.0.Final > > > When a gadget is not white-listed, the ProxyFilterService rejects the loading of the contents, but provides no hints on the logs about it, making the user to believe that the gadget might be at fault. A solution is to log at INFO level that access to it has been blocked. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 5 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