December 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-5241) Update messaging subsystem descriptions to properly report path cardinality

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5241?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5241. ---------------------------- > Update messaging subsystem descriptions to properly report path cardinality > --------------------------------------------------------------------------- > > Key: WFLY-5241 > URL: https://issues.jboss.org/browse/WFLY-5241 > Project: WildFly > Issue Type: Task > Components: JMS > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 10.0.0.CR1 > > > https://docs.jboss.org/author/display/WFLY10/Description+of+the+Managemen... has been updated to more intelligently report cardinality information about resource registrations, with each reg reporting its own cardinality instead of having the parent report data about the "key" portion of potentially unrelated children. > The two messaging subsystems are actually trying to use the old way for "path" children, so this JIRA is to move to the new way. > Instead of the parent resource reporting there must be 4 and no more than 4 children with key "path", now each of the 4 valid path children types will report that the min-occurs of that type is 1. (The max-occurs is also 1, but that will not be reported as that, per the spec, is the default for a 'singleton' type, and each of the 4 path types is a singleton.) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4981) Upgrade JBossWS from 5.0.0.Final to 5.1.0.Beta1

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4981?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4981. ---------------------------- > Upgrade JBossWS from 5.0.0.Final to 5.1.0.Beta1 > ----------------------------------------------- > > Key: WFLY-4981 > URL: https://issues.jboss.org/browse/WFLY-4981 > Project: WildFly > Issue Type: Component Upgrade > Components: Web Services > Reporter: Alessio Soldano > Assignee: Alessio Soldano > Fix For: 10.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4676) Unify help message in wsprovide.bat and wsprovide.sh

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4676?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4676. ---------------------------- > Unify help message in wsprovide.bat and wsprovide.sh > ---------------------------------------------------- > > Key: WFLY-4676 > URL: https://issues.jboss.org/browse/WFLY-4676 > Project: WildFly > Issue Type: Bug > Components: Web Services > Affects Versions: 10.0.0.Alpha1 > Reporter: Marek Kopecký > Assignee: Alessio Soldano > Priority: Minor > Fix For: 10.0.0.Alpha3 > > > Description of problem: > Unify help message in wsprovide.bat and wsprovide.sh > Steps to Reproduce: > 1. On windows: wsconsume.bat -h > 2. On linux: wsconsume.sh -h > Actual results: > On windows: > ... > usage: WSProvide [options] <endpoint class name> > ... > On linux: > ... > usage: wsprovide.sh [options] <endpoint class name> > ... > Expected results on Windows: > ... > usage: wsprovide.bat [options] <endpoint class name> > ... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2667) Support application-level batch configuration

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-2667?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-2667. ---------------------------- > Support application-level batch configuration > --------------------------------------------- > > Key: WFLY-2667 > URL: https://issues.jboss.org/browse/WFLY-2667 > Project: WildFly > Issue Type: Feature Request > Components: Batch > Affects Versions: 8.0.0.Beta1 > Reporter: Cheng Fang > Assignee: James Perkins > Fix For: 10.0.0.Alpha1 > > > Applications should be able to override certain batch configuration in WildFly batch subsystem with application deployment descriptors. In particular, applications may want to specify their own datasource jndi-name for batch job repository. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4680) Fork and JChannel names need to be unique

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4680?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4680. ---------------------------- > Fork and JChannel names need to be unique > ----------------------------------------- > > Key: WFLY-4680 > URL: https://issues.jboss.org/browse/WFLY-4680 > Project: WildFly > Issue Type: Sub-task > Components: Clustering > Affects Versions: 9.0.0.CR1, 10.0.0.Alpha2 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 9.0.0.CR2, 10.0.0.Alpha3 > > > The point is to > * recreate the channels as ee-web (with web fork on it) instead of channel web with fork web on it > * also investigate why without the fix for https://issues.jboss.org/browse/WFLY-4435 (and WFLY-4680) naming fork channels and jchannels the same (e.g. web) doesn't just result in duplicated service warning, but instead fails badly e.g. NPE in Infinispan https://issues.jboss.org/browse/ISPN-5483 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5285) Remove use of ManagementResourceRegistration.setRuntimeOnly()

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5285?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5285. ---------------------------- > Remove use of ManagementResourceRegistration.setRuntimeOnly() > ------------------------------------------------------------- > > Key: WFLY-5285 > URL: https://issues.jboss.org/browse/WFLY-5285 > Project: WildFly > Issue Type: Task > Affects Versions: 10.0.0.Beta2 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 10.0.0.CR1 > > > Replace use of to-be-deprecated ManagementResourceRegistration.setRuntimeOnly() with setting this up via the ResourceDefinition. > Right thing to do, plus it blocks WFCORE-959. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4587) Provide a migration management operation for HornetQ to ActiveMQ Artemis

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-4587?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-4587. ---------------------------- > Provide a migration management operation for HornetQ to ActiveMQ Artemis > ------------------------------------------------------------------------ > > Key: WFLY-4587 > URL: https://issues.jboss.org/browse/WFLY-4587 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha6 > > > WildFly 10 has a new messaging-activemq subsystem using ActiveMQ Artemis as its messaging broker. > WildFly 10 needs to provide a :migrate management operation so that user upgrading from WildFly 9 to 10 can start WildFly 10 with their old configuration (which used HornetQ) and migrate to the new subsystem (which used ActiveMQ Artemis). > This migrate operation deals only with the management resource and does *not* migrate data from HornetQ to Artemis. This will done in a separate step (using either a JMS bridge or data export tool) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-3518) JASPIAuthenticationMechanism#authenticate doesn't check if AuthenticatedSession is null

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-3518?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-3518. ---------------------------- > JASPIAuthenticationMechanism#authenticate doesn't check if AuthenticatedSession is null > --------------------------------------------------------------------------------------- > > Key: WFLY-3518 > URL: https://issues.jboss.org/browse/WFLY-3518 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 8.1.0.Final > Reporter: arjan tijms > Assignee: Stuart Douglas > Labels: jaspic > Fix For: 9.0.0.CR2, 10.0.0.Alpha1 > > > In {{org.wildfly.extension.undertow.security.jaspi.JASPIAuthenticationMechanism#authenticate}} the variable {{authSession}} in the fragment below is frequently null, leading to null pointer exceptions: > {code} > if (sessionManager != null) { > AuthenticatedSessionManager.AuthenticatedSession authSession = sessionManager.lookupSession(exchange); > cachedAccount = authSession.getAccount(); // NPE HAPPENS HERE > // if there is a cached account we set it in the security context so that the principal is available to > // SAM modules via request.getUserPrincipal(). > if (cachedAccount != null) { > jaspicSecurityContext.setCachedAuthenticatedAccount(cachedAccount); > } > } > {code} > At another place in Undertow where {{AuthenticatedSession}} is used, there's an extra null check (See {{io.undertow.security.impl.CachedAuthenticatedSessionMechanism#runCached}}). > I patched the code locally to add an extra null check: > {code} > if (sessionManager != null) { > AuthenticatedSessionManager.AuthenticatedSession authSession = sessionManager.lookupSession(exchange); > cachedAccount = authSession == null? null : authSession.getAccount(); > // if there is a cached account we set it in the security context so that the principal is available to > // SAM modules via request.getUserPrincipal(). > if (cachedAccount != null) { > jaspicSecurityContext.setCachedAuthenticatedAccount(cachedAccount); > } > } > {code} > After a short amount of testing everything seems to be okay with that extra check. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5050) JSP Cross-Context Include Not Working

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5050?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5050. ---------------------------- > JSP Cross-Context Include Not Working > ------------------------------------- > > Key: WFLY-5050 > URL: https://issues.jboss.org/browse/WFLY-5050 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 8.2.1.Final, 9.0.1.Final > Environment: Java 8 > Reporter: Brett Prucha > Assignee: Stuart Douglas > Fix For: 10.0.0.Beta1 > > Attachments: test.ear > > > Including JSP files from a cross-context application results in various errors depending on how it's executed and which version of Wildfly (8 or 9) is being used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-5004) Messaging migration does not work in domain mode

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-5004?page=com.atlassian.jira.plugin.... ] Kabir Khan closed WFLY-5004. ---------------------------- > Messaging migration does not work in domain mode > ------------------------------------------------ > > Key: WFLY-5004 > URL: https://issues.jboss.org/browse/WFLY-5004 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 10.0.0.Alpha5 > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Fix For: 10.0.0.Alpha6 > > > The :migrate operation of the legacy messaging subsystem does not work in domain mode. > The addresses returned by the describe handler starts with /subsystem while in domain mode, the subsystem configuration are under /profile=XXX > The :migrate operation must prepend the operation parent address (EMPTY_ADDRESS in standalone mode, /profile=XXX in domain mode) for the operation to be successful. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 7 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 December 2017