[JBoss JIRA] (ELYWEB-36) ElytronHttpExchange.getRequestParameters() is prematurely readying the request.
by Farah Juma (Jira)
[ https://issues.jboss.org/browse/ELYWEB-36?page=com.atlassian.jira.plugin.... ]
Farah Juma updated ELYWEB-36:
-----------------------------
Fix Version/s: 1.4.0.CR1
> ElytronHttpExchange.getRequestParameters() is prematurely readying the request.
> -------------------------------------------------------------------------------
>
> Key: ELYWEB-36
> URL: https://issues.jboss.org/browse/ELYWEB-36
> Project: Elytron Web
> Issue Type: Bug
> Components: Undertow Servlet
> Affects Versions: 1.2.3.Final, 1.3.0.Final
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Major
> Fix For: 1.2.4.CR1, 1.3.1.CR1, 1.4.0.CR1
>
>
> When running within Undertow as a Servlet container the method ElytronHttpExchange.getRequestParameters() is prematurely reading the FormData making it unavailable to the HttpServletRequest.
> If instead of handling them manually the request parameters were read from the HttpServletRequest this would not be an issue as the request can re-use it's own prior FormData parsing.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11535?page=com.atlassian.jira.plugin... ]
Paul Ferraro edited comment on WFLY-11535 at 1/21/19 1:42 PM:
--------------------------------------------------------------
This is likely due to https://issues.jboss.org/browse/JGRP-2281 and should have been fixed in WF14.
[~ianrodgers] Was this actually reproduced against WF 14.0.0.Final?
was (Author: pferraro):
This is likely due to https://issues.jboss.org/browse/JGRP-2281 and should have been fixed in WF14.
[~ianrodgers] What this actually reproduced against WF 14.0.0.Final?
> Cluster fails to merge if instances started simultaneously
> ----------------------------------------------------------
>
> Key: WFLY-11535
> URL: https://issues.jboss.org/browse/WFLY-11535
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.Final
> Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster
> Reporter: Ian Rodgers
> Assignee: Paul Ferraro
> Priority: Major
> Attachments: standalone-ha.xml
>
>
> Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members).
> We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join.
> This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix.
> On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11535) Cluster fails to merge if instances started simultaneously
by Paul Ferraro (Jira)
[ https://issues.jboss.org/browse/WFLY-11535?page=com.atlassian.jira.plugin... ]
Paul Ferraro commented on WFLY-11535:
-------------------------------------
This is likely due to https://issues.jboss.org/browse/JGRP-2281 and should have been fixed in WF14.
[~ianrodgers] What this actually reproduced against WF 14.0.0.Final?
> Cluster fails to merge if instances started simultaneously
> ----------------------------------------------------------
>
> Key: WFLY-11535
> URL: https://issues.jboss.org/browse/WFLY-11535
> Project: WildFly
> Issue Type: Bug
> Components: Clustering
> Affects Versions: 14.0.0.Final
> Environment: Keycloak 4.6.0 official docker image, AWS ECS cluster
> Reporter: Ian Rodgers
> Assignee: Paul Ferraro
> Priority: Major
> Attachments: standalone-ha.xml
>
>
> Our Keycloak docker cluster has four instances, clustered using Jgroups/Infinispan as per the standalone-ha.xml. If you start them all simultaneously the "Receive new cluster" logs indicate four separate clusters, each with a single member. They never get merged into the proper single cluster of four members. It seems to be the merging that has changed. The application then fails (we are not using sticky sessions, and each member is ignorant of the sessions on the other members).
> We can only start the cluster by first starting one instance, then when it is running, starting the other three. The logs then indicate the creation of a single cluster which subsequent instances join.
> This is consistent behaviour, and when we revert back to v.4.5.0, the issue goes away, Unfortunately we need 4.6.0 for an important fix.
> On 4.5.0 we get the message "Received new, MERGED cluster view for channel ejb: MergeView::" when it detects a number of subgroups to merge. This never appears in 4.6.0.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11621) Upgrade Weld to 3.1.0.Final
by Brian Stansberry (Jira)
[ https://issues.jboss.org/browse/WFLY-11621?page=com.atlassian.jira.plugin... ]
Brian Stansberry commented on WFLY-11621:
-----------------------------------------
Thanks, Matej, for the thorough info!
> Upgrade Weld to 3.1.0.Final
> ---------------------------
>
> Key: WFLY-11621
> URL: https://issues.jboss.org/browse/WFLY-11621
> Project: WildFly
> Issue Type: Component Upgrade
> Components: CDI / Weld
> Affects Versions: 15.0.1.Final
> Reporter: Matej Novotny
> Assignee: Matej Novotny
> Priority: Major
> Fix For: 16.0.0.CR1
>
>
> Weld 3.1.0.Final release is scheduled in early Feb, so this is a tracking issue for now. It is going to bump the minor version of Weld core and API as it contains several API/SPI changes and will need adjustments on WFLY side.
> Namely it:
> * Brings new API for class(WELD-2556) defining which will leverage jboss-modules ({{ClassDefiner}}
> ** This will need impl on WFLY side ([draft on my branch|https://github.com/manovotn/wildfly/tree/weld2556]) assuming jboss-modules 1.9 makes it to WFLY in time
> ** Required for any JDK 12 execution with Weld
> * Removes deprecated code from API/SPI (WELD-2558)
> ** Requires few removals in WFLY code ([done on this branch|https://github.com/manovotn/wildfly/tree/weld2558])
> * Brings new API for CDI context propagation (WELD-2497)
> ** This is no-op for WFLY as it doesn't use this API
> * [plus some changes on Weld core side]
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3474) Create HTML and CSS for List/Map data objects
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3474?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi edited comment on DROOLS-3474 at 1/21/19 12:25 PM:
--------------------------------------------------------------------
[~srambach]
yes, I know ul can contain only li. This is what I generate. I'm not an html-er, so probably it is not the best structure; anyway, I think it gives you an idea.
Using that, I could reuse the java code I used for the list to populate the key/value items in the map.
Last, I am not sure in your last example (Books) what should be the "key" and what the "value", but probably we are getting to the same structure.
[^Drools-DataObjectMap-Generated.html]
Let me know!
Thanks
Gabriele
was (Author: gabriolo):
[~srambach]
yes, I know ul can contain only li. This is what I generate. I'm not an html-er, so probably it is not the best structure; anyway, I think it gives you an idea.
Using that, I could reuse the java code I used for the list to populate the key/value items in the map.
Last, I do not understand in your last example (Books) what should be the "key" and what the "value".
[^Drools-DataObjectMap-Generated.html]
Let me know!
Thanks
Gabriele
> Create HTML and CSS for List/Map data objects
> ---------------------------------------------
>
> Key: DROOLS-3474
> URL: https://issues.jboss.org/browse/DROOLS-3474
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Drools-DataObjectMap-Generated.html, Rectangle.png, Rectangle2.png, editmap.jpg, editmap_items.jpg, firefox.png, list_edit_box.html
>
>
> Provide HTML and CSS for the designs in Drools-3098.
> Will first provide HTML structure, and follow up with CSS styling.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3474) Create HTML and CSS for List/Map data objects
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3474?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3474:
-------------------------------------
Attachment: Drools-DataObjectMap-Generated.html
> Create HTML and CSS for List/Map data objects
> ---------------------------------------------
>
> Key: DROOLS-3474
> URL: https://issues.jboss.org/browse/DROOLS-3474
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Drools-DataObjectMap-Generated.html, Rectangle.png, Rectangle2.png, editmap.jpg, editmap_items.jpg, firefox.png, list_edit_box.html
>
>
> Provide HTML and CSS for the designs in Drools-3098.
> Will first provide HTML structure, and follow up with CSS styling.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (DROOLS-3474) Create HTML and CSS for List/Map data objects
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3474?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi commented on DROOLS-3474:
------------------------------------------
[~srambach]
yes, I know ul can contain only li. This is what I generate. I'm not an html-er, so probably it is not the best structure; anyway, I think it gives you an idea.
Using that, I could reuse the java code I used for the list to populate the key/value items in the map.
Last, I do not understand in your last example (Books) what should be the "key" and what the "value".
[^Drools-DataObjectMap-Generated.html]
Let me know!
Thanks
Gabriele
> Create HTML and CSS for List/Map data objects
> ---------------------------------------------
>
> Key: DROOLS-3474
> URL: https://issues.jboss.org/browse/DROOLS-3474
> Project: Drools
> Issue Type: Story
> Components: Scenario Simulation and Testing
> Reporter: Amy Glass
> Assignee: Sarah Rambacher
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: Drools-DataObjectMap-Generated.html, Rectangle.png, Rectangle2.png, editmap.jpg, editmap_items.jpg, firefox.png, list_edit_box.html
>
>
> Provide HTML and CSS for the designs in Drools-3098.
> Will first provide HTML structure, and follow up with CSS styling.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months
[JBoss JIRA] (WFLY-11623) Incorrect warning from LoggingConfigurationFileReloader
by ehsavoie Hugonnet (Jira)
ehsavoie Hugonnet created WFLY-11623:
----------------------------------------
Summary: Incorrect warning from LoggingConfigurationFileReloader
Key: WFLY-11623
URL: https://issues.jboss.org/browse/WFLY-11623
Project: WildFly
Issue Type: Bug
Components: JMS
Affects Versions: 15.0.1.Final
Reporter: ehsavoie Hugonnet
Assignee: ehsavoie Hugonnet
1:08:06,687 WARN [org.apache.activemq.artemis.core.server] (Thread-17 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$6@46dfb7b8)) AMQ222276: Failed to process changes to the logging configuration file: file:/home/ehsavoie/dev/wildfly/wildfly/build/target/wildfly-16.0.0.Beta1-SNAPSHOT/standalone/configuration/logging.properties
This is due to the fact that ConfigurationPersistence implements LogContextConfiguration and Configurator. If the configurator implements LogContextConfiguration we should return it in org.apache.activemq.artemis.core.server.LoggingConfigurationFileReloader
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 5 months