October 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-352) Release WildFly Elytron 1.1.0.Beta1

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-352: ------------------------------------ Summary: Release WildFly Elytron 1.1.0.Beta1 Key: ELY-352 URL: https://issues.jboss.org/browse/ELY-352 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.1.0.Beta1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-339) CredentialStorage API/SPI

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-339?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse updated ELY-339: --------------------------------- Fix Version/s: 1.1.0.Alpha2 (was: 1.1.0.Beta1) > CredentialStorage API/SPI > ------------------------- > > Key: ELY-339 > URL: https://issues.jboss.org/browse/ELY-339 > Project: WildFly Elytron > Issue Type: Sub-task > Components: API / SPI > Reporter: Peter Skopek > Assignee: Peter Skopek > Fix For: 1.1.0.Alpha2 > > > Create CredentialStorage API/SPI. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-327) CredentialMapper needs to be associated with SecurityDomain and SecurityRealm

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-327?page=com.atlassian.jira.plugin.sy... ] Darran Lofthouse resolved ELY-327. ---------------------------------- Resolution: Out of Date > CredentialMapper needs to be associated with SecurityDomain and SecurityRealm > ----------------------------------------------------------------------------- > > Key: ELY-327 > URL: https://issues.jboss.org/browse/ELY-327 > Project: WildFly Elytron > Issue Type: Enhancement > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: David Lloyd > Fix For: 1.1.0.Alpha2 > > > If associated with security realm this takes priority over security domain association which is fallback impl -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5555) JMS Bridge ambiguous error reporting on module load failure

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-5555?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-5555: ------------------------------ Affects Version/s: 10.0.0.CR4 > JMS Bridge ambiguous error reporting on module load failure > ------------------------------------------------------------ > > Key: WFLY-5555 > URL: https://issues.jboss.org/browse/WFLY-5555 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR4 > Reporter: Bartosz Baranowski > Assignee: Jeff Mesnil > Priority: Minor > > If JMS bridge depends on module that for some reason cant be loaded, log will show cryptic message: > 10:21:26,173 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("jms-bridge" => "a-to-c-bridge") > ]) - failure description: "org.hornetq:main" > 1. Failure description does not describe a thing > 2. it points to HQ module, rather than custom module used in bridge conf. > Exception is thrown at JMSBridgeAdd:155 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5600) List of nodes taken from org.wildfly.clustering.group.Group is different across nodes

by Piotr Nowicki (JIRA)

Piotr Nowicki created WFLY-5600: ----------------------------------- Summary: List of nodes taken from org.wildfly.clustering.group.Group is different across nodes Key: WFLY-5600 URL: https://issues.jboss.org/browse/WFLY-5600 Project: WildFly Issue Type: Bug Components: Clustering, EE, EJB Affects Versions: 9.0.1.Final Environment: Windows 7 64 bit, JDK 1.8_20 64bit Reporter: Piotr Nowicki Assignee: Paul Ferraro I have a cluster of 2 nodes with a WAR application deployed using web-console and exposing EJB remote business interface with following content: {code}@Stateless @Remote public class ServiceImplementation implements Service { @Resource( lookup = "java:jboss/clustering/group/ejb" ) private Group channelGroup; @Override public void printNodeList() { for( Node node : channelGroup.getNodes()) { System.out.println( "node = " + node ); } } } {code} I invoke this EJB from a standalone client multiple times (to make sure that method calls will reach both nodes.) The result is different on both nodes: * On master node the result is *correct* = two nodes' names are printed out , * On second node the result is *incorrect* = *no nodes' names are printed out*. This was working fine in WFLY 8.2.0.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5536) Recovery manager is not able to recover MDB and shows warnings on each run.

by Andy Taylor (JIRA)

[ https://issues.jboss.org/browse/WFLY-5536?page=com.atlassian.jira.plugin.... ] Andy Taylor commented on WFLY-5536: ----------------------------------- [~hhovsepy] I have managed to run the test however I need to attach a debugger to the server orchestrating the recovery, could you provide details as to how to do this, ive tried updating the arquillian config but this is ignored. > Recovery manager is not able to recover MDB and shows warnings on each run. > --------------------------------------------------------------------------- > > Key: WFLY-5536 > URL: https://issues.jboss.org/browse/WFLY-5536 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.CR2 > Reporter: Hayk Hovsepyan > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: MDB_JMS_XA.log > > > Recovery manager is not able to recover MDB and shows warnings. > This causes to see the same warning log in server each time recovery is run. > This happens when server is crashed before transaction state is saved. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5598) Update to HAL 2.8.14.Final

by Heiko Braun (JIRA)

[ https://issues.jboss.org/browse/WFLY-5598?page=com.atlassian.jira.plugin.... ] Heiko Braun commented on WFLY-5598: ----------------------------------- Includes the updated picketlink user interface. > Update to HAL 2.8.14.Final > -------------------------- > > Key: WFLY-5598 > URL: https://issues.jboss.org/browse/WFLY-5598 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Console > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: 10.0.0.Final > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5599) Allow existing security domains to be exposed as Elytron SecurityRealms

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-5599: -------------------------------------- Summary: Allow existing security domains to be exposed as Elytron SecurityRealms Key: WFLY-5599 URL: https://issues.jboss.org/browse/WFLY-5599 Project: WildFly Issue Type: Enhancement Components: Security Reporter: Darran Lofthouse Assignee: Stefan Guilhen Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5555) JMS Bridge ambiguous error reporting on module load failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5555?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-5555: ----------------------------------- Component/s: JMS > JMS Bridge ambiguous error reporting on module load failure > ------------------------------------------------------------ > > Key: WFLY-5555 > URL: https://issues.jboss.org/browse/WFLY-5555 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: Jason Greene > Priority: Minor > > If JMS bridge depends on module that for some reason cant be loaded, log will show cryptic message: > 10:21:26,173 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("jms-bridge" => "a-to-c-bridge") > ]) - failure description: "org.hornetq:main" > 1. Failure description does not describe a thing > 2. it points to HQ module, rather than custom module used in bridge conf. > Exception is thrown at JMSBridgeAdd:155 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5555) JMS Bridge ambiguous error reporting on module load failure

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-5555?page=com.atlassian.jira.plugin.... ] Brian Stansberry reassigned WFLY-5555: -------------------------------------- Assignee: Jeff Mesnil (was: Jason Greene) > JMS Bridge ambiguous error reporting on module load failure > ------------------------------------------------------------ > > Key: WFLY-5555 > URL: https://issues.jboss.org/browse/WFLY-5555 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Bartosz Baranowski > Assignee: Jeff Mesnil > Priority: Minor > > If JMS bridge depends on module that for some reason cant be loaded, log will show cryptic message: > 10:21:26,173 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 51) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("jms-bridge" => "a-to-c-bridge") > ]) - failure description: "org.hornetq:main" > 1. Failure description does not describe a thing > 2. it points to HQ module, rather than custom module used in bridge conf. > Exception is thrown at JMSBridgeAdd:155 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 8 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