August 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-10859) Upgrade jastow to 2.0.4.Final

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFLY-10859?page=com.atlassian.jira.plugin... ] Ilia Vassilev updated WFLY-10859: --------------------------------- Git Pull Request: (was: https://github.com/wildfly/wildfly/pull/10910) > Upgrade jastow to 2.0.4.Final > ----------------------------- > > Key: WFLY-10859 > URL: https://issues.jboss.org/browse/WFLY-10859 > Project: WildFly > Issue Type: Component Upgrade > Components: Web (Undertow) > Reporter: Ilia Vassilev > Assignee: Stuart Douglas > Labels: downstream_dependency > Fix For: 12.0.0.CR1, 12.0.0.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4040) Deprecate PersistentResourceDefinition.Parameters, remove all uses

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-4040: ---------------------------------------- Summary: Deprecate PersistentResourceDefinition.Parameters, remove all uses Key: WFCORE-4040 URL: https://issues.jboss.org/browse/WFCORE-4040 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry PersistentResourceDefinition.Parameters extends SimpleResourceDefinition.Parameters but doesn't add anything to it, it just overrides and delegates to some superclass methods. But it's a builder kind of API so for every method it doesn't override, the superclass is not returning the subclass type, making it hard to use. The PersistentResourceDefinition can just accept the superclass Parameters. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10630) HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-10630?page=com.atlassian.jira.plugin... ] Stuart Douglas commented on WFLY-10630: --------------------------------------- There is a non spec compliant feature to allow wars in an ear to share a session, so in this case there is only one session per ear. > HttpSessionListener.sessionDestroyed() not called if session invalidated in another WAR > --------------------------------------------------------------------------------------- > > Key: WFLY-10630 > URL: https://issues.jboss.org/browse/WFLY-10630 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.0.0.Final, 13.0.0.Final > Environment: Windows 10, Java 1.8.0_131 > Reproducible with both WildFly-10.0.0.Final and Wildfly-13.0.0.Final > Reporter: Bernhard Kabelka > Assignee: Bartosz Baranowski > Attachments: LoginForm.png, roles.properties, sessionlistener-test.ear, standalone.xml, users.properties > > > For sessions shared across different WARs in a single EAR, the notification of HttpSessionListener works differently in WildFly 10.0.0.Final (and Wildfly 13.0.0.Final) than it it used to work in WildFly 8.2.0.Final: > I have an EAR containing two WARs with enabled session sharing across the WARs. Basically, one WAR contains the web UI, and the other WAR contains the REST interfaces for AJAX calls made by the UI. The user authenticates against the UI-WAR. On logout, a REST method in the AJAX-WAR is triggered which calls HttpSession.invalidate() on the user session. > In WildFly 8.2.0.Final, a HttpSessionListener in the UI-WAR gets notified immediately about session creation and destruction. > In WildFly 13.0.0.Final, however, a HttpSessionListener in either WAR only gets one of the two notifications: > * In the UI-WAR, I get a notification about the created session immediately when the login form is loaded. However, I do not receive any notification about the session destruction (unless it times out). > * In the AJAX-WAR, I do not get any notification about the session creation at all, but I immediately receive a notification about the session destruction. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10353) anonymous authentication for ejbs using legacy configuration - test

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10353?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10353: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/11432 (was: https://github.com/wildfly/wildfly/pull/11205) > anonymous authentication for ejbs using legacy configuration - test > ------------------------------------------------------------------- > > Key: WFLY-10353 > URL: https://issues.jboss.org/browse/WFLY-10353 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 13.0.0.Beta1 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > Create test for https://issues.jboss.org/browse/WFCORE-3826 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9232) mod_cluster decay factor does not support floating-point numerals; decays too quickly

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-9232?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-9232: -------------------------------- Fix Version/s: 14.0.0.Beta2 (was: 14.0.0.CR1) > mod_cluster decay factor does not support floating-point numerals; decays too quickly > ------------------------------------------------------------------------------------- > > Key: WFLY-9232 > URL: https://issues.jboss.org/browse/WFLY-9232 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 11.0.0.Beta1, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.Beta2 > > > Downstream counterpart MODCLUSTER-607. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8364) mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-8364?page=com.atlassian.jira.plugin.... ] James Perkins updated WFLY-8364: -------------------------------- Fix Version/s: 14.0.0.Beta2 (was: 14.0.0.CR1) > mod_cluster model allows both simple- and dynamic-load-providers to be defined in the model simultaneously > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-8364 > URL: https://issues.jboss.org/browse/WFLY-8364 > Project: WildFly > Issue Type: Bug > Components: mod_cluster > Affects Versions: 10.1.0.Final, 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.Beta2 > > > {code} > <subsystem xmlns="urn:jboss:domain:modcluster:3.0"> > <mod-cluster-config advertise-socket="modcluster" connector="ajp"> > <simple-load-provider factor="5"/> > <dynamic-load-provider> > <load-metric type="cpu"/> > </dynamic-load-provider> > </mod-cluster-config> > </subsystem> > {code} > However, it would be ideal if this was reworked into correct resources, like the following: > {{/subsystem=modcluster/proxy=default/load-provider=dynamic}} > {{/subsystem=modcluster/proxy=default/load-provider=simple}} > Jira for that is WFLY-10471. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10848) smallrye-config: Unable to deploy component using automatic converter on injected properties

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10848?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-10848: -------------------------------------- [~jmesnil] I assume this will require a component upgrade. > smallrye-config: Unable to deploy component using automatic converter on injected properties > -------------------------------------------------------------------------------------------- > > Key: WFLY-10848 > URL: https://issues.jboss.org/browse/WFLY-10848 > Project: WildFly > Issue Type: Bug > Components: MP Config > Reporter: Michal Jurc > Assignee: Jeff Mesnil > Priority: Blocker > Fix For: 14.0.0.CR1 > > > MicroProfile Configuration specification states the following: > {quote}Automatic Converters > If no built-in nor custom Converter for a requested Type T, an implicit Converter is automatically > provided if the following conditions are met: > • The target type \{@code T\} has a \{@code public static T of(String)\} method, or > • The target type \{@code T\} has a \{@code public static T valueOf(String)\} method, or > • The target type \{@code T\} has a public Constructor with a String parameter, or > • The target type \{@code T\} has a \{@code public static T parse(CharSequence)\} method{quote} > Consider deploying an application with the following injected property: > {code} @Inject > @ConfigProperty(name = "convertedOne", defaultValue = "2007-12-03T10:15:30") > LocalDateTime localDateTimeProperty;{code} > Deployment of such application fails with the following: > {code:title=jboss-cli}[standalone@localhost:9990 /] deploy ~/testing/mock-artifacts/smallrye-config-playground/ejb-smallrye-config/server/target/server.jar > {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFacto > ryService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}}}} > {code} > {code:title=server.log}12:46:19,263 ERROR [stderr] (MSC service thread 1-5) org.jboss.weld.exceptions.DeploymentException: WELD-001408: Unsatisfied dependencies for type LocalDateTime with qualifiers @ConfigProperty > 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at injection point [BackedAnnotatedField] @Inject @ConfigProperty ejb.HelloBean.localDateTimeProperty > 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) at ejb.HelloBean.localDateTimeProperty(HelloBean.java:0) > 12:46:19,263 ERROR [stderr] (MSC service thread 1-5) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPointForDeploymentProblems(Validator.java:378) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateInjectionPoint(Validator.java:290) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateGeneralBean(Validator.java:143) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateRIBean(Validator.java:164) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.Validator.validateBean(Validator.java:526) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:64) > 12:46:19,264 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.bootstrap.ConcurrentValidator$1.doWork(ConcurrentValidator.java:62) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:62) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.weld.executor.IterativeWorkerTaskFactory$1.call(IterativeWorkerTaskFactory.java:55) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at java.lang.Thread.run(Thread.java:748) > 12:46:19,265 ERROR [stderr] (MSC service thread 1-5) at org.jboss.threads.JBossThread.run(JBossThread.java:485) > 12:46:19,270 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: org.jboss.msc.service.StartException in service jboss.deployment.unit."server.jar".CdiValidatorFactoryService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1728) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1556) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378) > at java.lang.Thread.run(Thread.java:748) > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED > at org.jboss.weld.bean.builtin.BeanManagerProxy.checkContainerState(BeanManagerProxy.java:234) > at org.jboss.weld.bean.builtin.BeanManagerProxy.getReference(BeanManagerProxy.java:85) > at org.jboss.as.weld.CdiValidatorFactoryService.getReference(CdiValidatorFactoryService.java:122) > at org.jboss.as.weld.CdiValidatorFactoryService.start(CdiValidatorFactoryService.java:83) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1736) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1698) > ... 6 more > 12:46:19,288 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 1) WFLYCTL0013: Operation ("deploy") failed - address: ({"deployment" => "server.jar"}) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}} > 12:46:19,289 ERROR [org.jboss.as.server] (management-handler-thread - 1) WFLYSRV0021: Deploy of deployment "server.jar" was rolled back with the following failure message: > {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"server.jar\".CdiValidatorFactoryService" => "Failed to start service > Caused by: org.jboss.weld.exceptions.IllegalStateException: WELD-001332: BeanManager method getReference() is not available during application initialization. Container state: DEPLOYED"}} > {code} > This failure is not produced if the automatically converted property is optional. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10440) Upgrade mod_cluster to 1.4.0.Final

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10440?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10440: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Upgrade mod_cluster to 1.4.0.Final > ---------------------------------- > > Key: WFLY-10440 > URL: https://issues.jboss.org/browse/WFLY-10440 > Project: WildFly > Issue Type: Component Upgrade > Components: mod_cluster > Affects Versions: 13.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 14.0.0.CR1 > > > Tag https://github.com/modcluster/mod_cluster/tree/1.4.0.Final -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10404) Review/revise 2lc caching design

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10404?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10404: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Review/revise 2lc caching design > -------------------------------- > > Key: WFLY-10404 > URL: https://issues.jboss.org/browse/WFLY-10404 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, JPA / Hibernate > Affects Versions: 13.0.0.Beta1 > Reporter: Scott Marlow > Assignee: Paul Ferraro > Fix For: 14.0.0.CR1 > > > Review cache isolation, cache region factories, override ISPN default behavior to handle more efficient names, updates to infinispan-hibernate-cache-spi, app configuration choices for choosing different strategies. > * Avoid the ByteString byte length limitation of 255 ([https://github.com/infinispan/infinispan/commit/046517fc0829bb0a1768169e5...]) in region name prefix + region name as cache key. Also see [https://issues.jboss.org/browse/ISPN-9206]. > * Enhance the org.jboss.as.jpa.hibernate5.service.WildFlyCustomRegionFactoryInitiator to improve caching for: > ** container managed persistence units > ** non-container-managed persistence unit (e.g. native Hibernate or app calls into javax.persistence.Persistence.createEntityManagerFactory()) > ** WildFlyCustomRegionFactoryInitiator cannot start an Infinispan cache by default, should we offer an API/SPI that Spring could implement for specifying the cache (service) to be used for a particular persistence unit? The application could specify the custom API/SPI implementation class via a persistence unit property. > *** Currently, Hibernate defaults the 2lc on but that fails when the Infinispan cache is not automatically started, so WildFlyCustomRegionFactoryInitiator defaults caching off. > *** If this is not possible, then keep the current WildFlyCustomRegionFactoryInitiator logic to default Hibernate caching off, unless the app requests caching via configuration settings. > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10320) Upgrade artemis from 1.5.x to 2.x.x

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFLY-10320?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-10320: --------------------------------- Fix Version/s: 14.0.0.CR1 (was: 14.0.0.Beta2) > Upgrade artemis from 1.5.x to 2.x.x > ----------------------------------- > > Key: WFLY-10320 > URL: https://issues.jboss.org/browse/WFLY-10320 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Erich Duda > Assignee: Jeff Mesnil > Priority: Blocker > Labels: blocker-WF14, feature-branch-blocker > Fix For: 14.0.0.CR1 > > > As the summary of this Jira hints, this is an umbrella Jira for tracking all issues related to the upgrade of Artemis component from version 1.x to 2.x. > The issues were identified after running tests against following pull request - https://github.com/wildfly/wildfly/pull/10641 > This PR integrates Artemis 2.4.0 in WildFly master branch -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 August 2018