December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12905) Update $JBOSS_HOME/docs/schema to show https schema URL instead of http

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFLY-12905?page=com.atlassian.jira.plugi... ] Chao Wang updated WFLY-12905: ----------------------------- Description: jboss.org will start redirecting http to https , while JBoss should not have an issue if deployment descriptors are referencing http when they get redirected, we have seen some frameworks do have an issue. So it would be better if our schemas tell users to use the https for the schema. > Update $JBOSS_HOME/docs/schema to show https schema URL instead of http > ----------------------------------------------------------------------- > > Key: WFLY-12905 > URL: https://issues.redhat.com/browse/WFLY-12905 > Project: WildFly > Issue Type: Bug > Components: Server > Affects Versions: 18.0.1.Final > Reporter: Chao Wang > Assignee: Chao Wang > Priority: Major > > jboss.org will start redirecting http to https , while JBoss should not have an issue if deployment descriptors are referencing http when they get redirected, we have seen some frameworks do have an issue. So it would be better if our schemas tell users to use the https for the schema. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1915) stronger credential store

by Hisanobu Okuda (Jira)

Hisanobu Okuda created ELY-1915: ----------------------------------- Summary: stronger credential store Key: ELY-1915 URL: https://issues.redhat.com/browse/ELY-1915 Project: WildFly Elytron Issue Type: Feature Request Components: Credential Store Affects Versions: 1.6.1.Final Reporter: Hisanobu Okuda JCEKS which is used for credential store uses 3DES. Need more stronger credential store based on a stronger cryptography like AES256 or more. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12886) WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi... ] nimo stephan edited comment on WFLY-12886 at 12/19/19 5:03 PM: --------------------------------------------------------------- >Aren't you using empty beans.xml? yes, my beans.xml is emtpy. >Hmm, I cannot reproduce the problem. Actually, I use wildfly 17..and I see "WELD-000119" *on every log on restart.*.I cannot confirm this on wf 18..I also enabled DEBUG log to see more: {code:java} .. 03:22:14,144 INFO [io.smallrye.metrics] MicroProfile: Metrics activated 03:22:14,185 WARN [org.jboss.weld.Bootstrap] WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1! 03:22:14,485 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. 03:22:15,508 DEBUG [org.jboss.as.jpa] ServerService Thread Pool -- 81:transaction scoped EntityManager [ki.war#PU_QI]: created entity manager session Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000001:50467e87:5dfadec2:11 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) .. {code} However, all works, I dont see any errors. I dont think it`s important.. was (Author: nimo22): >Aren't you using empty beans.xml? yes, my beans.xml is emtpy. >Hmm, I cannot reproduce the problem. Actually, I use wildfly 17..and I see "WELD-000119" on every log on restart..I cannot confirm this on wf 18..I also enabled DEBUG log to see more: {code:java} .. 03:22:14,144 INFO [io.smallrye.metrics] MicroProfile: Metrics activated 03:22:14,185 WARN [org.jboss.weld.Bootstrap] WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1! 03:22:14,485 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. 03:22:15,508 DEBUG [org.jboss.as.jpa] ServerService Thread Pool -- 81:transaction scoped EntityManager [ki.war#PU_QI]: created entity manager session Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000001:50467e87:5dfadec2:11 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) .. {code} However, all works, I dont see any errors. I dont think it`s important.. > WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-12886 > URL: https://issues.redhat.com/browse/WFLY-12886 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 17.0.1.Final > Reporter: nimo stephan > Assignee: Matěj Novotný > Priority: Minor > > I get this info when starting wildfly server: > {code:java} > 01:33:09,168 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. > {code} > My WebUtils.class imports: > {code:java} > import java.net.URI; > import java.net.http.HttpClient; > import java.net.http.HttpRequest; > import java.net.http.HttpResponse.BodyHandlers; > {code} > Should I include java se module by myself in wildfly to remove this log? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12886) WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient

by nimo stephan (Jira)

[ https://issues.redhat.com/browse/WFLY-12886?page=com.atlassian.jira.plugi... ] nimo stephan commented on WFLY-12886: ------------------------------------- >Aren't you using empty beans.xml? yes, my beans.xml is emtpy. >Hmm, I cannot reproduce the problem. Actually, I use wildfly 17..and I see "WELD-000119" on every log on restart..I cannot confirm this on wf 18..I also enabled DEBUG log to see more: {code:java} .. 03:22:14,144 INFO [io.smallrye.metrics] MicroProfile: Metrics activated 03:22:14,185 WARN [org.jboss.weld.Bootstrap] WELD-000146: BeforeBeanDiscovery.addAnnotatedType(AnnotatedType<?>) used for class com.sun.faces.flow.FlowDiscoveryCDIHelper is deprecated from CDI 1.1! 03:22:14,485 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. If this is unexpected, enable DEBUG logging to see the full error. 03:22:15,508 DEBUG [org.jboss.as.jpa] ServerService Thread Pool -- 81:transaction scoped EntityManager [ki.war#PU_QI]: created entity manager session Local transaction (delegate=TransactionImple < ac, BasicAction: 0:ffff7f000001:50467e87:5dfadec2:11 status: ActionStatus.RUNNING >, owner=Local transaction context for provider JBoss JTA transaction provider) .. {code} However, all works, I dont see any errors. I dont think it`s important.. > WELD-000119: Not generating any bean definitions from..class loading error: Type java.net.http.HttpClient > --------------------------------------------------------------------------------------------------------- > > Key: WFLY-12886 > URL: https://issues.redhat.com/browse/WFLY-12886 > Project: WildFly > Issue Type: Enhancement > Components: CDI / Weld > Affects Versions: 17.0.1.Final > Reporter: nimo stephan > Assignee: Matěj Novotný > Priority: Minor > > I get this info when starting wildfly server: > {code:java} > 01:33:09,168 INFO [org.jboss.weld.Bootstrap] WELD-000119: Not generating any bean definitions from com.utils.WebUtils because of underlying class loading error: Type java.net.http.HttpClient from [Module "deployment.myapp.war" from Service Module Loader] not found. > {code} > My WebUtils.class imports: > {code:java} > import java.net.URI; > import java.net.http.HttpClient; > import java.net.http.HttpRequest; > import java.net.http.HttpResponse.BodyHandlers; > {code} > Should I include java se module by myself in wildfly to remove this log? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-289) Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues

by Fabio Burzigotti (Jira)

[ https://issues.redhat.com/browse/WFWIP-289?page=com.atlassian.jira.plugin... ] Fabio Burzigotti commented on WFWIP-289: ---------------------------------------- Thanks Paul for closing this issue and for your support. > Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues > -------------------------------------------------------------------------------------------- > > Key: WFWIP-289 > URL: https://issues.redhat.com/browse/WFWIP-289 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Blocker > > Complex scenario with 4 subsequent deployments. > The last one adds the `mp.openapi.scan.disable=true` MP Config core property - consequently no `mp.openapi.extensions.path` MP Config vendor extension property is defined. > This causes the server to behave in non-deterministic way for generation of OpenAPI document at standard `/openapi` URL. > "Non-deterministic" means that - when the test is executed several times - the generated document contains elements either from first or second deployments (third one is not registering the endpoint and is skipped as expected). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-1002) doPrivileged is used even when no security manager is present

by Stefan Guilhen (Jira)

[ https://issues.redhat.com/browse/SECURITY-1002?page=com.atlassian.jira.pl... ] Stefan Guilhen closed SECURITY-1002. ------------------------------------ Resolution: Won't Fix PicketBox community has been archived > doPrivileged is used even when no security manager is present > ------------------------------------------------------------- > > Key: SECURITY-1002 > URL: https://issues.redhat.com/browse/SECURITY-1002 > Project: PicketBox > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stefan Guilhen > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SECURITY-1003) SubjectActions uses AccessController.doPrivileged even when no security manager is present

by Stefan Guilhen (Jira)

[ https://issues.redhat.com/browse/SECURITY-1003?page=com.atlassian.jira.pl... ] Stefan Guilhen closed SECURITY-1003. ------------------------------------ Resolution: Won't Fix PicketBox community has been archived > SubjectActions uses AccessController.doPrivileged even when no security manager is present > ------------------------------------------------------------------------------------------ > > Key: SECURITY-1003 > URL: https://issues.redhat.com/browse/SECURITY-1003 > Project: PicketBox > Issue Type: Bug > Reporter: Stuart Douglas > Assignee: Stefan Guilhen > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-289) Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFWIP-289?page=com.atlassian.jira.plugin... ] Paul Ferraro closed WFWIP-289. ------------------------------ Resolution: Cannot Reproduce Once test was fixed to setup properly, the test passes. > Using mp.openapi.scan.disable=true on subsequent deployment causes OpenAPI generation issues > -------------------------------------------------------------------------------------------- > > Key: WFWIP-289 > URL: https://issues.redhat.com/browse/WFWIP-289 > Project: WildFly WIP > Issue Type: Bug > Components: MP OpenAPI > Reporter: Fabio Burzigotti > Assignee: Paul Ferraro > Priority: Blocker > > Complex scenario with 4 subsequent deployments. > The last one adds the `mp.openapi.scan.disable=true` MP Config core property - consequently no `mp.openapi.extensions.path` MP Config vendor extension property is defined. > This causes the server to behave in non-deterministic way for generation of OpenAPI document at standard `/openapi` URL. > "Non-deterministic" means that - when the test is executed several times - the generated document contains elements either from first or second deployments (third one is not registering the endpoint and is skipped as expected). -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12904) Create a quickstart for the ejb remoting and transaction recovery on OpenShift

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFLY-12904?page=com.atlassian.jira.plugi... ] Ondrej Chaloupka moved EAP7-1408 to WFLY-12904: ----------------------------------------------- Project: WildFly (was: EAP 7 Planning Pilot) Key: WFLY-12904 (was: EAP7-1408) Workflow: GIT Pull Request workflow (was: EAP Agile Workflow 2.0) Component/s: Quickstarts Transactions (was: Quickstarts) (was: Transactions) EAP PT Pre-Checked (PC): (was: TODO) EAP PT Community Docs (CD): (was: TODO) EAP PT Product Docs (PD): (was: New) Affects Version/s: 18.0.1.Final (was: 7.3.0.CD18) EAP PT Test Dev (TD): (was: TODO) EAP PT Docs Analysis (DA): (was: TODO) EAP PT Test Plan (TP): (was: TODO) EAP PT Analysis Document (AD): (was: TODO) > Create a quickstart for the ejb remoting and transaction recovery on OpenShift > ------------------------------------------------------------------------------ > > Key: WFLY-12904 > URL: https://issues.redhat.com/browse/WFLY-12904 > Project: WildFly > Issue Type: Task > Components: Quickstarts, Transactions > Affects Versions: 18.0.1.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > As the follow-up to the issue EAP7-1192 we need to have a quickstart which document the necessary steps to setup the OpenShift environment and to show how the scaledown recovery processing works. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-218) server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited

by Ondrej Chaloupka (Jira)

[ https://issues.redhat.com/browse/WFWIP-218?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFWIP-218: ---------------------------------------- Tested with the fix for the WFTC-77 and the eap openshift test passes (at least on my local CRC). Component upgrade for WFTC will be needed. > server scale down keeps data in client's data/ejb-xa-recovery and transactions on client aren't commited > -------------------------------------------------------------------------------------------------------- > > Key: WFWIP-218 > URL: https://issues.redhat.com/browse/WFWIP-218 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Reporter: Martin Simka > Assignee: Ondrej Chaloupka > Priority: Major > > this follows up on WFWIP-206 > While testing tx recovery in OpenShift I see that scale down of pod that has transaction in-doubt on it isn't successful > Scenario: > *ejb client* (app tx-client, pod tx-client-0): > * EJB business method > ** lookup remote EJB > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > ** call remote EJB > *ejb server* (app tx-server, pod tx-server-0): > * EJB business method > ** enlist XA resource 1 to transaction > ** enlist XA resource 2 to transaction > *testTxStatelessServerSecondCommitThrowRmFail* > ejb server XA resource 2 fails with {{XAException(XAException.XAER_RMFAIL)}} > Then the test calls scale down (size from 1 to 0) on tx-server pod. Server scale down completes but sometimes there some records left in {{<JBOSS_HOME>/standalone/data/ejb-xa-recovery}} on tx-client and transactions on client aren't commited. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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