[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8304:
---------------------------------
Priority: Minor (was: Major)
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Priority: Minor
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8304:
---------------------------------
Labels: (was: mod_cluster)
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Priority: Minor
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar updated WFLY-8304:
---------------------------------
Component/s: mod_cluster
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Priority: Minor
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8305) Exclude org.ow2.asm:asm from bld.
by R Searls (JIRA)
R Searls created WFLY-8305:
------------------------------
Summary: Exclude org.ow2.asm:asm from bld.
Key: WFLY-8305
URL: https://issues.jboss.org/browse/WFLY-8305
Project: WildFly
Issue Type: Task
Components: Web Services
Affects Versions: 11.0.0.Alpha1
Reporter: R Searls
Assignee: R Searls
Priority: Minor
With the update to woodstox to 5.x archive org.ow2.asm is obsolete but is still pulled in. Add excludes as needed in the pom's to remove.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar moved UNDERTOW-983 to WFLY-8304:
-----------------------------------------------
Project: WildFly (was: Undertow)
Key: WFLY-8304 (was: UNDERTOW-983)
Affects Version/s: 10.1.0.Final
(was: 1.4.8.Final)
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar commented on WFLY-8304:
--------------------------------------
This is a WFLY problem, not UNDERTOW one.
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFLY-8304) Max-attempts minimal value
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/WFLY-8304?page=com.atlassian.jira.plugin.... ]
Radoslav Husar edited comment on WFLY-8304 at 3/6/17 3:21 PM:
--------------------------------------------------------------
This is a WFLY problem, not UNDERTOW one; moved.
was (Author: rhusar):
This is a WFLY problem, not UNDERTOW one.
> Max-attempts minimal value
> --------------------------
>
> Key: WFLY-8304
> URL: https://issues.jboss.org/browse/WFLY-8304
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Bogdan Sikora
> Assignee: Radoslav Husar
> Labels: mod_cluster
>
> [Documentation|http://modcluster.io/documentation/#proxy-configuration-1]
> {noformat}
> Maximum number of failover attempts before giving up. The minimum value is 0, i.e. no failover. The default value is 1, i.e. do a one failover attempt.
> {noformat}
> Max-attemps minimal value is
> {noformat}
> "max-attempts" => {
> "type" => INT,
> "description" => "Max attempts to process an idempotent request.",
> "expressions-allowed" => true,
> "nillable" => true,
> "default" => 1,
> "min" => -1L,
> "max" => 2147483647L,
> "access-type" => "read-write",
> "storage" => "configuration",
> "restart-required" => "all-services"
> },
> {noformat}
> Min value to 0. In the mod_cluster subsystem(worker side).
> And max-attemps handling on the balancer side. Balancer has minimal value of 1 and therefore any value lower than that is ignored. Should be 0.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-1802) Ensure OpenSSL Registration if first.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ]
Darran Lofthouse edited comment on WFCORE-1802 at 3/6/17 1:51 PM:
------------------------------------------------------------------
[~swd847] I am trying to ensure wildfly-openssl is registered first so we can use it if available and fallback if not: -
https://github.com/darranl/wildfly-core/tree/WFCORE-1802
However I am running into a NPE within the 'org.jboss.as.test.integration.auditlog.AuditLogToTLSSyslogTestCase' test case.
{{
Caused by: java.lang.NullPointerException
at org.wildfly.openssl.OpenSSLSocket.connect(OpenSSLSocket.java:547)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:244)
at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:196)
at org.wildfly.openssl.OpenSSLSocket.<init>(OpenSSLSocket.java:83)
at org.wildfly.openssl.OpenSSLContextSPI$1.createSocket(OpenSSLContextSPI.java:359)
at org.jboss.as.controller.audit.SyslogAuditLogHandler$SSLContextOutputStream.<init>(SyslogAuditLogHandler.java:480)
at org.jboss.as.controller.audit.SyslogAuditLogHandler.initialize(SyslogAuditLogHandler.java:273)
... 31 more
}}
was (Author: dlofthouse):
[~swd847] I am trying to ensure wildfly-openssl is registered first so we can use it if available and fallback if not: -
https://github.com/darranl/wildfly-core/tree/WFCORE-1802
However I am running into a NPE within the 'org.jboss.as.test.integration.auditlog.AuditLogToTLSSyslogTestCase' test case.
{{Caused by: java.lang.NullPointerException
at org.wildfly.openssl.OpenSSLSocket.connect(OpenSSLSocket.java:547)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:244)
at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:196)
at org.wildfly.openssl.OpenSSLSocket.<init>(OpenSSLSocket.java:83)
at org.wildfly.openssl.OpenSSLContextSPI$1.createSocket(OpenSSLContextSPI.java:359)
at org.jboss.as.controller.audit.SyslogAuditLogHandler$SSLContextOutputStream.<init>(SyslogAuditLogHandler.java:480)
at org.jboss.as.controller.audit.SyslogAuditLogHandler.initialize(SyslogAuditLogHandler.java:273)
... 31 more}}
> Ensure OpenSSL Registration if first.
> -------------------------------------
>
> Key: WFCORE-1802
> URL: https://issues.jboss.org/browse/WFCORE-1802
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Stuart Douglas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta8
>
>
> The following in SecurityRealmResourceDefinition registers the provider: -
> {code}
> static {
> //register the Openssl Provider, if possible
> //not really sure if this is the best place for it
> try {
> OpenSSLProvider.register();
> DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
> } catch (Throwable t){
> DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
> }
> }
> {code}
> It would be good to remove this however for now we can't guarantee Elytron is enabled so register it globally.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-1802) Ensure OpenSSL Registration if first.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ]
Darran Lofthouse commented on WFCORE-1802:
------------------------------------------
[~swd847] I am trying to ensure wildfly-openssl is registered first so we can use it if available and fallback if not: -
https://github.com/darranl/wildfly-core/tree/WFCORE-1802
However I am running into a NPE within the 'org.jboss.as.test.integration.auditlog.AuditLogToTLSSyslogTestCase' test case.
{{Caused by: java.lang.NullPointerException
at org.wildfly.openssl.OpenSSLSocket.connect(OpenSSLSocket.java:547)
at java.net.Socket.<init>(Socket.java:434)
at java.net.Socket.<init>(Socket.java:244)
at javax.net.ssl.SSLSocket.<init>(SSLSocket.java:196)
at org.wildfly.openssl.OpenSSLSocket.<init>(OpenSSLSocket.java:83)
at org.wildfly.openssl.OpenSSLContextSPI$1.createSocket(OpenSSLContextSPI.java:359)
at org.jboss.as.controller.audit.SyslogAuditLogHandler$SSLContextOutputStream.<init>(SyslogAuditLogHandler.java:480)
at org.jboss.as.controller.audit.SyslogAuditLogHandler.initialize(SyslogAuditLogHandler.java:273)
... 31 more}}
> Ensure OpenSSL Registration if first.
> -------------------------------------
>
> Key: WFCORE-1802
> URL: https://issues.jboss.org/browse/WFCORE-1802
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Stuart Douglas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta8
>
>
> The following in SecurityRealmResourceDefinition registers the provider: -
> {code}
> static {
> //register the Openssl Provider, if possible
> //not really sure if this is the best place for it
> try {
> OpenSSLProvider.register();
> DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
> } catch (Throwable t){
> DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
> }
> }
> {code}
> It would be good to remove this however for now we can't guarantee Elytron is enabled so register it globally.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (WFCORE-1802) Ensure OpenSSL Registration if first.
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/WFCORE-1802?page=com.atlassian.jira.plugi... ]
Darran Lofthouse updated WFCORE-1802:
-------------------------------------
Description:
The following in SecurityRealmResourceDefinition registers the provider: -
{code}
static {
//register the Openssl Provider, if possible
//not really sure if this is the best place for it
try {
OpenSSLProvider.register();
DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
} catch (Throwable t){
DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
}
}
{code}
It would be good to remove this however for now we can't guarantee Elytron is enabled so register it globally.
was:
We need to remove the following block from SecurityRealmResourceDefinition: -
{code}
static {
//register the Openssl Provider, if possible
//not really sure if this is the best place for it
try {
OpenSSLProvider.register();
DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
} catch (Throwable t){
DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
}
}
{code}
Registration will then be possible within the Elytron subsystem configuration.
> Ensure OpenSSL Registration if first.
> -------------------------------------
>
> Key: WFCORE-1802
> URL: https://issues.jboss.org/browse/WFCORE-1802
> Project: WildFly Core
> Issue Type: Task
> Components: Security
> Reporter: Stuart Douglas
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 3.0.0.Beta8
>
>
> The following in SecurityRealmResourceDefinition registers the provider: -
> {code}
> static {
> //register the Openssl Provider, if possible
> //not really sure if this is the best place for it
> try {
> OpenSSLProvider.register();
> DomainManagementLogger.ROOT_LOGGER.registeredOpenSSLProvider();
> } catch (Throwable t){
> DomainManagementLogger.ROOT_LOGGER.debugf(t, "Failed to register OpenSSL provider");
> }
> }
> {code}
> It would be good to remove this however for now we can't guarantee Elytron is enabled so register it globally.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months