September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFWIP-194) Operator does not provide way to expose arbitrary port

by Martin Choma (Jira)

Martin Choma created WFWIP-194: ---------------------------------- Summary: Operator does not provide way to expose arbitrary port Key: WFWIP-194 URL: https://issues.jboss.org/browse/WFWIP-194 Project: WildFly WIP Issue Type: Bug Components: OpenShift Reporter: Martin Choma Assignee: Jeff Mesnil Going through non-Operator approach scenarios we have identified Operator is missing this feature: way to expose arbitrary container port, e.g: - https:8443 - jolokia:8778 - debugging:5000 - dns-ping:8888 - any app specific port Could be partially workarounded by `oc port-forward` capability -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4522) Invoke java methds during test scenarios

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4522: ------------------------------- Fix Version/s: 7.6.0.Final (was: 7.27.0.Final) > Invoke java methds during test scenarios > ---------------------------------------- > > Key: DROOLS-4522 > URL: https://issues.jboss.org/browse/DROOLS-4522 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Fix For: 7.6.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4522) Invoke java methds during test scenarios

by Yeser Amer (Jira)

Yeser Amer created DROOLS-4522: ---------------------------------- Summary: Invoke java methds during test scenarios Key: DROOLS-4522 URL: https://issues.jboss.org/browse/DROOLS-4522 Project: Drools Issue Type: Feature Request Components: Scenario Simulation and Testing Reporter: Yeser Amer Assignee: Yeser Amer Fix For: 7.27.0.Final -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4522) Invoke java methds during test scenarios

by Yeser Amer (Jira)

[ https://issues.jboss.org/browse/DROOLS-4522?page=com.atlassian.jira.plugi... ] Yeser Amer updated DROOLS-4522: ------------------------------- Sprint: 2019 Week 35-37 > Invoke java methds during test scenarios > ---------------------------------------- > > Key: DROOLS-4522 > URL: https://issues.jboss.org/browse/DROOLS-4522 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Fix For: 7.27.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-236) Update MANIFEST for JASPI

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/JBEE-236?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse resolved JBEE-236. ----------------------------------- Resolution: Done > Update MANIFEST for JASPI > ------------------------- > > Key: JBEE-236 > URL: https://issues.jboss.org/browse/JBEE-236 > Project: JBoss Enterprise Spec APIs > Issue Type: Task > Components: jboss-jaspi-api > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: jboss-jakarta-jaspi-api_spec-2.0.0.Final > > -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12522) Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFLY-12522?page=com.atlassian.jira.plugin... ] Jean Francois Denise commented on WFLY-12522: --------------------------------------------- Assigning to [~flavia.rainone]. > Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12522 > URL: https://issues.jboss.org/browse/WFLY-12522 > Project: WildFly > Issue Type: Bug > Components: CLI, Remoting, Web (Undertow) > Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final > Reporter: super 6349 > Assignee: Flavia Rainone > Priority: Major > > When the user executes jboss-cli commands on a fresh installation of wildfly, RemoteConnectionHandler objects are created but never released. > We identified this problem when we configured a readiness probe on openshift using jboss-cli (repeating every 15 seconds) and the memory started to increase along the days. The application was in development and nobody was accessing it, but the memory increased nonetheless. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12522) Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed

by Jean Francois Denise (Jira)

[ https://issues.jboss.org/browse/WFLY-12522?page=com.atlassian.jira.plugin... ] Jean Francois Denise reassigned WFLY-12522: ------------------------------------------- Assignee: Flavia Rainone (was: Jean Francois Denise) > Memory Leak: RemoteConnectionHandler objects are created but not being freed when jboss-cli commands are executed > ----------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12522 > URL: https://issues.jboss.org/browse/WFLY-12522 > Project: WildFly > Issue Type: Bug > Components: CLI, Remoting, Web (Undertow) > Affects Versions: 16.0.0.Final, 17.0.0.Final, 17.0.1.Final > Reporter: super 6349 > Assignee: Flavia Rainone > Priority: Major > > When the user executes jboss-cli commands on a fresh installation of wildfly, RemoteConnectionHandler objects are created but never released. > We identified this problem when we configured a readiness probe on openshift using jboss-cli (repeating every 15 seconds) and the memory started to increase along the days. The application was in development and nobody was accessing it, but the memory increased nonetheless. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBEE-237) Jakarta annotations missing license file in final jar distribution

by Yeray Borges (Jira)

Yeray Borges created JBEE-237: --------------------------------- Summary: Jakarta annotations missing license file in final jar distribution Key: JBEE-237 URL: https://issues.jboss.org/browse/JBEE-237 Project: JBoss Enterprise Spec APIs Issue Type: Bug Components: jboss-annotations-api Reporter: Yeray Borges Assignee: Yeray Borges -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12539) JGroups get modified in a wrong way after cli command

by Tomas Hofman (Jira)

[ https://issues.jboss.org/browse/WFLY-12539?page=com.atlassian.jira.plugin... ] Tomas Hofman moved JBEAP-17563 to WFLY-12539: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12539 (was: JBEAP-17563) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Management (was: Management) Affects Version/s: 18.0.0.Beta1 (was: 7.2.3.GA) Fix Version/s: (was: 7.2.5.GA) > JGroups get modified in a wrong way after cli command > ----------------------------------------------------- > > Key: WFLY-12539 > URL: https://issues.jboss.org/browse/WFLY-12539 > Project: WildFly > Issue Type: Bug > Components: Management > Affects Versions: 18.0.0.Beta1 > Environment: - Red Hat JBoss Enterprise Application Platform (EAP) > - 7.1 onwards > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Priority: Major > > What happens: > While trying to run domain with EAP 7 with EAP 6 as slaves the following happens: > Intro: > On running following cli commands after domain controller started, the jgroups get modified by themselves in a wrong way: > ------ > cli commands run: > /profile=MP_NONSINGLETONS/subsystem=bean-validation:remove > /profile=MP_TRANS_RMP_RAY/subsystem=bean-validation:remove > ------- > Before running cli command: > <protocol type="pbcast.NAKACK"/> > <protocol type="UNICAST2"/> > After running cli command: > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > ------ > Full jgroups section before running cli command for MP_TRANS_RMP_RAY, MP_NONSINGLETONS profiles: > Before running cli command: > <subsystem xmlns="urn:jboss:domain:jgroups:1.1" default-stack="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK"/> > <protocol type="UNICAST2"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </subsystem> > After running cli command: > ~~~ > <subsystem xmlns="urn:jboss:domain:jgroups:6.0"> > <channels default="auto"> > <channel name="ee-web" stack="udp"/> > <channel name="ee-hibernate" stack="udp"/> > <channel name="auto" stack="udp"/> > </channels> > <stacks default="udp"> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"> > <property name="port_range"> > 50 > </property> > </transport> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK" socket-binding="jgroups-udp-fd"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > <protocol type="RSVP"/> > </stack> > </stacks> > </subsystem> > ~~~ > The architecture EAP 7 master - EAP 6 slave is supported according to https://access.redhat.com/articles/2568341 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-11604) Non-anonymous principal is not propagated from EJB context to CDI bean

by Diana Vilkolakova (Jira)

[ https://issues.jboss.org/browse/WFLY-11604?page=com.atlassian.jira.plugin... ] Diana Vilkolakova closed WFLY-11604. ------------------------------------ Resolution: Duplicate WFLY-12537 and WFLY-12538 have been created to address the issues that came up in the comments. > Non-anonymous principal is not propagated from EJB context to CDI bean > ---------------------------------------------------------------------- > > Key: WFLY-11604 > URL: https://issues.jboss.org/browse/WFLY-11604 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Affects Versions: 14.0.1.Final, 15.0.1.Final > Reporter: Nikoleta Ziakova > Priority: Critical > > This is a follow-up on WFLY-11587 which only dealt with being able to inject the principal. > However, during testing I have tried a scenario when the caller principal was not anonymous (run-as-principal setting in jboss-ejb3.xml). See the test case in this [commit|https://github.com/nziakova/wildfly/commit/9ae586ad0159e6399f65103...]. > The principal is not propagated from the EJB context. The result is that injected principal in the CDI bean is always anonymous, although {{ctx.getCallerPrincipal()}} in the EJB returns correct principal. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019