October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-338) Mechanism realm awareness

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/ELY-338?page=com.atlassian.jira.plugin.sy... ] David Lloyd updated ELY-338: ---------------------------- Priority: Critical (was: Major) > Mechanism realm awareness > ------------------------- > > Key: ELY-338 > URL: https://issues.jboss.org/browse/ELY-338 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI, Authentication Mechanisms > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Critical > > Add support for mechanisms that allow selection from a set of realms. Provide reasonable fallback behavior when a mechanism does not allow realm selection, or for when the presented realm name is informational only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-338) Mechanism realm awareness

by David Lloyd (JIRA)

David Lloyd created ELY-338: ------------------------------- Summary: Mechanism realm awareness Key: ELY-338 URL: https://issues.jboss.org/browse/ELY-338 Project: WildFly Elytron Issue Type: Enhancement Components: API / SPI, Authentication Mechanisms Reporter: David Lloyd Assignee: David Lloyd Add support for mechanisms that allow selection from a set of realms. Provide reasonable fallback behavior when a mechanism does not allow realm selection, or for when the presented realm name is informational only. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-248) Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-248?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse reopened ELY-248: ---------------------------------- > Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set > ---------------------------------------------------------------------------------------------------- > > Key: ELY-248 > URL: https://issues.jboss.org/browse/ELY-248 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.0.0.Alpha2 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Alpha3 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-248) Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-248?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-248. ---------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Alpha3) Resolution: Out of Date > Inconsistent behavior in FileSystemRealm when verifying credentials and multiple credentials are set > ---------------------------------------------------------------------------------------------------- > > Key: ELY-248 > URL: https://issues.jboss.org/browse/ELY-248 > Project: WildFly Elytron > Issue Type: Bug > Components: Realms > Affects Versions: 1.0.0.Alpha2 > Reporter: Pedro Igor > Assignee: Pedro Igor > Fix For: 1.1.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1298) Misleading error code in case of missing depencencies

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1298?page=com.atlassian.jira.plugin... ] Jesper Pedersen closed JBJCA-1298. ---------------------------------- Resolution: Incomplete Description > Misleading error code in case of missing depencencies > ----------------------------------------------------- > > Key: JBJCA-1298 > URL: https://issues.jboss.org/browse/JBJCA-1298 > Project: IronJacamar > Issue Type: Bug > Components: Deployer > Affects Versions: 1.2.4.Final > Environment: Wildfly 9.0.1 / Windows 7 > Reporter: Ralf Battenfeld > Assignee: Jesper Pedersen > > Hi > I was more than a day analyzing an error reported by the resource adapter deployer saying that the class XXX has to implement the hashCode() and equals() method. At the end, it was a missing dependency in the rar archive. > I don't know if this bug is already fixed. If not then it really appreciated if you can fix this. At least, write this particular statement when you really have detected missing methods. I am sure that I am not the first one who faced this bug. I also looked at the specific code and think the extremely long method needs to be refactored. > Tx, > Ralf -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1293) Broken Links on JBoss.org & developers.redhat.com

by Jesper Pedersen (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1293?page=com.atlassian.jira.plugin... ] Jesper Pedersen closed JBJCA-1293. ---------------------------------- Resolution: Cannot Reproduce Bug There is no fisheye in http://www.ironjacamar.org/project.properties > Broken Links on JBoss.org & developers.redhat.com > ------------------------------------------------- > > Key: JBJCA-1293 > URL: https://issues.jboss.org/browse/JBJCA-1293 > Project: IronJacamar > Issue Type: Bug > Reporter: Daniel Coughlin > Assignee: Jesper Pedersen > > The following broken link is currently listed against this project on developers.redhat.com/projects. > http://fisheye.jboss.com/browse/JBossAS/projects/jboss-jca/trunk/ > If you maintain a project.properties file that you have told the RHD team about, then you just need to fix it in there and the change will be reflected on the site. Otherwise, you need to update the data on this project's Magnolia page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBASMP-71) JBoss Maven Plugin fails deploy in domain mode if one server is stopped

by Filippe Spolti (JIRA)

[ https://issues.jboss.org/browse/JBASMP-71?page=com.atlassian.jira.plugin.... ] Filippe Spolti reassigned JBASMP-71: ------------------------------------ Assignee: Filippe Spolti > JBoss Maven Plugin fails deploy in domain mode if one server is stopped > ----------------------------------------------------------------------- > > Key: JBASMP-71 > URL: https://issues.jboss.org/browse/JBASMP-71 > Project: JBoss AS Maven Plugins > Issue Type: Bug > Components: deploy > Affects Versions: 7.5.Final > Reporter: Jorge Solorzano > Assignee: Filippe Spolti > > I have a cluster in domain mode and configured my project to do the deploy on a server group (jboss-as:deploy), but if I have one server stopped the deploy fails. > I think it should do the deploy even if all servers are stopped, after all the master is the one who get the deploy and when the servers come back online then the master sends the content to the servers. > If I do the deploy directly from the manangement console it don't care if all servers (in the server group) are stopped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2492) <valid-connection-checker> does not have module attribute

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-2492?page=com.atlassian.jira.plugin.... ] Tom Jenkinson commented on WFLY-2492: ------------------------------------- Hi [~hsvabek], did we agree this was no longer a blocker? > <valid-connection-checker> does not have module attribute > --------------------------------------------------------- > > Key: WFLY-2492 > URL: https://issues.jboss.org/browse/WFLY-2492 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Affects Versions: 8.0.0.Beta1 > Reporter: James Livingston > Assignee: Lin Gao > Priority: Blocker > Fix For: 10.0.0.CR4 > > > A datasource's <valid-connection-checker> element lets you specify the class name. It does not let you specify the module name, so you can only use IJ-provided ones. It should let you specify a module name too, so you can use custom connection checkers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5501) JDBC Object Store problem with Mariadb55

by Tom Jenkinson (JIRA)

[ https://issues.jboss.org/browse/WFLY-5501?page=com.atlassian.jira.plugin.... ] Tom Jenkinson updated WFLY-5501: -------------------------------- Priority: Major (was: Critical) > JDBC Object Store problem with Mariadb55 > ---------------------------------------- > > Key: WFLY-5501 > URL: https://issues.jboss.org/browse/WFLY-5501 > Project: WildFly > Issue Type: Bug > Components: Transactions > Reporter: Hayk Hovsepyan > Assignee: Tom Jenkinson > Fix For: 10.0.0.CR4 > > Attachments: mariadb_jar.zip, server.log, standalone.xml > > > When configuring transactions to use Mariadb55 Datasource as a JDBC Object store, server fails to start with error: > {code} > 13:56:51,485 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.txn.ArjunaRecoveryManager" => "org.jboss.msc.service.StartException in service jboss.txn.ArjunaRecoveryManager: WFLYTX0005: Recovery manager create failed > Caused by: java.lang.NullPointerException"}} > {code} > Steps to reproduce: > 1. Create Mariadb55 JDBC driver module. Module archived directory is attached. > 2. Add driver into configuration xml. > 3. Create Datasource pointing to Mariadb55 database and using driver configured a a module. > 4. Configure transactions to use jdbc-store the added Datasource. standalone.xml is attached. > 5. Server fails to start. server.log is attached. > config xml file part: > {code} > <subsystem xmlns="urn:jboss:domain:datasources:4.0"> > <datasources> > <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true"> > <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url> > <driver>h2</driver> > <security> > <user-name>sa</user-name> > <password>sa</password> > </security> > </datasource> > <datasource jta="false" jndi-name="java:jboss/datasources/jdbc-store" pool-name="JDBCObjectStore" enabled="true" use-java-context="true"> > <connection-url>jdbc:mariadb://db22.mw.lab.eng.bos.redhat.com:3306/dballo17</connection-url> > <driver>module_mariadb.jar</driver> > <security> > <user-name>dballo17</user-name> > <password>dballo17</password> > </security> > </datasource> > <drivers> > <driver name="h2" module="com.h2database.h2"> > <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class> > </driver> > <driver name="module_mariadb.jar" module="mariadb_jar"/> > </drivers> > </datasources> > </subsystem> > <subsystem xmlns="urn:jboss:domain:transactions:3.0"> > <core-environment> > <process-id> > <uuid/> > </process-id> > </core-environment> > <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/> > <coordinator-environment enable-tsm-status="true"/> > <jdbc-store datasource-jndi-name="java:jboss/datasources/jdbc-store"/> > </subsystem> > {code} > Attached necessary info: > 1. server.log > 2. Module zip to extract in $JBOSS_HOME/modules/system/layers/base > 3. standalone.xml > Notes: > The same steps works for other databases. > When step 4. is not executed server starts successfully, so module is recognized. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-336) Tests do not establish LoginPermission

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-336?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-336: --------------------------------- Fix Version/s: 1.1.0.Final > Tests do not establish LoginPermission > -------------------------------------- > > Key: ELY-336 > URL: https://issues.jboss.org/browse/ELY-336 > Project: WildFly Elytron > Issue Type: Task > Components: Testsuite > Reporter: David Lloyd > Priority: Critical > Fix For: 1.1.0.Final > > > All users performing authentication in the test suite must be granted the LoginPermission. Without this permission, all tests performing authentications will fail when the {{identity.getPermissions().implies(new LoginPermission())}} checks are enabled in {{ServerAuthenticationContext}}. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 9 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 October 2015