[JBoss JIRA] (GTNPORTAL-2935) SqlSyntaxErrorException when starting JCR service configured with DB2 10
by Vlastislav Ramik (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2935?page=com.atlassian.jira.pl... ]
Vlastislav Ramik resolved GTNPORTAL-2935.
-----------------------------------------
Resolution: Done
After setting the parameter as described above. The issue is not present any more:
There is link to ui tests: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/EPP/view/6...
> SqlSyntaxErrorException when starting JCR service configured with DB2 10
> ------------------------------------------------------------------------
>
> Key: GTNPORTAL-2935
> URL: https://issues.jboss.org/browse/GTNPORTAL-2935
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01, 3.6.0.Beta02
> Environment: DB2 10
> Reporter: Tomas Kyjovsky
> Assignee: Vlastislav Ramik
> Labels: JPP61-Test-dev
> Attachments: SqlSyntaxErrorException.txt
>
>
> There are exceptions when starting repository service when portal is configured with DB2 10. JCR tables in DB are created.
> Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=LIMIT;;FETCH FIRST <n> ROWS ONLY, DRIVER=4.13.127
> at com.ibm.db2.jcc.am.id.a(id.java:677)
> at com.ibm.db2.jcc.am.id.a(id.java:60)
> at com.ibm.db2.jcc.am.id.a(id.java:127)
> at com.ibm.db2.jcc.am.no.c(no.java:2653)
> at com.ibm.db2.jcc.am.no.d(no.java:2641)
> at com.ibm.db2.jcc.am.no.a(no.java:2090)
> at com.ibm.db2.jcc.am.oo.a(oo.java:7671)
> at com.ibm.db2.jcc.t4.cb.h(cb.java:141)
> at com.ibm.db2.jcc.t4.cb.b(cb.java:41)
> at com.ibm.db2.jcc.t4.q.a(q.java:32)
> at com.ibm.db2.jcc.t4.sb.i(sb.java:135)
> at com.ibm.db2.jcc.am.no.ib(no.java:2059)
> at com.ibm.db2.jcc.am.oo.sc(oo.java:3559)
> at com.ibm.db2.jcc.am.oo.b(oo.java:4348)
> at com.ibm.db2.jcc.am.oo.fc(oo.java:743)
> at com.ibm.db2.jcc.am.oo.executeQuery(oo.java:713)
> at org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:107)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.db.DB2MYSMultiDbJDBCConnection.findNodesAndProperties(DB2MYSMultiDbJDBCConnection.java:85) [exo.jcr.component.core-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getNodesAndProperties(JDBCStorageConnection.java:1210) [exo.jcr.component.core-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
> ... 7 more
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2935) SqlSyntaxErrorException when starting JCR service configured with DB2 10
by Vlastislav Ramik (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2935?page=com.atlassian.jira.pl... ]
Vlastislav Ramik reassigned GTNPORTAL-2935:
-------------------------------------------
Assignee: Vlastislav Ramik
> SqlSyntaxErrorException when starting JCR service configured with DB2 10
> ------------------------------------------------------------------------
>
> Key: GTNPORTAL-2935
> URL: https://issues.jboss.org/browse/GTNPORTAL-2935
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01, 3.6.0.Beta02
> Environment: DB2 10
> Reporter: Tomas Kyjovsky
> Assignee: Vlastislav Ramik
> Labels: JPP61-Test-dev
> Attachments: SqlSyntaxErrorException.txt
>
>
> There are exceptions when starting repository service when portal is configured with DB2 10. JCR tables in DB are created.
> Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-104, SQLSTATE=42601, SQLERRMC=LIMIT;;FETCH FIRST <n> ROWS ONLY, DRIVER=4.13.127
> at com.ibm.db2.jcc.am.id.a(id.java:677)
> at com.ibm.db2.jcc.am.id.a(id.java:60)
> at com.ibm.db2.jcc.am.id.a(id.java:127)
> at com.ibm.db2.jcc.am.no.c(no.java:2653)
> at com.ibm.db2.jcc.am.no.d(no.java:2641)
> at com.ibm.db2.jcc.am.no.a(no.java:2090)
> at com.ibm.db2.jcc.am.oo.a(oo.java:7671)
> at com.ibm.db2.jcc.t4.cb.h(cb.java:141)
> at com.ibm.db2.jcc.t4.cb.b(cb.java:41)
> at com.ibm.db2.jcc.t4.q.a(q.java:32)
> at com.ibm.db2.jcc.t4.sb.i(sb.java:135)
> at com.ibm.db2.jcc.am.no.ib(no.java:2059)
> at com.ibm.db2.jcc.am.oo.sc(oo.java:3559)
> at com.ibm.db2.jcc.am.oo.b(oo.java:4348)
> at com.ibm.db2.jcc.am.oo.fc(oo.java:743)
> at com.ibm.db2.jcc.am.oo.executeQuery(oo.java:713)
> at org.jboss.jca.adapters.jdbc.CachedPreparedStatement.executeQuery(CachedPreparedStatement.java:107)
> at org.jboss.jca.adapters.jdbc.WrappedPreparedStatement.executeQuery(WrappedPreparedStatement.java:462)
> at org.exoplatform.services.jcr.impl.storage.jdbc.optimisation.db.DB2MYSMultiDbJDBCConnection.findNodesAndProperties(DB2MYSMultiDbJDBCConnection.java:85) [exo.jcr.component.core-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
> at org.exoplatform.services.jcr.impl.storage.jdbc.JDBCStorageConnection.getNodesAndProperties(JDBCStorageConnection.java:1210) [exo.jcr.component.core-1.15.1-CP01-redhat-1.jar:1.15.1-CP01-redhat-1]
> ... 7 more
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2811) The portlet modes are sometimes displayed selected in latest versions of FF and Chrome
by Vu Viet Phuong (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2811?page=com.atlassian.jira.pl... ]
Vu Viet Phuong updated GTNPORTAL-2811:
--------------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/gatein/gatein-portal/pull/423
The problem caused by double click on the wrapper of the popup menu. The solution is follow the design of twitter bootstrap dropdown component
> The portlet modes are sometimes displayed selected in latest versions of FF and Chrome
> --------------------------------------------------------------------------------------
>
> Key: GTNPORTAL-2811
> URL: https://issues.jboss.org/browse/GTNPORTAL-2811
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Interface
> Affects Versions: 3.2.0-GA, 3.5.0.Final
> Environment: GateIn-3.5.0.Final-tomcat7/GateIn-3.2.0.Final-tomcat6
> Java 1.6.0_37
> Firefox 16.0.2/17.0.1/18.0.1 and Chrome 24.0.1312.56
> Reporter: Nicolas Filotto
> Assignee: Vu Viet Phuong
> Priority: Minor
> Labels: portal-s70
> Attachments: Portlet-Modes.jpg
>
> Original Estimate: 5 hours
> Remaining Estimate: 5 hours
>
> It seems that there is a display issue on latest versions of FF and Chrome when we show the portlet modes, indeed sometimes the labels are selected by default as you can see in the screenshot and sometimes it appears normally. After a deeper investigation it seems to be due to the fact that FF believes that we want to select the content by left clicking on the arrow, one way to fix it is to use the trick described here http://stackoverflow.com/questions/69430/is-there-a-way-to-make-text-unse.... By simply adding the css attributes of the class {{unselectable}} in the div of class {{ControlIcon}}, I could fix the issue on chrome and FF (did not test on other browsers). In other words, I modified the file webapps/portal/groovy/portal/webui/application/UIPortlet.gtmpl to replace
> {code}
> <div class="ControlIcon ArrowDownIcon" title="<%=_ctx.appRes("UIPortlet.tooltip.PortletMode");%>" style="position: relative;">
> {code}
> with
> {code}
> <div class="ControlIcon ArrowDownIcon" title="<%=_ctx.appRes("UIPortlet.tooltip.PortletMode");%>" style="position: relative;-moz-user-select: -moz-none;-khtml-user-select: none;-webkit-user-select: none;-ms-user-select: none;user-select: none;" unselectable="on">
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2961) Token Service: Configurable the delay time to run clear expired token
by Hai Nguyen (JIRA)
Hai Nguyen created GTNPORTAL-2961:
-------------------------------------
Summary: Token Service: Configurable the delay time to run clear expired token
Key: GTNPORTAL-2961
URL: https://issues.jboss.org/browse/GTNPORTAL-2961
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Reporter: Hai Nguyen
Assignee: Hai Nguyen
Priority: Minor
Currently, we was hardcode 10 minutes for delay time to run clear expired token.
It should be passed from initial parameter configuration. If the delay time <= 0 then the background thread (for clear expired token) does not create
--
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, 11 months
[JBoss JIRA] (GTNPORTAL-2944) Some of the token unit tests are randomly failed sometimes
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2944?page=com.atlassian.jira.pl... ]
Trong Tran commented on GTNPORTAL-2944:
---------------------------------------
I believe that the cleaning up expired tokens by a thread is leading to these exceptions
> Some of the token unit tests are randomly failed sometimes
> ----------------------------------------------------------
>
> Key: GTNPORTAL-2944
> URL: https://issues.jboss.org/browse/GTNPORTAL-2944
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Trong Tran
> Assignee: Trong Tran
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> The following are some of unit tests failed sometimes that we have got :
> {code}
> Running unit test:testDuplicatedTokenGeneration
> 14:07:46,024 ERROR TestSimpleGeneratorService:103 - Unit test testDuplicatedTokenGeneration did not complete
> java.lang.NullPointerException
> at org.exoplatform.web.security.TestSimpleGeneratorService.testDuplicatedTokenGeneration(TestSimpleGeneratorService.java:80)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> {code}
> {code}
> Running unit test:testCleanExpiredTokens
> 19:58:45,167 ERROR TestGadgetTokenInfoService:103 - Unit test testCleanExpiredTokens did not complete
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testCleanExpiredTokens(TestGadgetTokenInfoService.java:147)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {code}
> {code}
> Running unit test:testCleanExpiredTokens
> 02:46:41,188 ERROR TestPlainCookieTokenService:103 - Unit test testCleanExpiredTokens did not complete
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at org.exoplatform.web.security.AbstractCookieTokenServiceTest.testCleanExpiredTokens(AbstractCookieTokenServiceTest.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {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, 11 months
[JBoss JIRA] (GTNPORTAL-2944) Some of the token unit tests are randomly failed sometimes
by Trong Tran (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-2944?page=com.atlassian.jira.pl... ]
Work on GTNPORTAL-2944 started by Trong Tran.
> Some of the token unit tests are randomly failed sometimes
> ----------------------------------------------------------
>
> Key: GTNPORTAL-2944
> URL: https://issues.jboss.org/browse/GTNPORTAL-2944
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 3.6.0.Beta01
> Reporter: Trong Tran
> Assignee: Trong Tran
> Labels: portal-s70
> Fix For: 3.6.0.Beta02
>
>
> The following are some of unit tests failed sometimes that we have got :
> {code}
> Running unit test:testDuplicatedTokenGeneration
> 14:07:46,024 ERROR TestSimpleGeneratorService:103 - Unit test testDuplicatedTokenGeneration did not complete
> java.lang.NullPointerException
> at org.exoplatform.web.security.TestSimpleGeneratorService.testDuplicatedTokenGeneration(TestSimpleGeneratorService.java:80)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:168)
> {code}
> {code}
> Running unit test:testCleanExpiredTokens
> 19:58:45,167 ERROR TestGadgetTokenInfoService:103 - Unit test testCleanExpiredTokens did not complete
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at org.exoplatform.portal.gadget.TestGadgetTokenInfoService.testCleanExpiredTokens(TestGadgetTokenInfoService.java:147)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {code}
> {code}
> Running unit test:testCleanExpiredTokens
> 02:46:41,188 ERROR TestPlainCookieTokenService:103 - Unit test testCleanExpiredTokens did not complete
> junit.framework.AssertionFailedError: expected:<0> but was:<1>
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.failNotEquals(Assert.java:287)
> at junit.framework.Assert.assertEquals(Assert.java:67)
> at junit.framework.Assert.assertEquals(Assert.java:134)
> at junit.framework.Assert.assertEquals(Assert.java:140)
> at org.exoplatform.web.security.AbstractCookieTokenServiceTest.testCleanExpiredTokens(AbstractCookieTokenServiceTest.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> {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, 11 months