September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2592) wildfly-service.exe and jbosspass wrong with # inside

by Lukas Vydra (Jira)

[ https://issues.redhat.com/browse/WFCORE-2592?page=com.atlassian.jira.plug... ] Lukas Vydra commented on WFCORE-2592: ------------------------------------- Characters ; and # as part of the procrun syntax can be escaped by putting them into single quotes, so my'#'pass should by working. We could also add character escaping into service.bat > wildfly-service.exe and jbosspass wrong with # inside > ----------------------------------------------------- > > Key: WFCORE-2592 > URL: https://issues.redhat.com/browse/WFCORE-2592 > Project: WildFly Core > Issue Type: Bug > Components: Scripts > Affects Versions: 8.0.0.Beta5 > Reporter: Seb Dk > Assignee: Lukas Vydra > Priority: Major > > Hi there, > > I am installing wildfy 10.1.0 as service on a win 20012 server. > It is working but I cannot stop the service. > I figured out where the problem is coming from. > > When I installe Wildly as a service, I run the following command: > E:\Products\wildfly-10.1.0.Final\bin\service>service.bat install /serviceuser .\JBoss /servicepass my#pass /controller localhost:9991 /jbossuser myuser /jbosspass *my#pass* > > But I can see whe I am trying to stop the service, the command running is: > E:\Products\wildfly-10.1.0.Final\bin\jboss-cli.bat --controller=localhost:9991 --connect --user=myuser --password=*my" "pass* --command=:shutdown > > Any workaround? > > Thanks, > > S. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13918) Bump MicroProfile SmallRye Config to activate Variable Expansion

by Sven Haag (Jira)

[ https://issues.redhat.com/browse/WFLY-13918?page=com.atlassian.jira.plugi... ] Sven Haag updated WFLY-13918: ----------------------------- Summary: Bump MicroProfile SmallRye Config to activate Variable Expansion (was: Bump MicroProfile-Config smallrye-config (to 1.9.0)) > Bump MicroProfile SmallRye Config to activate Variable Expansion > ---------------------------------------------------------------- > > Key: WFLY-13918 > URL: https://issues.redhat.com/browse/WFLY-13918 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Config > Affects Versions: 20.0.1.Final, 21.0.0.Beta1 > Reporter: Sven Haag > Assignee: Jeff Mesnil > Priority: Major > > Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. > See: [https://github.com/smallrye/smallrye-config/releases] > > Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13918) Bump MicroProfile SmallRye Config to activate Variable Expansion

by Sven Haag (Jira)

[ https://issues.redhat.com/browse/WFLY-13918?page=com.atlassian.jira.plugi... ] Sven Haag updated WFLY-13918: ----------------------------- Description: Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. was: Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. > Bump MicroProfile SmallRye Config to activate Variable Expansion > ---------------------------------------------------------------- > > Key: WFLY-13918 > URL: https://issues.redhat.com/browse/WFLY-13918 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Config > Affects Versions: 20.0.1.Final, 21.0.0.Beta1 > Reporter: Sven Haag > Assignee: Jeff Mesnil > Priority: Major > > Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Please bump to the latest (1.9.0) smallrye-config implementation. > See: [https://github.com/smallrye/smallrye-config/releases] > > Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13918) Bump MicroProfile-Config smallrye-config (to 1.9.0)

by Sven Haag (Jira)

[ https://issues.redhat.com/browse/WFLY-13918?page=com.atlassian.jira.plugi... ] Sven Haag updated WFLY-13918: ----------------------------- Description: Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. was: Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] > Bump MicroProfile-Config smallrye-config (to 1.9.0) > --------------------------------------------------- > > Key: WFLY-13918 > URL: https://issues.redhat.com/browse/WFLY-13918 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Config > Affects Versions: 20.0.1.Final, 21.0.0.Beta1 > Reporter: Sven Haag > Assignee: Jeff Mesnil > Priority: Major > > Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. > See: [https://github.com/smallrye/smallrye-config/releases] > > Adapt [https://github.com/wildfly/wildfly/blob/20.0.1.Final/microprofile/config-... to comply with [https://github.com/smallrye/smallrye-config/blob/1.9.0/implementation/src...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5146) WFLYPRT0057 message handling improvement

by Katarína Hermanová (Jira)

[ https://issues.redhat.com/browse/WFCORE-5146?page=com.atlassian.jira.plug... ] Katarína Hermanová updated WFCORE-5146: --------------------------------------- Description: WFLYPRT0057 message may or may not be output. This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_). {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java} 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable { --- snip --- 135 @Override 136 public Cancellable cancel() { 137 if (cancellable && cancelled.compareAndSet(false, true)) { 138 final Thread thread = this.thread; 139 if(thread != null) { 140 thread.interrupt(); 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread); 142 } 143 } 144 return this; 145 } --- snip --- 152 @Override 153 public void run() { 154 if (cancellable && cancelled.get()) { 155 Thread.currentThread().interrupt(); 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName()); 157 } 158 this.thread = Thread.currentThread(); 159 try { 160 doExecute(); 161 } finally { 162 this.thread = null; 163 } 164 } {code} The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_). This is just a timing, we cannot determine the need for this message. {noformat} - Thread dump "management task-2" #139 prio=5 os_prio=0 tid=0x0000562c38351800 nid=0x3626 at breakpoint[0x00007facf3098000] java.lang.Thread.State: RUNNABLE at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.cancel(ManagementRequestContextImpl.java:141) at org.jboss.as.protocol.mgmt.ActiveOperationImpl.asyncCancel(ActiveOperationImpl.java:150) at org.jboss.as.protocol.mgmt.AbstractMessageHandler.cancelAllActiveOperations(AbstractMessageHandler.java:441) at org.jboss.as.protocol.mgmt.AbstractMessageHandler.shutdownNow(AbstractMessageHandler.java:150) at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:181) at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:178) at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50) at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520) at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425) at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286) at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508) at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:150) at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:129) at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:273) at org.jboss.remoting3.remote.RemoteConnectionChannel$$Lambda$737/243506564.run(Unknown Source) at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) at org.jboss.remoting3.EndpointImpl$TrackingExecutor$$Lambda$720/801134859.run(Unknown Source) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) "management-handler-thread - 3" #145 prio=5 os_prio=0 tid=0x0000562c38d5b000 nid=0x3b80 at breakpoint[0x00007facf416f000] java.lang.Thread.State: RUNNABLE at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:162) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:485) - log 09:45:24,686 INFO [org.jboss.as.protocol] (management task-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 3,5,management-handler-thread]{noformat} was: WFLYPRT0057 message may or may not be output. This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_). {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java} 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable { --- snip --- 135 @Override 136 public Cancellable cancel() { 137 if (cancellable && cancelled.compareAndSet(false, true)) { 138 final Thread thread = this.thread; 139 if(thread != null) { 140 thread.interrupt(); 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread); 142 } 143 } 144 return this; 145 } --- snip --- 152 @Override 153 public void run() { 154 if (cancellable && cancelled.get()) { 155 Thread.currentThread().interrupt(); 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName()); 157 } 158 this.thread = Thread.currentThread(); 159 try { 160 doExecute(); 161 } finally { 162 this.thread = null; 163 } 164 } {code} The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_). This is just a timing, we cannot determine the need for this message. > WFLYPRT0057 message handling improvement > ---------------------------------------- > > Key: WFCORE-5146 > URL: https://issues.redhat.com/browse/WFCORE-5146 > Project: WildFly Core > Issue Type: Enhancement > Components: CLI, Management, Remoting > Reporter: Katarína Hermanová > Assignee: Katarína Hermanová > Priority: Major > > WFLYPRT0057 message may or may not be output. > This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_). > {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java} > 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable { > --- snip --- > 135 @Override > 136 public Cancellable cancel() { > 137 if (cancellable && cancelled.compareAndSet(false, true)) { > 138 final Thread thread = this.thread; > 139 if(thread != null) { > 140 thread.interrupt(); > 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread); > 142 } > 143 } > 144 return this; > 145 } > --- snip --- > 152 @Override > 153 public void run() { > 154 if (cancellable && cancelled.get()) { > 155 Thread.currentThread().interrupt(); > 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName()); > 157 } > 158 this.thread = Thread.currentThread(); > 159 try { > 160 doExecute(); > 161 } finally { > 162 this.thread = null; > 163 } > 164 } > {code} > The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_). > This is just a timing, we cannot determine the need for this message. > {noformat} > - Thread dump > "management task-2" #139 prio=5 os_prio=0 tid=0x0000562c38351800 nid=0x3626 at breakpoint[0x00007facf3098000] > java.lang.Thread.State: RUNNABLE > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.cancel(ManagementRequestContextImpl.java:141) > at org.jboss.as.protocol.mgmt.ActiveOperationImpl.asyncCancel(ActiveOperationImpl.java:150) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler.cancelAllActiveOperations(AbstractMessageHandler.java:441) > at org.jboss.as.protocol.mgmt.AbstractMessageHandler.shutdownNow(AbstractMessageHandler.java:150) > at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:181) > at org.jboss.as.remoting.AbstractChannelOpenListenerService$2.handleClose(AbstractChannelOpenListenerService.java:178) > at org.jboss.remoting3.spi.SpiUtils.safeHandleClose(SpiUtils.java:50) > at org.jboss.remoting3.spi.AbstractHandleableCloseable$CloseHandlerTask.run(AbstractHandleableCloseable.java:520) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.runCloseTask(AbstractHandleableCloseable.java:425) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.closeComplete(AbstractHandleableCloseable.java:286) > at org.jboss.remoting3.remote.RemoteConnectionChannel.closeAction(RemoteConnectionChannel.java:508) > at org.jboss.remoting3.spi.AbstractHandleableCloseable.close(AbstractHandleableCloseable.java:150) > at org.jboss.as.protocol.mgmt.ManagementChannelReceiver.handleEnd(ManagementChannelReceiver.java:129) > at org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$notifyEnd$0(RemoteConnectionChannel.java:273) > at org.jboss.remoting3.remote.RemoteConnectionChannel$$Lambda$737/243506564.run(Unknown Source) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.remoting3.EndpointImpl$TrackingExecutor$$Lambda$720/801134859.run(Unknown Source) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > "management-handler-thread - 3" #145 prio=5 os_prio=0 tid=0x0000562c38d5b000 nid=0x3b80 at breakpoint[0x00007facf416f000] > java.lang.Thread.State: RUNNABLE > at org.jboss.as.protocol.mgmt.ManagementRequestContextImpl$AsyncTaskRunner.run(ManagementRequestContextImpl.java:162) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > - log > 09:45:24,686 INFO [org.jboss.as.protocol] (management task-2) WFLYPRT0057: cancelled task by interrupting thread Thread[management-handler-thread - 3,5,management-handler-thread]{noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13918) Bump MicroProfile-Config smallrye-config (to 1.9.0)

by Sven Haag (Jira)

[ https://issues.redhat.com/browse/WFLY-13918?page=com.atlassian.jira.plugi... ] Sven Haag updated WFLY-13918: ----------------------------- Description: Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] was: Currently there is smallrye-config 1.6.5 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] > Bump MicroProfile-Config smallrye-config (to 1.9.0) > --------------------------------------------------- > > Key: WFLY-13918 > URL: https://issues.redhat.com/browse/WFLY-13918 > Project: WildFly > Issue Type: Component Upgrade > Components: MP Config > Affects Versions: 20.0.1.Final, 21.0.0.Beta1 > Reporter: Sven Haag > Assignee: Jeff Mesnil > Priority: Major > > Currently there is smallrye-config 1.6.2 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. > See: [https://github.com/smallrye/smallrye-config/releases] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13918) Bump MicroProfile-Config smallrye-config (to 1.9.0)

by Sven Haag (Jira)

Sven Haag created WFLY-13918: -------------------------------- Summary: Bump MicroProfile-Config smallrye-config (to 1.9.0) Key: WFLY-13918 URL: https://issues.redhat.com/browse/WFLY-13918 Project: WildFly Issue Type: Component Upgrade Components: MP Config Affects Versions: 21.0.0.Beta1, 20.0.1.Final Reporter: Sven Haag Assignee: Jeff Mesnil Currently there is smallrye-config 1.6.5 which does not contain the highly appreciated feature of variable expansion. Also a CVE related to snakeyaml is present in the old version. Please bump to the latest (1.9.0) smallrye-config implementation. See: [https://github.com/smallrye/smallrye-config/releases] -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5146) WFLYPRT0057 message handling improvement

by Katarína Hermanová (Jira)

Katarína Hermanová created WFCORE-5146: ------------------------------------------ Summary: WFLYPRT0057 message handling improvement Key: WFCORE-5146 URL: https://issues.redhat.com/browse/WFCORE-5146 Project: WildFly Core Issue Type: Enhancement Components: CLI, Management, Remoting Reporter: Katarína Hermanová Assignee: Katarína Hermanová WFLYPRT0057 message may or may not be output. This message is output if an AsyncTaskRunner runable thread is not null(_ManagementRequestContextImpl.java:139_). {code:java|title=org/jboss.as/protocol/mgmt/ManagementRequestContextImpl.java} 126 private abstract static class AsyncTaskRunner implements Runnable, Cancellable { --- snip --- 135 @Override 136 public Cancellable cancel() { 137 if (cancellable && cancelled.compareAndSet(false, true)) { 138 final Thread thread = this.thread; 139 if(thread != null) { 140 thread.interrupt(); 141 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTask(getClass().getSimpleName(), thread); 142 } 143 } 144 return this; 145 } --- snip --- 152 @Override 153 public void run() { 154 if (cancellable && cancelled.get()) { 155 Thread.currentThread().interrupt(); 156 ProtocolLogger.ROOT_LOGGER.cancelledAsyncTaskBeforeRun(getClass().getSimpleName()); 157 } 158 this.thread = Thread.currentThread(); 159 try { 160 doExecute(); 161 } finally { 162 this.thread = null; 163 } 164 } {code} The process is working on multi thread, so the WFLYPRT0057 message is output by race condition of null thread handling(_ManagementRequestContextImpl.java:162_). This is just a timing, we cannot determine the need for this message. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10948) Update MyFaces to 2.3.6 in jsf-installer

by erick leal (Jira)

[ https://issues.redhat.com/browse/WFLY-10948?page=com.atlassian.jira.plugi... ] erick leal closed WFLY-10948. ----------------------------- Fix Version/s: 21.0.0.Final Resolution: Done > Update MyFaces to 2.3.6 in jsf-installer > ---------------------------------------- > > Key: WFLY-10948 > URL: https://issues.redhat.com/browse/WFLY-10948 > Project: WildFly > Issue Type: Component Upgrade > Components: JSF > Reporter: erick leal > Assignee: Farah Juma > Priority: Major > Fix For: 21.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2505) DNS_PING: support comma-separated list in the dns_query field

by Savitha Ganapathi (Jira)

[ https://issues.redhat.com/browse/JGRP-2505?page=com.atlassian.jira.plugin... ] Savitha Ganapathi updated JGRP-2505: ------------------------------------ Git Pull Request: https://github.com/belaban/JGroups/pull/513 > DNS_PING: support comma-separated list in the dns_query field > ------------------------------------------------------------- > > Key: JGRP-2505 > URL: https://issues.redhat.com/browse/JGRP-2505 > Project: JGroups > Issue Type: Enhancement > Affects Versions: 5.0.0.Final > Reporter: Savitha Ganapathi > Assignee: Bela Ban > Priority: Major > > In multi-region deployments, it'd be useful to combine addresses from multiple DNS queries to form the cluster. A simple change would be to make the "dns_query" parameter a comma-separated list of queries as opposed to a single query like it is currently. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 12 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira September 2020