Bug 1032105 - Testing with increasing number of Portal containers per JPP instance
Summary: Testing with increasing number of Portal containers per JPP instance
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Portal Platform 6
Classification: JBoss
Component: Requirements
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: 6.1.1
Assignee: mposolda
QA Contact: Dominik Pospisil
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-19 14:56 UTC by Divya Mehra
Modified: 2014-01-28 14:11 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-28 14:11:00 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
EXO WCM JIRA JCR-2252 0 None None None Never
Red Hat Issue Tracker GTNPORTAL-3296 0 Minor Resolved Possibility to update users via organization-configuration.xml 2014-03-11 00:52:00 UTC

Description Divya Mehra 2013-11-19 14:56:17 UTC 
Description of problem:

Document start-up times, performance, scalability with increasing number of Portal Containers (up to 50) in a single JPP instance.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Note You need to log in before you can comment on or make changes to this bug.