December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4229) Make http status return while deploying configurable

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4229?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4229. ---------------------------- > Make http status return while deploying configurable > ---------------------------------------------------- > > Key: WFLY-4229 > URL: https://issues.jboss.org/browse/WFLY-4229 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 8.2.0.Final > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha4 > > > For deployment behind proxies it would be more than welcome to have server return 503 instead of 404 while application is deploying. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4770) Upgrade HAL to 2.8.0.Alpha0

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4770?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4770. ---------------------------- > Upgrade HAL to 2.8.0.Alpha0 > --------------------------- > > Key: WFLY-4770 > URL: https://issues.jboss.org/browse/WFLY-4770 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Harald Pehl > Assignee: Harald Pehl > Fix For: 10.0.0.Alpha3 > > > HAL 2.7.1 contains a critical bugfix for HAL-617. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4812) Upgrade Infinispan to 7.2.3.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4812?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4812. ---------------------------- > Upgrade Infinispan to 7.2.3.Final > --------------------------------- > > Key: WFLY-4812 > URL: https://issues.jboss.org/browse/WFLY-4812 > Project: WildFly > Issue Type: Component Upgrade > Components: Clustering > Affects Versions: 9.0.0.CR2, 10.0.0.Alpha3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.Final, 10.0.0.Alpha4 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4746) SSO cookie-name attribute is ignored

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4746?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4746. ---------------------------- > SSO cookie-name attribute is ignored > ------------------------------------ > > Key: WFLY-4746 > URL: https://issues.jboss.org/browse/WFLY-4746 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5032) Authentication token in session triggers replication of session each request

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5032?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5032. ---------------------------- > Authentication token in session triggers replication of session each request > ---------------------------------------------------------------------------- > > Key: WFLY-5032 > URL: https://issues.jboss.org/browse/WFLY-5032 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.0.0.Alpha6 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 10.0.0.Beta1 > > > If an authentication token exists in the web session, and the user is using FORM or a custom authentication mechanism, then that token is read from the session each request. The token is treated as a mutable object by the clustering code and triggers replication of the session on each request. > Annotating this with @Immutable will fix the problem. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4800) No reload required when add mime-mapping to servlet-container

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4800?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4800. ---------------------------- > No reload required when add mime-mapping to servlet-container > ------------------------------------------------------------- > > Key: WFLY-4800 > URL: https://issues.jboss.org/browse/WFLY-4800 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Alpha3 > Reporter: Jan Stourac > Assignee: Stuart Douglas > Fix For: 10.0.0.Alpha4 > > Attachments: simple-web.war > > > When mime-mapping is added to servlet container then no reload of server is required, although change takes effect after server restart is performed. > Expected behaivour is either that change takes effect immediatelly after configuration is changed or that server reload is required in response message and result of the operation. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2885) HttpListenerService start doesn't clean up if start fails

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2885?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-2885. ---------------------------- > HttpListenerService start doesn't clean up if start fails > --------------------------------------------------------- > > Key: WFLY-2885 > URL: https://issues.jboss.org/browse/WFLY-2885 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Tomaz Cerar > Fix For: 10.0.0.Alpha5 > > > HttpListenerService.prestart() does some registration stuff that doesn't get cleaned up if start() fails later on. > I noticed this in the logs while debugging RolloutPlanTestCase failures on JDK8. Probably unrelated to those failures; just an FYI to give context. > What happens in the test is it does an http-listener=xxx:add that is deliberately meant to fail in Stage.RUNTIME (due to a port conflict.) Later on the test does the same thing again. It's meant to fail there too, but I noticed in the logs that it failed for the *wrong reason*, before the port conflict: > {code} > [Server:main-one] 10:13:44,128 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.undertow.listener.maxFailOnePlan: org.jboss.msc.service.StartException in service jboss.undertow.listener.maxFailOnePlan: Failed to start service > [Server:main-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1904) [jboss-msc-1.2.0.Final.jar:1.2.0.Final] > [Server:main-one] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0] > [Server:main-one] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0] > [Server:main-one] at java.lang.Thread.run(Thread.java:744) [rt.jar:1.8.0] > [Server:main-one] Caused by: java.lang.IllegalArgumentException: UT000053: Listener maxFailOnePlan already registered > [Server:main-one] at io.undertow.server.ListenerRegistry.addListener(ListenerRegistry.java:32) [undertow-core-1.0.0.CR5.jar:1.0.0.CR5] > [Server:main-one] at org.wildfly.extension.undertow.HttpListenerService.preStart(HttpListenerService.java:107) > [Server:main-one] at org.wildfly.extension.undertow.ListenerService.start(ListenerService.java:121) > [Server:main-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) [jboss-msc-1.2.0.Final.jar:1.2.0.Final] > [Server:main-one] at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) [jboss-msc-1.2.0.Final.jar:1.2.0.Final] > [Server:main-one] ... 3 more > {code} > The error ^^^ will continue to happen until the server is restarted, even if the port conflict situation was fixed. It's because the ListenerRegistry.addListener call from the first attempt was never cleaned up. > Cleaning up would have to be done in a catch block in ListenerService.start(). The code in stop() that normally does the cleanup does not get called if service start has failed. > I expect we have this kind of problem in many places in the WF code. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5001) Undertow mod_cluster CLI: Control LBGroup: Enable Nodes, Disable Nodes, Stop Nodes

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5001?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5001. ---------------------------- > Undertow mod_cluster CLI: Control LBGroup: Enable Nodes, Disable Nodes, Stop Nodes > ---------------------------------------------------------------------------------- > > Key: WFLY-5001 > URL: https://issues.jboss.org/browse/WFLY-5001 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Reporter: Michal Karm Babacek > Assignee: Stuart Douglas > Priority: Critical > Labels: mod_cluster > Fix For: 10.0.0.Beta1 > > > As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities. > h3. Control Load Balancing Groups > For any Load Balancing Group enabled environment, it is essential to be able to Enable Nodes, Disable Nodes and Stop Nodes. These actions will enable, disable and stop all contexts with all nodes present in a particular Load Balancing Group. > It is an equivalent of sending this MCMP message attributes ({{LB-GROUP-1}} is an arbitrary example Load Balancing Group name): > * Enable Nodes {{Cmd=ENABLE-APP&Range=DOMAIN&Domain=LB-GROUP-1}} > * Disable Nodes {{Cmd=DISABLE-APP&Range=DOMAIN&Domain=LB-GROUP-1}} > * Stop Nodes {{Cmd=STOP-APP&Range=DOMAIN&Domain=LB-GROUP-1}} > h3. Call to action > Enable user to carry out these actions via WildFly CLI. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4974) XAResource of ActiveMQ does not implements org.jboss.tm.XAResourceWrapper

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4974?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4974. ---------------------------- > XAResource of ActiveMQ does not implements org.jboss.tm.XAResourceWrapper > ------------------------------------------------------------------------- > > Key: WFLY-4974 > URL: https://issues.jboss.org/browse/WFLY-4974 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha6 > > > messaging-activemq subsystem does not load properly the service for ActiveMQXAResourceWrapperFactory. > The service file contains a typo: it is org.apache.activemq.service.extensions.xa.ActiveMQXAResourceWrapperFactory while it must be org.apache.activemq.artemis.service.extensions.xa.ActiveMQXAResourceWrapperFactory -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5242) Inconsistent format for IPv6 addresses in server log

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5242?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5242. ---------------------------- > Inconsistent format for IPv6 addresses in server log > ---------------------------------------------------- > > Key: WFLY-5242 > URL: https://issues.jboss.org/browse/WFLY-5242 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Beta2 > Reporter: Lyle Wang > Assignee: Chao Wang > Priority: Minor > Fix For: 10.0.0.CR1 > > > Description of problem: > When IPv6 is used, square brackets for IPv6 addresses are missed in some of log entries. Specifically, the address format from Undertow logs is different from those "WFLYSRV" logs. > How reproducible: > Always > Steps to Reproduce: > 1. Config IPv6 (example: https://docs.jboss.org/author/display/WFLY10/Interfaces+and+ports) > 2. Start WildFly and check the log > Actual results: > ---------------------------------------- > 2015-08-31 12:51:47,812 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /0:0:0:0:0:0:0:1:8080 > ...... > 2015-08-31 12:51:48,431 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://[::1]:9993/management > 2015-08-31 12:51:48,432 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://[::1]:9993 > ---------------------------------------- > In Undertow logs it's like "/0:0:0:0:0:0:0:1:8080" but in WildFly server logs "http://[::1]:9993/management" > Expected results: > Consistent format should be used for IPv6 address across different components and the address is enclosed in square brackets [ ]. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2017