April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-11967) Eliminate deprecated CapabilityServiceTarget.addCapability() usages

by Richard Opalka (Jira)

Richard Opalka created WFLY-11967: ------------------------------------- Summary: Eliminate deprecated CapabilityServiceTarget.addCapability() usages Key: WFLY-11967 URL: https://issues.jboss.org/browse/WFLY-11967 Project: WildFly Issue Type: Enhancement Components: Agroal, EJB, JCA, Mail, MP Health, Transactions, Web (Undertow) Reporter: Richard Opalka Assignee: Richard Opalka Fix For: 17.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11116) Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception)

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-11116?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11116: ------------------------------------- This doesn't make any sense. Are you certain that the HttpSession used by the redirected request is the same as the one used by the servlet that performed the redirect? Verify using HttpSession.getId(); > Wildfly 12.0.0 Final Delay in Getting the Value Attributes of the Session Variables (Result in Null Pointer Exception) > ---------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-11116 > URL: https://issues.jboss.org/browse/WFLY-11116 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 14.0.1.Final, 12.0.0.Final, 13.0.0.Final, 15.0.0.Final > Reporter: ziad saade > Assignee: Paul Ferraro > Priority: Critical > > I have two Servlets Book and BookPreview the attribute is set in Book Servlet as follow: > > Book.java > TestBean testBean=null; > if(session.getAttribute("testBean")!=null) > testBean = (TestBean)session.getAttribute("testBean"); > else{ > testBean=new TestBean(); > session.setAttribute("testBean",testBean); > } > testBean.setAmount("10"); > > response.sendRedirect("BookPreview"); > > > The session attribute can be retrieved and the page is loaded normally and the Amount value is displayed however when submitting the form (Post Action in BookPreview.java) Null Pointer exception is generated. > > BookPreview.java > > TestBean testBean = (TestBean)session.getAttribute("testBean"); > String amount = testBean.getAmount; //Null pointer exception when submitting the form > > <form method="Post" action="BookPreview"> > > </form> > > TestBean.java > > public class TestBean implements java.io.Serializable { > > private static final long serialVersionUID = 1L; > private String amount; > > public String getAmount() { > return amount; > } > > public void setAmount(String amount) { > this.amount = amount; > } > } > > Kindly advice how to fix the problem at the level of the server configuration. > PS: I am not getting the exception when deploying the same application under other J EE application servers (Tomcat....) > > Thanks and Best Regards -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11906) Managed Executor Task Fails with CDI if created from Batchlet

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-11906?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-11906: ----------------------------------- I propsed a fix (see linked PR) that propagates EE concurrency context to batch execution, and with that the demo app passed (first 3 cases). > Managed Executor Task Fails with CDI if created from Batchlet > ------------------------------------------------------------- > > Key: WFLY-11906 > URL: https://issues.jboss.org/browse/WFLY-11906 > Project: WildFly > Issue Type: Bug > Components: Batch, CDI / Weld, Concurrency Utilities > Affects Versions: 16.0.0.Final > Environment: Java 8 > Reporter: Cody Lerum > Assignee: Cheng Fang > Priority: Major > > This previously was working (verified in reproducer) on Wildfly 14.0.1 > Inside of a batchlet if a Managed Executor Task is executed and that Task uses CDI.current() an exception is thrown > {code:java} > 11:00:02,343 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) java.lang.IllegalStateException: WFLYWELD0039: Singleton not set for ModuleClassLoader for Module "org.jboss.as.ee" version 16.0.0.Final from local module loader @78e94dcf (finder: local module finder @233fe9b6 (roots: V:\opt\wildfly-16.0.0.Final\modules,V:\opt\wildfly-16.0.0.Final\modules\system\layers\base)). This means that you are trying to access a weld deployment with a Thread Context ClassLoader that is not associated with the deployment. > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:77) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.services.ModuleGroupSingletonProvider$TCCLSingleton.get(ModuleGroupSingletonProvider.java:134) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.weld.Container.instance(Container.java:57) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.weld.WeldProvider.getCDI(WeldProvider.java:69) > 11:00:02,344 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.lambda$getCDIProvider$0(CDI.java:87) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:174) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.TreeMap$KeySpliterator.tryAdvance(TreeMap.java:2770) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline.forEachWithCancel(ReferencePipeline.java:126) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.copyIntoWithCancel(AbstractPipeline.java:498) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:485) > 11:00:02,345 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.FindOps$FindOp.evaluateSequential(FindOps.java:152) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.stream.ReferencePipeline.findFirst(ReferencePipeline.java:464) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.getCDIProvider(CDI.java:88) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at javax.enterprise.inject.spi.CDI.current(CDI.java:64) > 11:00:02,346 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at com.outjected.demo.DemoTask.run(DemoTask.java:27) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.ee.concurrent.ControlPointUtils$ControlledRunnable.run(ControlPointUtils.java:105) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.FutureTask.run$$$capture(FutureTask.java:266) > 11:00:02,347 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.FutureTask.run(FutureTask.java) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.glassfish.enterprise.concurrent.internal.ManagedFutureTask.run(ManagedFutureTask.java:141) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 11:00:02,348 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at java.lang.Thread.run(Thread.java:748) > 11:00:02,349 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.glassfish.enterprise.concurrent.ManagedThreadFactoryImpl$ManagedThread.run(ManagedThreadFactoryImpl.java:250) > 11:00:02,349 ERROR [stderr] (EE-ManagedExecutorService-default-Thread-1) at org.jboss.as.ee.concurrent.service.ElytronManagedThreadFactory$ElytronManagedThread.run(ElytronManagedThreadFactory.java:85) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-705) Update kiali build job to work with new kiali operator

by Filip Brychta (Jira)

[ https://issues.jboss.org/browse/SWSQE-705?page=com.atlassian.jira.plugin.... ] Filip Brychta commented on SWSQE-705: ------------------------------------- Added https://gitlab.cee.redhat.com/istio/kiali-qe/kiali-qe-utils/merge_requests/2 which should make it work after merge. > Update kiali build job to work with new kiali operator > ------------------------------------------------------ > > Key: SWSQE-705 > URL: https://issues.jboss.org/browse/SWSQE-705 > Project: Kiali QE > Issue Type: QE Task > Reporter: Filip Brychta > Assignee: Filip Brychta > Priority: Critical > Labels: infrastructure > > There is new PR which is enabling kiali operator and removing old bash script which was used for building and deploying kiali. We need to update our jobs to work with this new operator. > https://github.com/kiali/kiali/pull/974 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3875) Executable model - Invalid packages loaded for classpath container

by Olli Johnson (Jira)

[ https://issues.jboss.org/browse/DROOLS-3875?page=com.atlassian.jira.plugi... ] Olli Johnson commented on DROOLS-3875: -------------------------------------- This is a complete blocker for my team trying to convert to the executable model. We must stick with the non-executable model build until we can load our multiple kjar modules into the container correctly. > Executable model - Invalid packages loaded for classpath container > ------------------------------------------------------------------ > > Key: DROOLS-3875 > URL: https://issues.jboss.org/browse/DROOLS-3875 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.19.0.Final, 7.20.0.Final > Reporter: Olli Johnson > Assignee: Luca Molteni > Priority: Blocker > Attachments: drools-classpath-error.zip > > > When building and running a maven multi-module project using several kjar modules the class-path container is incorrect and differs from the container created when not built with the executable model. > See steps to reproduce and attached project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3875) Executable model - Invalid packages loaded for classpath container

by Olli Johnson (Jira)

[ https://issues.jboss.org/browse/DROOLS-3875?page=com.atlassian.jira.plugi... ] Olli Johnson updated DROOLS-3875: --------------------------------- Steps to Reproduce: Create a simple multi-module project like that attached, where there are multiple kjar modules. Build this without the executable model (mvn clean install -DgenerateModel=NO), create the classpath container and print the produced bases and packages. Observe the expected output: {code:java} BASE: modC PACKAGE: olijohns.modC FACTTYPE: olijohns.modC.FactC BASE: modB PACKAGE: olijohns.modB FACTTYPE: olijohns.modB.FactB BASE: modA PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA {code} Repeat the process but with the executable model (-DgenerateModel=YES) and observe the invalid output: {code:java} BASE: modC BASE: modB PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA BASE: modA PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA {code} was: Create a simple multi-module project like that attached, where there are multiple kjar modules. Build this without the executable model (mvn clean install -DgenerateModel=NO), create the classpath container and print the produced bases and packages. Observe the expected output: ``` BASE: modC PACKAGE: olijohns.modC FACTTYPE: olijohns.modC.FactC BASE: modB PACKAGE: olijohns.modB FACTTYPE: olijohns.modB.FactB BASE: modA PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA ``` Repeat the process but with the executable model (-DgenerateModel=YES) and observe the invalid output: ``` BASE: modC BASE: modB PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA BASE: modA PACKAGE: olijohns.modA FACTTYPE: olijohns.modA.FactA ``` > Executable model - Invalid packages loaded for classpath container > ------------------------------------------------------------------ > > Key: DROOLS-3875 > URL: https://issues.jboss.org/browse/DROOLS-3875 > Project: Drools > Issue Type: Bug > Components: executable model > Affects Versions: 7.19.0.Final, 7.20.0.Final > Reporter: Olli Johnson > Assignee: Luca Molteni > Priority: Blocker > Attachments: drools-classpath-error.zip > > > When building and running a maven multi-module project using several kjar modules the class-path container is incorrect and differs from the container created when not built with the executable model. > See steps to reproduce and attached project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3875) Executable model - Invalid packages loaded for classpath container

by Olli Johnson (Jira)

Olli Johnson created DROOLS-3875: ------------------------------------ Summary: Executable model - Invalid packages loaded for classpath container Key: DROOLS-3875 URL: https://issues.jboss.org/browse/DROOLS-3875 Project: Drools Issue Type: Bug Components: executable model Affects Versions: 7.20.0.Final, 7.19.0.Final Reporter: Olli Johnson Assignee: Luca Molteni Attachments: drools-classpath-error.zip When building and running a maven multi-module project using several kjar modules the class-path container is incorrect and differs from the container created when not built with the executable model. See steps to reproduce and attached project. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11933) Error when accessing metrics with RBAC enabled

by Claudio Weiler (Jira)

[ https://issues.jboss.org/browse/WFLY-11933?page=com.atlassian.jira.plugin... ] Claudio Weiler updated WFLY-11933: ---------------------------------- Component/s: Management > Error when accessing metrics with RBAC enabled > ---------------------------------------------- > > Key: WFLY-11933 > URL: https://issues.jboss.org/browse/WFLY-11933 > Project: WildFly > Issue Type: Bug > Components: Management, MP Metrics > Affects Versions: 16.0.0.Final > Reporter: Claudio Weiler > Assignee: Jeff Mesnil > Priority: Critical > > When RBAC is enabled for management in Wildfly 16, metrics throws exception: > java.lang.IllegalStateException: WFLYMETRICS0003: Unable to read attribute XAForgetAverageTime on [ > ("subsystem" => "datasources"), > ("data-source" => "ExampleDS"), > ("statistics" => "pool") > ]: "WFLYCTL0216: Management resource '[ > (\"subsystem\" => \"datasources\"), > (\"data-source\" => \"ExampleDS\"), > (\"statistics\" => \"pool\") > ]' not found". -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4413) Fix backward compatibility issues of javax.api & javax.sql.api modules

by Dennis Reed (Jira)

[ https://issues.jboss.org/browse/WFCORE-4413?page=com.atlassian.jira.plugi... ] Dennis Reed updated WFCORE-4413: -------------------------------- > Fix backward compatibility issues of javax.api & javax.sql.api modules > ---------------------------------------------------------------------- > > Key: WFCORE-4413 > URL: https://issues.jboss.org/browse/WFCORE-4413 > Project: WildFly Core > Issue Type: Bug > Components: Modules > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta3 > > > Modules related commit of WFCORE-3684 issue (commit id b0199c5635186386df3ef7a8c2b7aac37525eee1) > introduced backward compatibility issues of javax.api & javax.sql.api modules > This needs to be fixed. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFWIP-155) WildFly gets stuck with TLSv1.3 on JDK 11

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFWIP-155?page=com.atlassian.jira.plugin.... ] Farah Juma commented on WFWIP-155: ---------------------------------- [~adamkrajcik] Can we close this one now since it was fixed by UNDERTOW-1493? > WildFly gets stuck with TLSv1.3 on JDK 11 > ----------------------------------------- > > Key: WFWIP-155 > URL: https://issues.jboss.org/browse/WFWIP-155 > Project: WildFly WIP > Issue Type: Bug > Components: Security > Environment: JDK 11 > Reporter: Adam Krajcik > Assignee: Farah Juma > Priority: Blocker > Labels: jdk11 > > WildFly gets stuck with when using TLSv1.3. The process starts to heavily use the processor and cannot be stopped by simple SIGINT(Ctrl+C). The issue needs further investigation as no apparent reason for it being stuck. > One possibility is mentioned in the comments for UNDERTOW-1493 is [JDK-8208526|https://bugs.openjdk.java.net/browse/JDK-8208526]. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 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 April 2019