January 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2177) Remove the 'elytron' supplement from the Remoting subsystem.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFCORE-2177: ---------------------------------------- Summary: Remove the 'elytron' supplement from the Remoting subsystem. Key: WFCORE-2177 URL: https://issues.jboss.org/browse/WFCORE-2177 Project: WildFly Core Issue Type: Task Components: Remoting Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 3.0.0.Alpha18 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (ELY-864) Compatibility with Picketbox SecurityVaultData

by Zoran Regvart (JIRA)

Zoran Regvart created ELY-864: --------------------------------- Summary: Compatibility with Picketbox SecurityVaultData Key: ELY-864 URL: https://issues.jboss.org/browse/ELY-864 Project: WildFly Elytron Issue Type: Bug Components: Credential Store Affects Versions: 1.1.0.Beta19 Reporter: Zoran Regvart Assignee: Peter Skopek Priority: Minor As per [Java Object Serialization Specification 6.0 chapter 3.1|https://docs.oracle.com/javase/8/docs/platform/serialization/spec/inp...], a substitution of class from serialized form can occur only if both classes have the same `serialVersionUID` and class name (package name can differ). Otherwise `java.io.InvalidClassException` is thrown. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2176) ProcessStateListener execution isn't cancelled when timeout is reached

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2176?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet moved JBEAP-8194 to WFCORE-2176: -------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2176 (was: JBEAP-8194) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: Domain Management) Affects Version/s: 3.0.0.Alpha16 (was: 7.1.0.DR10) > ProcessStateListener execution isn't cancelled when timeout is reached > ---------------------------------------------------------------------- > > Key: WFCORE-2176 > URL: https://issues.jboss.org/browse/WFCORE-2176 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.0.Alpha16 > Reporter: ehsavoie Hugonnet > Assignee: ehsavoie Hugonnet > > [Analysis document|https://developer.jboss.org/wiki/DevAnalysisForListenerForLifecy...] for listener for lifecycle server events says that there is management attribute {{timeout}} which is described: > {quote} > timeout - a timeout in seconds before cancelling the execution of the listener. > {quote} > But execution of {{runtimeConfigurationStateChanged}} and {{runningStateChanged}} methods isn't cancelled when timeout is reached. {{java.util.concurrent.TimeoutException}} is correctly logged. > It seems to me that [ProcessStateListenerService.java#L176|https://github.com/wildfly/wildfly-...] needs to cancel {{Future}} in {{TimeoutException}} catch block -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7871) Decouple backup/site name from the name of the corresponding resource

by Paul Ferraro (JIRA)

Paul Ferraro created WFLY-7871: ---------------------------------- Summary: Decouple backup/site name from the name of the corresponding resource Key: WFLY-7871 URL: https://issues.jboss.org/browse/WFLY-7871 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 10.1.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Fix For: 11.0.0.Beta1 Currently, the site names defined in the JGroups subsystem RELAY2 protocol, and the backup names defined in the Infinispan subsystem do not allow expressions, since these name are used for the corresponding resource paths. To simplify the use of cross-site replication (specifically, to allow each site to use an identical domain.xml/standalone.xml), we can support expressions if we decouple the site name from the resource name. e.g. <backups> <backup name="remote" site="${...}" strategy="SYNC"/> </backups> <relay site="local"> <remote-site name="local" site-name="${...}" channel=".."/> <remote-site name="remote" site-name="${...}" channel=".."/> </relay> -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7870) Remove the -elytron.xml configurations and add the Elytron subsystem to the default configuration.

by Darran Lofthouse (JIRA)

Darran Lofthouse created WFLY-7870: -------------------------------------- Summary: Remove the -elytron.xml configurations and add the Elytron subsystem to the default configuration. Key: WFLY-7870 URL: https://issues.jboss.org/browse/WFLY-7870 Project: WildFly Issue Type: Enhancement Components: Build System Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 11.0.0.Alpha1 Resources will continue to reference legacy security resources, we will document some commands showing how to activate Elytron based security. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2174) AwaiterModelControllerClient should be in public package

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2174?page=com.atlassian.jira.plugi... ] Jean-Francois Denise commented on WFCORE-2174: ---------------------------------------------- I introduced this interface to hide the CLIModelControllerClient impl. But it ended in the wrong package. JF > AwaiterModelControllerClient should be in public package > -------------------------------------------------------- > > Key: WFCORE-2174 > URL: https://issues.jboss.org/browse/WFCORE-2174 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > AwaiterModelControllerClient can be used by third party, it shouldn't be in impl. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2175) suggest-capabilities operation fails for specific parameters

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2175?page=com.atlassian.jira.plugi... ] Tomaz Cerar reassigned WFCORE-2175: ----------------------------------- Assignee: Tomaz Cerar (was: Brian Stansberry) > suggest-capabilities operation fails for specific parameters > ------------------------------------------------------------ > > Key: WFCORE-2175 > URL: https://issues.jboss.org/browse/WFCORE-2175 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Harald Pehl > Assignee: Tomaz Cerar > > The following operation fails with a {{StringIndexOutOfBoundsException}} > {code} > /host=master/core-service=capability-registry:suggest-capabilities(name=org.wildfly.clustering.jgroups.channel-factory,dependent-address=[("profile" => "full-ha"),("subsystem" => "jgroups")]) > {code} > while similar operations work w/o an error > {code} > /host=master/core-service=capability-registry:suggest-capabilities(name=org.wildfly.batch.job.repository, dependent-address=[("profile" => "full"), ("subsystem" => "batch-jberet")]) > {code} > This is the code which throws the {{StringIndexOutOfBoundsException}}: https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBLOGGING-127) JDK 9 EA build 151 - Loggers not created

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/JBLOGGING-127?page=com.atlassian.jira.plu... ] James Perkins commented on JBLOGGING-127: ----------------------------------------- This is caused by JDK-8172158. I'll leave this open for now until a release is done with the bug fix. > JDK 9 EA build 151 - Loggers not created > ---------------------------------------- > > Key: JBLOGGING-127 > URL: https://issues.jboss.org/browse/JBLOGGING-127 > Project: JBoss Logging > Issue Type: Bug > Affects Versions: 3.2.1.Final > Reporter: Matej Novotny > Assignee: James Perkins > > I started looking into JDK 9 EA for [Weld|https://github.com/weld/core] and we use JBoss logging [there|https://github.com/weld/core/tree/master/impl/src/main/java/org/jbo...]. > Everything was working as expected with logging up until latest JDK EA build release (build 151). > Suddenly, after running build on JDK 9, no logger classes are generated and there is no error message either. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2174) AwaiterModelControllerClient should be in public package

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2174?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-2174: ------------------------------------------ Ah, never mind, I should look at what the issue is about before commenting! This isn't actually a ModelControllerClient impl or subinterface. > AwaiterModelControllerClient should be in public package > -------------------------------------------------------- > > Key: WFCORE-2174 > URL: https://issues.jboss.org/browse/WFCORE-2174 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Reporter: Jean-Francois Denise > Assignee: Jean-Francois Denise > > AwaiterModelControllerClient can be used by third party, it shouldn't be in impl. > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2175) suggest-capabilities operation fails for specific parameters

by Harald Pehl (JIRA)

Harald Pehl created WFCORE-2175: ----------------------------------- Summary: suggest-capabilities operation fails for specific parameters Key: WFCORE-2175 URL: https://issues.jboss.org/browse/WFCORE-2175 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Harald Pehl Assignee: Brian Stansberry The following operation fails with a {{StringIndexOutOfBoundsException}} {code} /host=master/core-service=capability-registry:suggest-capabilities(name=org.wildfly.clustering.jgroups.channel-factory,dependent-address=[("profile" => "full-ha"),("subsystem" => "jgroups")]) {code} while similar operations work w/o an error {code} /host=master/core-service=capability-registry:suggest-capabilities(name=org.wildfly.batch.job.repository, dependent-address=[("profile" => "full"), ("subsystem" => "batch-jberet")]) {code} This is the code which throws the {{StringIndexOutOfBoundsException}}: https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/j... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 January 2017