May 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9658) Batch jobs in a sub-deployment can be started but not queried

by Alessandro Moscatelli (JIRA)

[ https://issues.jboss.org/browse/WFLY-9658?page=com.atlassian.jira.plugin.... ] Alessandro Moscatelli commented on WFLY-9658: --------------------------------------------- Is this really fixed in 13.0.0.Beta1 ? I just had a try and it seems not ... > Batch jobs in a sub-deployment can be started but not queried > ------------------------------------------------------------- > > Key: WFLY-9658 > URL: https://issues.jboss.org/browse/WFLY-9658 > Project: WildFly > Issue Type: Bug > Components: Batch > Reporter: James Perkins > Assignee: James Perkins > > In an EAR deployment that contains a multiple batch deployments each sub-deployment can start jobs from other sub-deployments, but the job information cannot be queried. For example a job can be started from a WAR that is in an EJB, however you cannot execute {{JobOperator.getJobInstance()}} from the WAR on the same job. > Visibility should be consistent for starting and querying batch jobs. > More details on https://github.com/jberet/jsr352/issues/105. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2531) Scenario Simulation feature

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2531?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2531: -------------------------------- Tester: Jozef Marko > Scenario Simulation feature > --------------------------- > > Key: DROOLS-2531 > URL: https://issues.jboss.org/browse/DROOLS-2531 > Project: Drools > Issue Type: Enhancement > Reporter: Daniele Zonca > Assignee: Daniele Zonca > > We want to create a new feature in Drools WB and core to support scenario testing. > The scenarios will be executed in a simulation mode to let the user able to test his system and export results for post-simulation analysis/no regression. > Drools WB should support user in scenario definition (i.e. define facts template) and then let insert input data (single or bulk) with corresponding expected results. > Drools core should support steps definition with a fluent API and then simulation runs. We should also support a JUnit-like output format. > This feature will also dismiss current Test Scenario asset -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3868) Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3868?page=com.atlassian.jira.plugi... ] Yeray Borges reassigned WFCORE-3868: ------------------------------------ Assignee: Yeray Borges (was: David Lloyd) > Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-3868 > URL: https://issues.jboss.org/browse/WFCORE-3868 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta4 > Reporter: Yeray Borges > Assignee: Yeray Borges > Attachments: ExecutorServiceShutdownReproducer.war > > > EAP's EE-Concurrency Managed Executor Service is expected to skip the tasks that are pending in its execution queue upon server shutdown as [documented here |https://docs.jboss.org/author/display/WFLY/Suspend%2C+Resume+and+Graceful+shutdown] > This is necessary to cope with scenario where a polling-type task is re-scheduling a new instance of itself just before exiting (so that there is always one task polling - pattern used e.g. by Spring message listeners -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-3868) Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work

by Yeray Borges (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3868?page=com.atlassian.jira.plugi... ] Yeray Borges moved JBEAP-14764 to WFCORE-3868: ---------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-3868 (was: JBEAP-14764) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: EE) Affects Version/s: 5.0.0.Beta4 (was: 7.1.2.GA) > Domain mode shutdown of EE executor service with :stop() or :stop(timeout=0) command doesn't work > ------------------------------------------------------------------------------------------------- > > Key: WFCORE-3868 > URL: https://issues.jboss.org/browse/WFCORE-3868 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 5.0.0.Beta4 > Reporter: Yeray Borges > Assignee: David Lloyd > Attachments: ExecutorServiceShutdownReproducer.war > > > EAP's EE-Concurrency Managed Executor Service is expected to skip the tasks that are pending in its execution queue upon server shutdown as [documented here |https://docs.jboss.org/author/display/WFLY/Suspend%2C+Resume+and+Graceful+shutdown] > This is necessary to cope with scenario where a polling-type task is re-scheduling a new instance of itself just before exiting (so that there is always one task polling - pattern used e.g. by Spring message listeners -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty to 4.1.24.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Summary: Upgrade Netty to 4.1.24.Final (was: Upgrade Netty to 4.1.22.Final) > Upgrade Netty to 4.1.24.Final > ----------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.22.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9483) Upgrade Netty to 4.1.24.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9483?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9483: ------------------------------ Description: https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.24.F... (was: https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.22.F...) > Upgrade Netty to 4.1.24.Final > ----------------------------- > > Key: WFLY-9483 > URL: https://issues.jboss.org/browse/WFLY-9483 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > https://github.com/netty/netty/compare/netty-4.1.9.Final...netty-4.1.24.F... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9484) Upgrade netty-xnio-transport to 0.1.6.Final

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9484?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9484: ------------------------------ Summary: Upgrade netty-xnio-transport to 0.1.6.Final (was: Upgrade netty-xnio-transport to 0.1.5.Final) > Upgrade netty-xnio-transport to 0.1.6.Final > ------------------------------------------- > > Key: WFLY-9484 > URL: https://issues.jboss.org/browse/WFLY-9484 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > netty-xnio-transport must be updated to the version of XNIO and netty used in WildFly with Artemis 2.x releases -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9407) Upgrade Artemis 2.6.0

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9407?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-9407: ------------------------------ Summary: Upgrade Artemis 2.6.0 (was: Upgrade Artemis 2.5.0) > Upgrade Artemis 2.6.0 > --------------------- > > Key: WFLY-9407 > URL: https://issues.jboss.org/browse/WFLY-9407 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: downstream_dependency > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1377) use enlistmentTrace instead of disableEnlistment parameter to avoid eager IJ000100

by Stefano Maestri (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1377?page=com.atlassian.jira.plugin... ] Stefano Maestri resolved JBJCA-1377. ------------------------------------ Resolution: Done > use enlistmentTrace instead of disableEnlistment parameter to avoid eager IJ000100 > ---------------------------------------------------------------------------------- > > Key: JBJCA-1377 > URL: https://issues.jboss.org/browse/JBJCA-1377 > Project: IronJacamar > Issue Type: Bug > Reporter: Stefano Maestri > Assignee: Stefano Maestri > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1587) X500 principal [CN=client] was not decoded - no values of attribute [2.5.4.3]

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-1587?page=com.atlassian.jira.plugin.s... ] Martin Choma updated ELY-1587: ------------------------------ Description: Debugging revealed certificate use {{utf8String}} representation whereas Elytron is expecting {{printableString}} In rfc 5280 [1] chapter 4.1.2.4. Issuer there is specified value of subject/issuer can be of 5 types {code} DirectoryString ::= CHOICE { teletexString TeletexString (SIZE (1..MAX)), printableString PrintableString (SIZE (1..MAX)), universalString UniversalString (SIZE (1..MAX)), utf8String UTF8String (SIZE (1..MAX)), bmpString BMPString (SIZE (1..MAX)) } {code} However Elytron X500 principal decoder [2] can handle only 2 of them PRINTABLE_STRING_TYPE and IA5_STRING_TYPE (not sure which type of rfc does that match) [2] Definitely missing {{utf8String}} (my case). Also revise for backward compatibility {{teletexString}}, {{bmpString}} and {{universalString}} [1] https://www.ietf.org/rfc/rfc5280.txt [2] https://github.com/wildfly-security/wildfly-elytron/blob/32ff7c17965b3eca... was: Debugging revealed certificate use {{utf8String}} representation whereas Elytron is expecting {{printableString}} In rfc 5280 [1] chapter 4.1.2.4. Issuer there is specified value of ssubject/issuer can be of 5 types {code} DirectoryString ::= CHOICE { teletexString TeletexString (SIZE (1..MAX)), printableString PrintableString (SIZE (1..MAX)), universalString UniversalString (SIZE (1..MAX)), utf8String UTF8String (SIZE (1..MAX)), bmpString BMPString (SIZE (1..MAX)) } {code} However Elytron X500 principal decoder [2] can handle only 2 of them PRINTABLE_STRING_TYPE and IA5_STRING_TYPE (not sure which type of rfc does that match) [2] Definitely missing {{utf8String}} (my case). Also revise for backward compatibility {{teletexString}}, {{bmpString}} and {{universalString}} [1] https://www.ietf.org/rfc/rfc5280.txt [2] https://github.com/wildfly-security/wildfly-elytron/blob/32ff7c17965b3eca... > X500 principal [CN=client] was not decoded - no values of attribute [2.5.4.3] > ----------------------------------------------------------------------------- > > Key: ELY-1587 > URL: https://issues.jboss.org/browse/ELY-1587 > Project: WildFly Elytron > Issue Type: Bug > Components: Certificate Authority, X.500 > Affects Versions: 1.3.2.Final > Reporter: Martin Choma > Priority: Critical > Fix For: 1.3.3.CR1 > > > Debugging revealed certificate use {{utf8String}} representation whereas Elytron is expecting {{printableString}} > In rfc 5280 [1] chapter 4.1.2.4. Issuer there is specified value of subject/issuer can be of 5 types > {code} > DirectoryString ::= CHOICE { > teletexString TeletexString (SIZE (1..MAX)), > printableString PrintableString (SIZE (1..MAX)), > universalString UniversalString (SIZE (1..MAX)), > utf8String UTF8String (SIZE (1..MAX)), > bmpString BMPString (SIZE (1..MAX)) } > {code} > However Elytron X500 principal decoder [2] can handle only 2 of them PRINTABLE_STRING_TYPE and IA5_STRING_TYPE (not sure which type of rfc does that match) [2] > Definitely missing {{utf8String}} (my case). Also revise for backward compatibility {{teletexString}}, {{bmpString}} and {{universalString}} > [1] https://www.ietf.org/rfc/rfc5280.txt > [2] https://github.com/wildfly-security/wildfly-elytron/blob/32ff7c17965b3eca... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 May 2018