[JBoss JIRA] Created: (GTNWSRP-235) It's not possible to create two consumers with different name in clustered environment
by Michal Vanco (JIRA)
It's not possible to create two consumers with different name in clustered environment
--------------------------------------------------------------------------------------
Key: GTNWSRP-235
URL: https://issues.jboss.org/browse/GTNWSRP-235
Project: GateIn WSRP
Issue Type: Bug
Affects Versions: 2.0.0-GA
Environment: 2 EPP 5.1.1 DEV01 instances in cluster + loadbalancer as producer
1 local EPP5.1.1 DEV01 instance as consumer
Reporter: Michal Vanco
Assignee: Chris Laprun
Fix For: 2.0.1-GA
Attachments: wsrp-cluster-names.txt
Exact steps to reproduce:
- start clustered environment with loadbalancer as producer
- register consumer with name 'test1'
- delete consumer
- register consumer with name 'test2' -> error:
org.chromattic.api.DuplicateNameException: Attempt to insert context EntityContext[state=ObjectStatus[status=TRANSIENT],mapper=EntityMapper[class=class org.gatein.portal.wsrp.state.producer.registrations.mapping.ConsumerMapping,typeName=wsrp:consumer]] as an existing child with name mvanco-laptop_WSRP_v1_version child of node /wsrp:consumersandgroups
(log from producer attached)
Note: I have also applied patched gatein wsrp jar (for epp5.1.1 CR1) with the same result.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] Created: (GTNWSRP-237) Potential NPE in org.gatein.portal.wsrp.structure.MOPConsumerStructureProvider
by Minh Hoang TO (JIRA)
Potential NPE in org.gatein.portal.wsrp.structure.MOPConsumerStructureProvider
------------------------------------------------------------------------------
Key: GTNWSRP-237
URL: https://issues.jboss.org/browse/GTNWSRP-237
Project: GateIn WSRP
Issue Type: Bug
Reporter: Minh Hoang TO
Assignee: Chris Laprun
{code}
public void addWindow(String windowName, String uuid)
{
// add suffix in case we have several windows with the same name in the page
if (childrenWindows.containsKey(windowName))
{
if (windowName.endsWith("|"))
{
windowName += "|";
}
else
{
windowName += windowName + " |";
}
}
childrenWindows.put(windowName, uuid);
}
{code}
There is NPE at windowName.endsWith("|") in case saved page contains two non-titled portlet windows referring to the same portlet object.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (GTNPORTAL-2340) WebAppController needs to start RequestLifeCycle for every processing (including static resource processing)
by Marek Posolda (JIRA)
Marek Posolda created GTNPORTAL-2340:
----------------------------------------
Summary: WebAppController needs to start RequestLifeCycle for every processing (including static resource processing)
Key: GTNPORTAL-2340
URL: https://issues.jboss.org/browse/GTNPORTAL-2340
Project: GateIn Portal
Issue Type: Enhancement
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-Beta01
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 3.2.0-CR01
Second thing is not so bad but a bit more tricky. The piece of code in WebAppController:
{code}
if (!started)
{
RequestLifeCycle.begin(ExoContainerContext.getCurrentContainer());
started = true;
}
.....
processed = handler.execute(new ControllerContext(this,
router, req, res, parameters));
.....
if (started)
{
RequestLifeCycle.end();
}
{code}
This means that we need to start RequestLifeCycle for processing of
every resource including static resource. And startup of some services
is quite expensive (like startup of OrganizationService requires startup
of Hibernate transaction). In other words, currently we are starting
Hibernate transaction for processing images and other static resources.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (GTNPORTAL-2361) Validator's error in GroupManagement
by Marek Posolda (JIRA)
Marek Posolda created GTNPORTAL-2361:
----------------------------------------
Summary: Validator's error in GroupManagement
Key: GTNPORTAL-2361
URL: https://issues.jboss.org/browse/GTNPORTAL-2361
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.2.0-CR01
Reporter: Marek Posolda
Assignee: Chris Laprun
Fix For: 3.2.0-GA
http://eppdev01.brq.redhat.com:8080/portal -> login as root -> Go to OrganizationManagement -> Click to "Group Management" -> Click to some group in the left part -> Click to button "Save" in right part (with User Name left empty.) -> Now I have message "Unneeded by this implementation". I saw something like that in your validator's code. (See screenshot)
It's caused by MultipleConditionsValidator, which is trying to throw validation error because of empty username. Problem is that method getMessageLocalization is not not supported for this implementation and it throws error "Unneeded by this implementation"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 2 months