January 2013 - gatein-issues - Jboss List Archives

[JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- claprun(a)redhat.com made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] It is possible to fix this issue by changing the configuration of JBoss WS in standalone.xml (and standalone-ha.xml, of course) by changing: <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host> to <wsdl-host>jbossws.undefined.host</wsdl-host> as explained in https://docs.jboss.org/author/display/JBWS/Advanced+User+Guide#AdvancedUs.... There doesn't seem to be any need to use <modify-wsdl-address>true</modify-wsdl-address>, though. Alessio said that using jbossws.undefined.host probably forces the dynamic rewrite and that he needs to update the docs. > WS ports link to individual nodes' URL instead of loadbalancer > -------------------------------------------------------------- > > Key: GTNWSRP-340 > URL: https://issues.jboss.org/browse/GTNWSRP-340 > Project: GateIn WSRP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Consumer, Producer > Affects Versions: 2.2.0.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.1.Final > > > This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2804) Invalid property 'PortalPermissionSelector' or 'PagePermissionSelector' instead of 'Access Permission Setting'

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2804?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2804: ---------------------------------------------------- Michal Vanco <mvanco(a)redhat.com> made a comment on [bug 902363|https://bugzilla.redhat.com/show_bug.cgi?id=902363] > Invalid property 'PortalPermissionSelector' or 'PagePermissionSelector' instead of 'Access Permission Setting' > -------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-2804 > URL: https://issues.jboss.org/browse/GTNPORTAL-2804 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Peter Palaga > > There is invalid property when setting permissions for portal/page. > This is caused by https://github.com/gatein/gatein-portal/commit/7a0935858c6d13c0267e1a5f4b... (fix for GTNPORTAL-2753) > Version-Release number of selected component (if applicable): > JPP 6.0.0 ER05 > How reproducible: > always > Steps to Reproduce: > 1. sign in > 2. create new portal or page and go to permission setting - invalid access permission tab > > Actual results: > Tab label contains PortalPermissionSelector or similar. > Expected results: > Access Permission Setting should be displayed -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2753) Edit page - can't modify access permissions in switched view mode when Application Registry portlet is on page

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2753?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2753: ---------------------------------------------------- theute(a)redhat.com made a comment on [bug 881374|https://bugzilla.redhat.com/show_bug.cgi?id=881374] Fixed, but other issue poped up https://bugzilla.redhat.com/show_bug.cgi?id=902363 > Edit page - can't modify access permissions in switched view mode when Application Registry portlet is on page > -------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-2753 > URL: https://issues.jboss.org/browse/GTNPORTAL-2753 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Viliam Rockai > Assignee: Viliam Rockai > Labels: portal-s69 > Fix For: 3.6.0.Final > > > Steps to Reproduce: > 1. Log in as root > 2. Edit page - add Application Registry portlet > 3. Switch view mode - View page properties - permissions settings - uncheck Make it public > There is no Add Permission button. When click Edit permissions settings and Select new permission, the Add Permission button appears in the Access permissions tab, but is not clickable. When switch view mode back, then it works fine. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2753) Edit page - can't modify access permissions in switched view mode when Application Registry portlet is on page

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2753?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2753: ---------------------------------------------------- theute(a)redhat.com changed the Status of [bug 881374|https://bugzilla.redhat.com/show_bug.cgi?id=881374] from MODIFIED to ON_QA > Edit page - can't modify access permissions in switched view mode when Application Registry portlet is on page > -------------------------------------------------------------------------------------------------------------- > > Key: GTNPORTAL-2753 > URL: https://issues.jboss.org/browse/GTNPORTAL-2753 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Viliam Rockai > Assignee: Viliam Rockai > Labels: portal-s69 > Fix For: 3.6.0.Final > > > Steps to Reproduce: > 1. Log in as root > 2. Edit page - add Application Registry portlet > 3. Switch view mode - View page properties - permissions settings - uncheck Make it public > There is no Add Permission button. When click Edit permissions settings and Select new permission, the Add Permission button appears in the Access permissions tab, but is not clickable. When switch view mode back, then it works fine. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2772) Gadgets don't work when accessed via https

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2772?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2772: ---------------------------------------------------- theute(a)redhat.com changed the Status of [bug 881975|https://bugzilla.redhat.com/show_bug.cgi?id=881975] from MODIFIED to ON_QA > Gadgets don't work when accessed via https > ------------------------------------------ > > Key: GTNPORTAL-2772 > URL: https://issues.jboss.org/browse/GTNPORTAL-2772 > Project: GateIn Portal > Issue Type: Bug > Components: Shindig > Affects Versions: 3.5.0.Final > Reporter: Marko Strukelj > Assignee: Marko Strukelj > Fix For: 3.6.0.Final > > > When you add gadget on dashboard page, an error message is displayed: > "Errors while retrieving gadget specification file". > Exception is thrown: "SSLException: hostname in certificate didn't match: <localhost/127.0.0.1> != <localhost>". > Info on setting up https: https://docs.jboss.org/author/display/GTNPORTAL35/HTTPS+Configuration. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2771) Ensure that generated rememberme token is really unique

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2771?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2771: ---------------------------------------------------- theute(a)redhat.com changed the Status of [bug 887972|https://bugzilla.redhat.com/show_bug.cgi?id=887972] from MODIFIED to ON_QA > Ensure that generated rememberme token is really unique > ------------------------------------------------------- > > Key: GTNPORTAL-2771 > URL: https://issues.jboss.org/browse/GTNPORTAL-2771 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Marek Posolda > Assignee: Marek Posolda > Labels: EPP6.0-Test-Dev > Fix For: 3.6.0.Final > > > Currently we are generating random rememberme tokens based on random int number (random.nextInt()). In systems with millions or many thousands login, this discriminator is not enough. > We should improve it and fix it either by: > 1) Ensure that generated token is really unique. In system with many logins the random number may not be unique enough, so we need to add other info (like System.currentTimeMillis() or counter or both...) > 2) In case that token already exists, we should generate other one instead of refresh the current one. > Maybe combination of both approaches would be best :-) -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNPORTAL-2754) Priority ignored during navigation import for modes merge and overwrite.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNPORTAL-2754?page=com.atlassian.jira.pl... ] RH Bugzilla Integration commented on GTNPORTAL-2754: ---------------------------------------------------- theute(a)redhat.com changed the Status of [bug 887954|https://bugzilla.redhat.com/show_bug.cgi?id=887954] from MODIFIED to ON_QA > Priority ignored during navigation import for modes merge and overwrite. > ------------------------------------------------------------------------ > > Key: GTNPORTAL-2754 > URL: https://issues.jboss.org/browse/GTNPORTAL-2754 > Project: GateIn Portal > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 3.5.0.Final > Reporter: Nick Scavelli > Assignee: Nick Scavelli > Labels: EPP6.0-Test-Dev > Fix For: 3.6.0.Final > > Attachments: navigation-import-priority-fix.patch > > > Looks like in NavigationImporter navigation priority cannot be updated once created. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-259) Performance issue of WSRP when running over Apache CXF.

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-259?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-259: ------------------------------------------------- theute(a)redhat.com changed the Status of [bug 794143|https://bugzilla.redhat.com/show_bug.cgi?id=794143] from NEW to CLOSED > Performance issue of WSRP when running over Apache CXF. > ------------------------------------------------------- > > Key: GTNWSRP-259 > URL: https://issues.jboss.org/browse/GTNWSRP-259 > Project: GateIn WSRP > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Consumer > Affects Versions: 2.1.0-GA > Reporter: Gary Hu > Assignee: Chris Laprun > Fix For: 2.2.0.Final > > Attachments: jax-ws-catalog.xml > > > There's significant performance issue when running WSRP over Apache CXF on EPP 5.1.1. > To reproduce this: > 1) install Apache CXF on EPP 5.1.1 > 2) go to WSRP admin page and refresh the consumer self1. it takes minutes to refresh the page. > There is a workaround: > add the attached catalog file under jboss-epp-5.1/jboss-as/server/default/deploy/gatein.ear/META-INF when using jbossws-cxf stack . This will pick up the local shema file in cxf-api.jar. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- Michal Vanco <mvanco(a)redhat.com> made a comment on [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] Hi Chris, I was just checking the same scenario which is already described here with JPP 6.0.0 ER05 (which also includes the patch JBPAPP-10497) and it seems like issue is still present. Again I have 2 producer nodes + loadbalancer + another jpp instance as consumer. I registered consumer against loadbanacer WSDL, added remote portlet and failover active producer node. Unfortunately portlet isn't displayed and it's not possible to refresh consumer. I'm getting: java.net.ConnectException: ConnectException invoking http://perf15.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDesc...: Connection refused (perf15 was active producer node which was stopped). There is a change at loadbalancer, host:port/wsrp-producer/v2/MarkupService?wsdl - before it showed different node for each refresh - right now it points to active node only. But... the content is: <definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:bind="urn:oasis:names:tc:wsrp:v2:bind" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="urn:oasis:names:tc:wsrp:v2:wsdl"> <import location="http://perf13.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupServi..." namespace="urn:oasis:names:tc:wsrp:v2:bind"></import> <service name="WSRPService"> <port binding="bind:WSRP_v2_ServiceDescription_Binding_SOAP" name="WSRPServiceDescriptionService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/ServiceDesc..."/> </port> <port binding="bind:WSRP_v2_PortletManagement_Binding_SOAP" name="WSRPPortletManagementService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/PortletMana..."/> </port> <port binding="bind:WSRP_v2_Markup_Binding_SOAP" name="WSRPMarkupService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/MarkupService"/> </port> <port binding="bind:WSRP_v2_Registration_Binding_SOAP" name="WSRPRegistrationService"> <soap:address location="http://perf11.mw.lab.eng.bos.redhat.com:8080/wsrp-producer/v2/Registratio..."/> </port> </service> </definitions> I expected perf13...(loadbalancer) will be used at all wsdl links (that's what patch was about), but it's not. This also means that current docs test at BZ doesn't reflect current portal behavior. Thanks for any updates!!! > WS ports link to individual nodes' URL instead of loadbalancer > -------------------------------------------------------------- > > Key: GTNWSRP-340 > URL: https://issues.jboss.org/browse/GTNWSRP-340 > Project: GateIn WSRP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Consumer, Producer > Affects Versions: 2.2.0.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.1.Final > > > This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down. -- 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

13 years, 2 months

1
0
0 / 0

[JBoss JIRA] (GTNWSRP-340) WS ports link to individual nodes' URL instead of loadbalancer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/GTNWSRP-340?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on GTNWSRP-340: ------------------------------------------------- Michal Vanco <mvanco(a)redhat.com> changed the Status of [bug 880729|https://bugzilla.redhat.com/show_bug.cgi?id=880729] from ON_QA to ASSIGNED > WS ports link to individual nodes' URL instead of loadbalancer > -------------------------------------------------------------- > > Key: GTNWSRP-340 > URL: https://issues.jboss.org/browse/GTNWSRP-340 > Project: GateIn WSRP > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: Consumer, Producer > Affects Versions: 2.2.0.Final > Reporter: Chris Laprun > Assignee: Chris Laprun > Fix For: 2.2.1.Final > > > This results in failover problems when a producer node is taken down since the port on the consumer side might refer to the node URL that is down. -- 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

13 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

gatein-issues January 2013