[JBoss JIRA] (GTNPORTAL-2809) Insert New Column in Columns Layout Container doesn't work
by Viliam Rockai (JIRA)
Viliam Rockai created GTNPORTAL-2809:
----------------------------------------
Summary: Insert New Column in Columns Layout Container doesn't work
Key: GTNPORTAL-2809
URL: https://issues.jboss.org/browse/GTNPORTAL-2809
Project: GateIn Portal
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: User Interface, WebUI
Affects Versions: 3.5.0.Final
Reporter: Viliam Rockai
Assignee: Viliam Rockai
Insert new column
Steps to reproduce:
1. Log in as Root
2. Site Editor - Edit Page
3. Drag and drop any Columns container in the page
On the column menu there is drop down icon offering a new menu with choices. This menu is not opened.
--
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
11 years, 3 months
[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:
----------------------------------------------------
vramik(a)redhat.com changed the Status of [bug 887972|https://bugzilla.redhat.com/show_bug.cgi?id=887972] from ON_QA to VERIFIED
> 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
11 years, 3 months
[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]
Note that applying the change to wsdl-host only seems to work *when* the JBoss WS patch has been applied. It seems that using a non-patched JBoss WS version results in WSRP not working at all in clustered or single-node mode since the port URLs use jbossws.undefined.host instead of localhost in that case and are not being rewritten.
> 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
11 years, 3 months