September 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13887) Add http-connections element to jboss-ejb-client_1_4.xsd schema

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13887?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-13887: ------------------------------ Description: Need to add the new element to jboss-ejb-client_1_4.xsd schema: {code:xml} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> <client-context default-compression="-1"> <http-connections> <http-connection uri="http://localhost:8180/wildfly-services"/> </http-connections> </client-context> </jboss-ejb-client> {code} Also need to update jboss-ejb-client.adoc to reflect the new element. This element (http-connections) is already implemented as part of WFLY-12190 EJB over HTTP discovery configuration. was: Need to add the new element to jboss-ejb-client_1_4.xsd schema: {code:xml} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> <client-context default-compression="-1"> <http-connections> <http-connection uri="http://localhost:8180/wildfly-services"/> </http-connections> </client-context> </jboss-ejb-client> {code} Also need to update jboss-ejb-client.adoc to reflect the new element. > Add http-connections element to jboss-ejb-client_1_4.xsd schema > --------------------------------------------------------------- > > Key: WFLY-13887 > URL: https://issues.redhat.com/browse/WFLY-13887 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > Need to add the new element to jboss-ejb-client_1_4.xsd schema: > {code:xml} > <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> > <client-context default-compression="-1"> > <http-connections> > <http-connection uri="http://localhost:8180/wildfly-services"/> > </http-connections> > </client-context> > </jboss-ejb-client> > {code} > Also need to update jboss-ejb-client.adoc to reflect the new element. > This element (http-connections) is already implemented as part of WFLY-12190 EJB over HTTP discovery configuration. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13887) Add http-connections element to jboss-ejb-client_1_4.xsd schema

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13887?page=com.atlassian.jira.plugi... ] Cheng Fang updated WFLY-13887: ------------------------------ Description: Need to add the new element to jboss-ejb-client_1_4.xsd schema: {code:xml} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> <client-context default-compression="-1"> <http-connections> <http-connection uri="http://localhost:8180/wildfly-services"/> </http-connections> </client-context> </jboss-ejb-client> {code} Also need to update jboss-ejb-client.adoc to reflect the new element. was: Need to add the new element to jboss-ejb-client_1_4.xsd schema: {code:xml} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> <client-context default-compression="-1"> <http-connections> <http-connection uri="http://localhost:8180/wildfly-services"/> </http-connections> </client-context> </jboss-ejb-client> {code} Also need to update jboss-ejb-client.adoc to reflect the new element. > Add http-connections element to jboss-ejb-client_1_4.xsd schema > --------------------------------------------------------------- > > Key: WFLY-13887 > URL: https://issues.redhat.com/browse/WFLY-13887 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > > Need to add the new element to jboss-ejb-client_1_4.xsd schema: > {code:xml} > <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> > <client-context default-compression="-1"> > <http-connections> > <http-connection uri="http://localhost:8180/wildfly-services"/> > </http-connections> > </client-context> > </jboss-ejb-client> > {code} > Also need to update jboss-ejb-client.adoc to reflect the new element. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13887) Add http-connections element to jboss-ejb-client_1_4.xsd schema

by Cheng Fang (Jira)

Cheng Fang created WFLY-13887: --------------------------------- Summary: Add http-connections element to jboss-ejb-client_1_4.xsd schema Key: WFLY-13887 URL: https://issues.redhat.com/browse/WFLY-13887 Project: WildFly Issue Type: Bug Components: EJB Affects Versions: 21.0.0.Beta1 Reporter: Cheng Fang Assignee: Cheng Fang Need to add the new element to jboss-ejb-client_1_4.xsd schema: {code:xml} <jboss-ejb-client xmlns="urn:jboss:ejb-client:1.4"> <client-context default-compression="-1"> <http-connections> <http-connection uri="http://localhost:8180/wildfly-services"/> </http-connections> </client-context> </jboss-ejb-client> {code} Also need to update jboss-ejb-client.adoc to reflect the new element. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4923) read-resource operation does not resolve expressions recursively

by Sweta Patra (Jira)

[ https://issues.redhat.com/browse/WFCORE-4923?page=com.atlassian.jira.plug... ] Sweta Patra updated WFCORE-4923: -------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/4337 (was: https://github.com/wildfly/wildfly-core/pull/4297) > read-resource operation does not resolve expressions recursively > ---------------------------------------------------------------- > > Key: WFCORE-4923 > URL: https://issues.redhat.com/browse/WFCORE-4923 > Project: WildFly Core > Issue Type: Bug > Components: Management > Affects Versions: 12.0.0.Beta1 > Reporter: Tamás Ábele > Assignee: Jeff Mesnil > Priority: Major > Attachments: hal-error1.png, hal-error2.png > > > The problem affects all versions. The wildfly controller does not resolve expression resursively which causes improper behaviour of the jbos CLI. > {code:json} > [standalone@localhost:9992 /] /subsystem=batch-jberet:read-resource(include-runtime=true,recursive=true,resolve-expressions=true) > { > "outcome" => "success", > "result" => { > "restart-jobs-on-resume" => true, > "security-domain" => undefined, > "default-job-repository" => "in-memory", > "default-thread-pool" => "batch", > "in-memory-job-repository" => {"in-memory" => {}}, > "jdbc-job-repository" => undefined, > "thread-factory" => undefined, > "thread-pool" => {"batch" => { > "active-count" => 0, > "completed-task-count" => 0L, > "current-thread-count" => 0, > "keepalive-time" => { > "time" => 30L, > "unit" => "SECONDS" > }, > "largest-thread-count" => 0, > "max-threads" => expression "${batch-max-threads}", > "name" => "batch", > "queue-size" => 0, > "rejected-count" => 0, > "task-count" => 0L, > "thread-factory" => undefined > }} > } > } > {code} > The missing recursive expression resolvation also causes runtime errors in the wildfly console (HAL) if you use properties your configuration XML-s (standalone.xml, domain.xml, ...) Two examples can be found in the attachements. > The solution would be only adding the > {code:java} > rrOp.get(ModelDescriptionConstants.RESOLVE_EXPRESSIONS).set(resolve); > {code} > line after > {code:java} > rrOp.get(ModelDescriptionConstants.INCLUDE_DEFAULTS).set(defaults); > {code} > in the doExecuteInternal method of the > \controller\src\main\java\org\jboss\as\controller\operations\global\ReadResourceHandler.java > The wildfly console (HAL) source code is also buggy, which when creates an operation like this > {code:java} > Operation operation = new Operation.Builder(address, READ_RESOURCE_OPERATION) > {code} > in several places I found does not contain the line > {code:java} > .param(RESOLVE_EXPRESSIONS, true) > {code} > and this will cause unresolved expressions to be returned and later numeric error to be thrown while trying to read them. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13802) The undertow layer can not deploy deployments without the ee layer

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFLY-13802?page=com.atlassian.jira.plugi... ] Darran Lofthouse commented on WFLY-13802: ----------------------------------------- Need to re-review this issue. Depending on EE is not wanted as it is hard to remove dependencies later. What can this layer really be used for? Can we make it fail cleanly if used for more than is supported? The Undertow DUPs pre-date capabilities by a long way so a simple check may be possible to fail at least cleanly or offer some kind of minimal support. > The undertow layer can not deploy deployments without the ee layer > ------------------------------------------------------------------ > > Key: WFLY-13802 > URL: https://issues.redhat.com/browse/WFLY-13802 > Project: WildFly > Issue Type: Bug > Components: Build System, Web (Undertow) > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 21.0.0.Final > > > {code:java} > 16:35:06,234 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-8) MSC000001: Failed to start service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: org.jboss.msc.service.StartException in service jboss.deployment.unit."simple-webapp.war".undertow-deployment.UndertowDeploymentInfoService: Failed to start service > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1731) > at org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1990) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.lang.Thread.run(Thread.java:748) > Caused by: java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50) > at org.jboss.as.ee.component.ComponentRegistry.createInstanceFactory(ComponentRegistry.java:76) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.createServletConfig(UndertowDeploymentInfoService.java:709) > at org.wildfly.extension.undertow.deployment.UndertowDeploymentInfoService.start(UndertowDeploymentInfoService.java:276) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > ... 6 more > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13886) Remoting outbound channels are not closed

by Pankaj Narkhede (Jira)

Pankaj Narkhede created WFLY-13886: -------------------------------------- Summary: Remoting outbound channels are not closed Key: WFLY-13886 URL: https://issues.redhat.com/browse/WFLY-13886 Project: WildFly Issue Type: Bug Components: Remoting Affects Versions: 20.0.1.Final, 18.0.1.Final Reporter: Pankaj Narkhede Assignee: Flavia Rainone We are seeing below issue in Wildfly 18 and 20 which is blocking our migration from wildfly10 but not seeing same issue in wildfly10. It seems similar issue has been opened in JBEAP, https://issues.redhat.com/browse/JBEAP-18322 Suppressed: org.jboss.remoting3.ProtocolException: Too many channels open at org.jboss.remoting3.remote.RemoteConnectionHandler.handleOutboundChannelOpen(RemoteConnectionHandler.java:194) at org.jboss.remoting3.remote.RemoteConnectionHandler.open(RemoteConnectionHandler.java:335) at org.jboss.remoting3.ConnectionImpl.openChannel(ConnectionImpl.java:109) at org.jboss.remoting3.ClientServiceHandle.getClientService(ClientServiceHandle.java:80) -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13885) org.jboss.as.test.integration.web.sharedsession.SharedSessionTestCase should test non-distributed session manager

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-13885: ----------------------------------- Summary: org.jboss.as.test.integration.web.sharedsession.SharedSessionTestCase should test non-distributed session manager Key: WFLY-13885 URL: https://issues.redhat.com/browse/WFLY-13885 Project: WildFly Issue Type: Bug Components: Test Suite Affects Versions: 21.0.0.Beta1 Reporter: Paul Ferraro Assignee: Paul Ferraro This test should be updated to use the latest shared-session-config schema which allows an application to indicate whether to use a distributed session manager or not. This test should explicitly test the non-distributed behavior. We have separate tests that validate distributed behavior. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5209) Missing value replacement does not work correctly in new PMML regression model

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5209?page=com.atlassian.jira.plug... ] Gabriele Cardosi closed DROOLS-5209. ------------------------------------ > Missing value replacement does not work correctly in new PMML regression model > ------------------------------------------------------------------------------ > > Key: DROOLS-5209 > URL: https://issues.redhat.com/browse/DROOLS-5209 > Project: Drools > Issue Type: Bug > Affects Versions: 7.35.0.Final > Reporter: Jiri Petrlik > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Missing value replacement does not work correctly in new PMML regression model. See reproducer in "MissingDataRegressionTest". PR with test can be found here: https://github.com/kiegroup/drools/pull/2835 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5209) Missing value replacement does not work correctly in new PMML regression model

by Gabriele Cardosi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5209?page=com.atlassian.jira.plug... ] Gabriele Cardosi updated DROOLS-5209: ------------------------------------- Labels: TrustyAI (was: ) > Missing value replacement does not work correctly in new PMML regression model > ------------------------------------------------------------------------------ > > Key: DROOLS-5209 > URL: https://issues.redhat.com/browse/DROOLS-5209 > Project: Drools > Issue Type: Bug > Affects Versions: 7.35.0.Final > Reporter: Jiri Petrlik > Assignee: Gabriele Cardosi > Priority: Major > Labels: TrustyAI > > Missing value replacement does not work correctly in new PMML regression model. See reproducer in "MissingDataRegressionTest". PR with test can be found here: https://github.com/kiegroup/drools/pull/2835 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13790) Memory leak caused by org.eclipse.yasson.internal.JsonBinding

by Ahcene Kessal (Jira)

[ https://issues.redhat.com/browse/WFLY-13790?page=com.atlassian.jira.plugi... ] Ahcene Kessal commented on WFLY-13790: -------------------------------------- The change resolves the issue. I will provide more details tomorrow as it is getting a bit late here. Thank you. > Memory leak caused by org.eclipse.yasson.internal.JsonBinding > ------------------------------------------------------------- > > Key: WFLY-13790 > URL: https://issues.redhat.com/browse/WFLY-13790 > Project: WildFly > Issue Type: Bug > Components: REST > Affects Versions: 20.0.1.Final > Reporter: Ahcene Kessal > Assignee: r searls > Priority: Major > > org.eclipse.yasson.internal.JsonBinding keeps a reference on an enum after the war is undeployed which results in a classloader leak. > 1- Deploy the following application: > > {code:java} > package au.com.spatiumxl.model; > public class Book { > public enum Status { READ, UNREAD } > private String title; > private Book.Status status; > public Book(String title) { > this.title = title; > this.status = Book.Status.UNREAD; > } > public String getTitle() { > return title; > } > public Book.Status getStatus() { > return status; > } > } > {code} > > {code:java} > package au.com.spatiumxl.ejb; > [...] > import au.com.spatiumxl.model.Book; > @Stateless > @LocalBean > public class BookService { > public List<Book> getBooks() { > List<Book> books = new ArrayList<>(); > books.add(new Book("title1")); > return books; > } > } > {code} > > {code:java} > package au.com.spatiumxl.rest; > [...] > import au.com.spatiumxl.ejb.BookService; > import au.com.spatiumxl.model.Book; > @RequestScoped > @Path("")public > class BookEndPoint { > @Inject BookService bookService; > @GET @Path("/get-books") > @Produces("application/json") > public List<Book> getBooks() { > return bookService.getBooks(); > } > } > {code} > > 2- On the browser go to: http://<host>/<context-root>/.../get-books > 3- Undeploy the war > 4- The memory analyser shows: > {code:java} > java.lang.Thread > org.jboss.modules.ModuleClassLoader > org.jboss.modules.Module > org.jboss.modules.LocalModuleLoader > java.util.concurrent.ConcurrentHashMap > java.util.concurrent.ConcurrentHashMap$Node[] > java.util.concurrent.ConcurrentHashMap$Node > org.jboss.modules.ModuleLoader$FutureModule > org.jboss.modules.Module > org.jboss.modules.ModuleClassLoader > java.util.Vector > java.lang.Object[] > org.jboss.resteasy.plugins.providers.jsonb.AbstractJsonBindingProvider > org.eclipse.yasson.internal.JsonBinding > org.eclipse.yasson.internal.JsonbContext > org.eclipse.yasson.internal.MappingContext > java.util.concurrent.ConcurrentHashMap > java.util.concurrent.ConcurrentHashMap$Node[] > java.util.concurrent.ConcurrentHashMap$Node > org.eclipse.yasson.internal.model.ClassModel > org.eclipse.yasson.internal.model.PropertyModel[] > org.eclipse.yasson.internal.model.PropertyModel > au.com.spatiumxl.model.Book$Status > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 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 2020