[JBoss JIRA] Created: (GTNPORTAL-2092) Upgrade to JCR 1.14.0-GA
by Boleslaw Dawidowicz (JIRA)
Upgrade to JCR 1.14.0-GA
------------------------
Key: GTNPORTAL-2092
URL: https://issues.jboss.org/browse/GTNPORTAL-2092
Project: GateIn Portal
Issue Type: Task
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01
Reporter: Boleslaw Dawidowicz
Assignee: Boleslaw Dawidowicz
Fix For: 3.2.0-M02
Upgrade component versions related to JCR:
<org.exoplatform.kernel.version>2.3.0-GA</org.exoplatform.kernel.version>
<org.exoplatform.core.version>2.4.0-GA</org.exoplatform.core.version>
<org.exoplatform.ws.version>2.2.0-GA</org.exoplatform.ws.version>
<org.exoplatform.jcr.version>1.14.0-GA</org.exoplatform.jcr.version>
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Updated: (GTNPORTAL-1974) Add Node button always create new node on the top level
by Minh Hoang TO (JIRA)
[ https://issues.jboss.org/browse/GTNPORTAL-1974?page=com.atlassian.jira.pl... ]
Minh Hoang TO updated GTNPORTAL-1974:
-------------------------------------
Original Estimate: 4 hours
Remaining Estimate: 4 hours
Labels: EPP_5.1.x_Triage portal-s60 (was: EPP_5.1.x_Triage)
> Add Node button always create new node on the top level
> -------------------------------------------------------
>
> Key: GTNPORTAL-1974
> URL: https://issues.jboss.org/browse/GTNPORTAL-1974
> Project: GateIn Portal
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Michal Vanco
> Labels: EPP_5.1.x_Triage, portal-s60
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Using Add Node button in Navigation Management (Site or Group) always create new node at the top level.
> When you have some subnode selected and Add Node button is used, node is created at the top level.
> Only way to create subnode is to use context menu otherwise node selection is ignored.
> Maybe it's wanted behavior, but IMO users would appreciate to create node on current selection.
> Or is there reason for this behavior?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months
[JBoss JIRA] Created: (GTNPORTAL-2088) Infinite loop when edit banner portlet with invalid value
by Michal Vanco (JIRA)
Infinite loop when edit banner portlet with invalid value
---------------------------------------------------------
Key: GTNPORTAL-2088
URL: https://issues.jboss.org/browse/GTNPORTAL-2088
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-M01, 3.1.0-GA
Environment: verified with EPP 5.2.0 DEV03 and 5.1.1 GA
Reporter: Michal Vanco
Fix For: 3.2.0-M02
Attachments: epp52.jps
When you edit banner portlet with invalid value, close & open browser -> you are not able to access portal.
With each refresh it takes another database connection and after 20 attempts you end up with:
13:20:10,748 ERROR [JDBCExceptionReporter] Unable to get managed connection for gatein-idm; - nested throwable: (javax.resource.ResourceException: Unable to get managed connection for gatein-idm)
I'm also attaching thread dump where you can see that 20 threads are running in following classes:
at java.util.HashMap.get(HashMap.java:300)
at org.exoplatform.resolver.ApplicationResourceResolver.getResourceResolver(ApplicationResourceResolver.java:70)
at org.exoplatform.webui.application.WebuiRequestContext.getResourceResolver(WebuiRequestContext.java:184)
I think there is problem with while loop in WebuiRequestContext.getResourceResolver method.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 7 months