July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBPORTAL-1211) portal load test: optimize DB query

by Prabhat Jha (JIRA)

portal load test: optimize DB query ----------------------------------- Key: JBPORTAL-1211 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1211 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Core Affects Versions: 2.4.1 SP1 Reporter: Prabhat Jha Assigned To: Julien Viet During portal load test, we found some bottlenecks related to call to DB. At 500 simultaneous user thread, we start seeing org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout with min pool size of 20 and max pool size of 40. I am not sure but the following query which does join of 6 tables probably also needs to be optimized select portalobje0_.PK as PK20_0_, portalobje0_.LISTENER as LISTENER20_0_, portalobje0_4_.INSTANCE_REF as INSTANCE2_27_0_, case when portalobje0_1_.PK is not null then 1 when portalobje0_2_.PK is not null then 2 when portalobje0_3_.PK is not null then 3 when portalobje0_4_.PK is not null then 4 when portalobje0_.PK is not null then 0 end as clazz_0_, declaredpr1_.OBJECT_KEY as OBJECT1_2_, declaredpr1_.jbp_VALUE as jbp2_2_, declaredpr1_.NAME as NAME2_, modes2_.PK as PK3_, modes2_.name as name3_, windowstat3_.PK as PK4_, windowstat3_.name as name4_ from JBP_PORTAL_OBJECT portalobje0_ left outer join JBP_CONTEXT portalobje0_1_ on portalobje0_.PK=portalobje0_1_.PK left outer join JBP_PORTAL portalobje0_2_ on portalobje0_.PK=portalobje0_2_.PK left outer join JBP_PAGE portalobje0_3_ on portalobje0_.PK=portalobje0_3_.PK left outer join JBP_WINDOW portalobje0_4_ on portalobje0_.PK=portalobje0_4_.PK left outer join JBP_PORTAL_OBJECT_PROPS declaredpr1_ on portalobje0_.PK=declaredpr1_.OBJECT_KEY left outer join JBP_PORTAL_MODE modes2_ on portalobje0_.PK=modes2_.PK left outer join JBP_PORTAL_WINDOW_STATE windowstat3_ on portalobje0_.PK=windowstat3_.PK where portalobje0_.PK=? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

4
9
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-398) allow for typed properties (PortalObject Properties for Portals, Pages, and Windows)

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-398?page=all ] Julien Viet resolved JBPORTAL-398. ---------------------------------- Resolution: Out of Date We should replace it with meta data that would provide a behavior for the properties. > allow for typed properties (PortalObject Properties for Portals, Pages, and Windows) > ------------------------------------------------------------------------------------ > > Key: JBPORTAL-398 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-398 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Reporter: Martin Holzner > Priority: Minor > > Julien: > "we could also add more typed properties, for instance for the portal > object listener" -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1393) Maximized portlet window DynaRenderOptions

by Ovidiu Nichifor (JIRA)

Maximized portlet window DynaRenderOptions ------------------------------------------ Key: JBPORTAL-1393 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1393 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Theme Affects Versions: 2.6.CR2 Reporter: Ovidiu Nichifor Assigned To: Julien Viet Priority: Minor Assuming you are in dashboard, have you noticed that if you maximize a portlet and try to move it, although there is only one maximized region it will stick to the same coordinates (i.e. the position does not change). BUT! Once you hit the normal action mode, the dashboard will display all its portlets except the one you maximized & moved? A work around has been proposed here - http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4043228#4043228 but this implies to rebuild portal jars. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
1
0 / 0

[JBoss JIRA] Resolved: (JBPTL-51) Have a different page to change password

by Thomas Heute (JIRA)

[ http://jira.jboss.com/jira/browse/JBPTL-51?page=all ] Thomas Heute resolved JBPTL-51. ------------------------------- Resolution: Out of Date Assignee: Thomas Heute > Have a different page to change password > ---------------------------------------- > > Key: JBPTL-51 > URL: http://jira.jboss.com/jira/browse/JBPTL-51 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Reporter: Thomas Heute > Assigned To: Thomas Heute > Priority: Optional > Attachments: JBPTL-51.zip > > Original Estimate: 1 hour, 30 minutes > Remaining Estimate: 1 hour, 30 minutes > > Just to make it more convenient, a different page (than the edit profile page) to change the password would be nice. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-393) Security audit/log

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-393?page=all ] Julien Viet resolved JBPORTAL-393. ---------------------------------- Resolution: Out of Date Not in the scope of the portal project > Security audit/log > ------------------ > > Key: JBPORTAL-393 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-393 > Project: JBoss Portal > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Portal Core > Affects Versions: 2.2 Final > Reporter: Noel Rocher > Priority: Optional > > Provide a mean to log and see all security problems that occur. > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Resolved: (JBPORTAL-699) Blog Portlet

by Julien Viet (JIRA)

[ http://jira.jboss.com/jira/browse/JBPORTAL-699?page=all ] Julien Viet resolved JBPORTAL-699. ---------------------------------- Resolution: Out of Date Since labs are working on it. > Blog Portlet > ------------ > > Key: JBPORTAL-699 > URL: http://jira.jboss.com/jira/browse/JBPORTAL-699 > Project: JBoss Portal > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Portal Samples > Reporter: Roy Russo > Priority: Optional > > A simple blog portlet with the following features: > - Blogs categorized by username. > - Blog should offer a global RSS feed and a category RSS feed. > - Users with the proper credentials should be able to: > -- post blogs > -- edit/delete blog postings. > - Anonymous users should not be able to view admin screen and can only view blog postings. > * Optional feature of allowing comments is a nice-to-have. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1328) Management Portlet, unable to create Window for page.

by Anders Andersen (JIRA)

Management Portlet, unable to create Window for page. ----------------------------------------------------- Key: JBPORTAL-1328 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1328 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Portlet Affects Versions: 2.6.Beta1 Environment: OS: Mac OSX 10.4.9 Browser: Firefox 2.0.0.3 or Safari Database: both Mysql5 and hsqldb Reporter: Anders Andersen Assigned To: Julien Viet Priority: Critical It is not possible any longer to add a window to a page. There is no data entry field any longer. The documentation describes a Management Portlet able to add windows to a page by selecting an instance. Unless I have misunderstood the portal this seems to be a fatal error in the portal. In all previous versions it was possible to relate an instance to a page by creating a window. It is still possible to remove a window, but as stated not possible to add a window :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1114) Redo quickstart guide

by Roy Russo (JIRA)

Redo quickstart guide --------------------- Key: JBPORTAL-1114 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1114 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal Documentation Affects Versions: 2.6.Alpha1 Reporter: Roy Russo Assigned To: Roy Russo Fix For: 2.6.Alpha1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

3
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1071) Clusterting problems in jboss-portal-2.4.1.CR1

by Rajesh Rajasekaran (JIRA)

Clusterting problems in jboss-portal-2.4.1.CR1 ---------------------------------------------- Key: JBPORTAL-1071 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1071 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Rajesh Rajasekaran "Portal Session Replication" and "CMS Clustering" scenarios explained in the wiki do not work with jboss-portal-2.4.1.CR1 http://wiki.jboss.org/wiki/Wiki.jsp?page=PortalClusteringTests This was tested using postgresql -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

2
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1110) Portlet Deployment Directory only allows deploy

by symmetrysolutions (JIRA)

Portlet Deployment Directory only allows deploy ----------------------------------------------- Key: JBPORTAL-1110 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1110 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Server Affects Versions: 2.4 Final Environment: Windows XP SP1, JBoss v4.0.5.GA, Java 1.5 Reporter: symmetrysolutions Assigned To: Julien Viet When the portlet is not deployed from the JBoss Home/server/default/deploy directory the portlet will not deploy. The following error is produced: 2006-11-10 08:59:55,937 ERROR [org.apache.catalina.core.StandardContext] Error starting static Resources java.lang.IllegalArgumentException: Document base C:\jboss-4.0.5.GA\server\default\.\deploy_40\helloworldjsf.war does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:140) at org.apache.catalina.core.StandardContext.resourcesStart(StandardContext.java:3848) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4019) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:759) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:739) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:524) The portlet is not being deployed from C:\jboss-4.0.5.GA\server\default\.\deploy_40 it is actually in C:\deploy_40 but the portal seems to assume the deployment is from the jboss server deploy directory. I always modify my deploy URL in my JBoss service to allow deployments from another directory. The portal itself is actually in this directory and is deploying correctly allong with all of its default portals but my portlet will not deploy unless I put it in the C:\jboss-4.0.5.GA\server\default\deploy directory. The portlet I am using is the default JSF Hello World portlet. I have not tried with other portlets. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

18 years, 10 months

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2007