March 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-1066) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-1066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant edited comment on WFLY-1066 at 3/18/16 9:58 AM: ---------------------------------------------------------------- This would be essential for Infinispan Server. Would it be possible to at least get the Core changes in ? [~bstansberry], [~jason.greene] I guess this really needs your validation since it introduces changes to the server<>host protocol was (Author: nadirx): This would be essential for Infinispan Server. Would it be possible to at least get the Core changes in ? [~bstansberry], [~jason.greene] I guess this really needs your validation since it > Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING) > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1066 > URL: https://issues.jboss.org/browse/WFLY-1066 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: Server running in Domain mode > Reporter: Wolf-Dieter Fink > Assignee: Tristan Tarrant > Labels: clustering, domain, jgroups > > It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode. > All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration. > The domain server will receive the informations if a host-controller enrol and register server to a clustered server-group. > So the configuration of the initial_hosts can be done automaticaly to avoid old entries which cause unnecessary checks and ensure that all active servers are known. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-1066) Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING)

by Tristan Tarrant (JIRA)

[ https://issues.jboss.org/browse/WFLY-1066?page=com.atlassian.jira.plugin.... ] Tristan Tarrant commented on WFLY-1066: --------------------------------------- This would be essential for Infinispan Server. Would it be possible to at least get the Core changes in ? [~bstansberry], [~jason.greene] I guess this really needs your validation since it > Automatic configuration of 'Initial_hosts' for a cluster using JGroups TCP-stack in domain mode (aka DOMAIN_PING) > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-1066 > URL: https://issues.jboss.org/browse/WFLY-1066 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Environment: Server running in Domain mode > Reporter: Wolf-Dieter Fink > Assignee: Dominik Pospisil > Labels: clustering, domain, jgroups > > It is complicated to keep the subsystem JGroups in sync if the tcp-stack is used in domain mode. > All new servers that join/leave a clustered server group (configuration) must be added or removed by hand for the jgroup configuration. > The domain server will receive the informations if a host-controller enrol and register server to a clustered server-group. > So the configuration of the initial_hosts can be done automaticaly to avoid old entries which cause unnecessary checks and ensure that all active servers are known. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-458) Attachment and resource scopes for HTTP auth API

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-458?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-458: ------------------------------------ Assignee: Darran Lofthouse > Attachment and resource scopes for HTTP auth API > ------------------------------------------------ > > Key: ELY-458 > URL: https://issues.jboss.org/browse/ELY-458 > Project: WildFly Elytron > Issue Type: Feature Request > Components: HTTP > Reporter: David Lloyd > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Add an API to provide access to attachment and resource scopes as follows: > * Exchange/Request > * Connection > * Session > * Application† > * SSL Session > * Global/JVM† > Scopes marked with † can have access to resources as well. > Scopes should also optionally support the registration of notifications so that a mechanism can be informed about the destruction of a specific scope. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-464) Update HTTP API / SPI to allow mechanisms access to resources in application.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-464: ------------------------------------ Summary: Update HTTP API / SPI to allow mechanisms access to resources in application. Key: ELY-464 URL: https://issues.jboss.org/browse/ELY-464 Project: WildFly Elytron Issue Type: Feature Request Components: HTTP Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6408) Failed to add datasource of sql server in Wildfly 9

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-6408?page=com.atlassian.jira.plugin.... ] Tomaz Cerar closed WFLY-6408. ----------------------------- Assignee: (was: Jason Greene) Resolution: Rejected This is type of discussion that belongs to user forums not bug tracker. Forums can be found at https://developer.jboss.org/en/wildfly > Failed to add datasource of sql server in Wildfly 9 > --------------------------------------------------- > > Key: WFLY-6408 > URL: https://issues.jboss.org/browse/WFLY-6408 > Project: WildFly > Issue Type: Bug > Reporter: vlad ZHANG > > Hello, > I encounter a problem in deploying datasource of sql server in Wildfly 9. > The Wildfly version I have downloaded is Wildfly 9.2.0.Final. I added a user and entered the Administrator Console in a browser. > The sql server version I have downloaded is sql server 2008. I want to deploy a datasource of sql server. > I started to download a JDBC Driver. The version I have downloaded is "Microsoft JDBC Drivers 6.0 (Preview), 4.2, 4.1, and 4.0 for SQL Server" from "https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=1...". > I succeeded in adding this driver by choosing deployment--->add--->Upload a new deployment in the Administration Console. But when I try to add a datasource, I had a problem. > In the "configuration" of Administration Console, I chose Subsystems--->Datasources--->Non-XA--->add. Then I chose the driver I had deployed. But I always cannot create this datasource, the error is always: > Failed to create JDBC connection. > An internal error occurred. > Unexpected HTTP response: 500 > Request > { > "address" => [ > ("subsystem" => "datasources"), > ("data-source" => "MSSQLDS") > ], > "operation" => "test-connection-in-pool" > } > Response > Internal Server Error > { > "outcome" => "failed", > "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", > "rolled-back" => true, > "response-headers" => {"process-state" => "reload-required"} > } > And I don't know why. Could anyone help me, please? Thank you in advance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6408) Failed to add datasource of sql server in Wildfly 9

by vlad ZHANG (JIRA)

vlad ZHANG created WFLY-6408: -------------------------------- Summary: Failed to add datasource of sql server in Wildfly 9 Key: WFLY-6408 URL: https://issues.jboss.org/browse/WFLY-6408 Project: WildFly Issue Type: Bug Reporter: vlad ZHANG Assignee: Jason Greene Hello, I encounter a problem in deploying datasource of sql server in Wildfly 9. The Wildfly version I have downloaded is Wildfly 9.2.0.Final. I added a user and entered the Administrator Console in a browser. The sql server version I have downloaded is sql server 2008. I want to deploy a datasource of sql server. I started to download a JDBC Driver. The version I have downloaded is "Microsoft JDBC Drivers 6.0 (Preview), 4.2, 4.1, and 4.0 for SQL Server" from "https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=1...". I succeeded in adding this driver by choosing deployment--->add--->Upload a new deployment in the Administration Console. But when I try to add a datasource, I had a problem. In the "configuration" of Administration Console, I chose Subsystems--->Datasources--->Non-XA--->add. Then I chose the driver I had deployed. But I always cannot create this datasource, the error is always: Failed to create JDBC connection. An internal error occurred. Unexpected HTTP response: 500 Request { "address" => [ ("subsystem" => "datasources"), ("data-source" => "MSSQLDS") ], "operation" => "test-connection-in-pool" } Response Internal Server Error { "outcome" => "failed", "failure-description" => "WFLYJCA0040: failed to invoke operation: WFLYJCA0047: Connection is not valid", "rolled-back" => true, "response-headers" => {"process-state" => "reload-required"} } And I don't know why. Could anyone help me, please? Thank you in advance. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-6406) Artemis AIO journal fails on zfsonlinux ZFS filesystem

by Dominik Pospisil (JIRA)

[ https://issues.jboss.org/browse/WFLY-6406?page=com.atlassian.jira.plugin.... ] Dominik Pospisil commented on WFLY-6406: ---------------------------------------- It turns out that zfsonlinux does support Async IO since 6.4 but it does not support direct io (O_DIRECT) yet. According to libaio docs, it requires O_DIRECT. Maybe the AIOSequentialFileFactory.isSupported() should be enhanced to perform some more thorough check than just checking if native lib was loaded as it does as of now. > Artemis AIO journal fails on zfsonlinux ZFS filesystem > ------------------------------------------------------ > > Key: WFLY-6406 > URL: https://issues.jboss.org/browse/WFLY-6406 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.1.0.Final > Reporter: Dominik Pospisil > Assignee: Dominik Pospisil > > Artemis AIO journal fails on zfsonlinux ZFS filesystem. According to zfsonlinux docs libaio should be supported. > I guess that the initialization should work or failback to NIO. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-463) Update verifyEvidence to attempt to use the Principal from the evidence if possible and if the name has not already been set.

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-463: ------------------------------------ Summary: Update verifyEvidence to attempt to use the Principal from the evidence if possible and if the name has not already been set. Key: ELY-463 URL: https://issues.jboss.org/browse/ELY-463 Project: WildFly Elytron Issue Type: Feature Request Components: API / SPI Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta5 This is effectively pulling the steps from SecurityDomainTrustManager to ServerAuthenticationContext and instead of using an EvidenceDecoder just attempt to obtain the Principal from the evidence. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-450) Drop EvidenceDecoder

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-450?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reassigned ELY-450: ------------------------------------ Assignee: Darran Lofthouse > Drop EvidenceDecoder > -------------------- > > Key: ELY-450 > URL: https://issues.jboss.org/browse/ELY-450 > Project: WildFly Elytron > Issue Type: Feature Request > Components: SSL > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > Drop the EvidenceDecoder as it is only used by SecurityDomainTrustManager. > Instead Evidence will have a getPrincipal method which will by default return null, when verifyEvidence is called this can be used to set the current principal / trigger name rewriters / principal decoders etc... Then verifyEvidence can call itself / continue. > Where no Principal is returned the current iterate the realms approach can be used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-141) Add a Credential to Name Resolver SPI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-141?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-141. ---------------------------------- Resolution: Won't Fix We have decided to enhance the Evidence API to optionally make a Principal available, PrincipalDecoders and NameRewriters will then take over the rest. > Add a Credential to Name Resolver SPI > ------------------------------------- > > Key: ELY-141 > URL: https://issues.jboss.org/browse/ELY-141 > Project: WildFly Elytron > Issue Type: Feature Request > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.1.0.Beta5 > > > We are predominantly considering this in the context of the validation side of the API. > However should still not exclude the possibility that after obtaining a RealmIdentity the validation may still be performed in the mechanism. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016