May 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12050) WildFly management console fails to load deployments if war fails to deploy

by Philippe Julien (Jira)

[ https://issues.jboss.org/browse/WFLY-12050?page=com.atlassian.jira.plugin... ] Philippe Julien updated WFLY-12050: ----------------------------------- Attachment: Screen Shot 2019-05-06 at 10.37.03 AM.png > WildFly management console fails to load deployments if war fails to deploy > --------------------------------------------------------------------------- > > Key: WFLY-12050 > URL: https://issues.jboss.org/browse/WFLY-12050 > Project: WildFly > Issue Type: Bug > Components: Web Console > Affects Versions: 16.0.0.Final > Reporter: Philippe Julien > Assignee: Harald Pehl > Priority: Major > Attachments: Screen Shot 2019-05-06 at 10.37.03 AM.png > > > When a .war that has servlets declared using @WebServlet fails to deploy, the console cannot list any deployments. > Here is the exception that is logged by WildFly: > {noformat} > 09:52:08.629 [org.jboss.as.controller.management-operation] WFLYCTL0013: Operation ("read-attribute") failed - address: ([ > ("deployment" => "test-war.war"), > ("subsystem" => "undertow"), > ("servlet" => "com.test.TestServlet") > ]): java.lang.IllegalStateException > at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50) > at org.wildfly.extension.undertow.DeploymentServletDefinition$AbstractMetricsHandler$1.execute(DeploymentServletDefinition.java:175) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) > at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) > at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) > at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) > at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) > at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) > at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) > at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) > at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) > at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > 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) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} > I have pushed a small reproducer .war application here: https://github.com/philippejulien/test-war -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12050) WildFly management console fails to load deployments if war fails to deploy

by Philippe Julien (Jira)

Philippe Julien created WFLY-12050: -------------------------------------- Summary: WildFly management console fails to load deployments if war fails to deploy Key: WFLY-12050 URL: https://issues.jboss.org/browse/WFLY-12050 Project: WildFly Issue Type: Bug Components: Web Console Affects Versions: 16.0.0.Final Reporter: Philippe Julien Assignee: Harald Pehl When a .war that has servlets declared using @WebServlet fails to deploy, the console cannot list any deployments. Here is the exception that is logged by WildFly: {noformat} 09:52:08.629 [org.jboss.as.controller.management-operation] WFLYCTL0013: Operation ("read-attribute") failed - address: ([ ("deployment" => "test-war.war"), ("subsystem" => "undertow"), ("servlet" => "com.test.TestServlet") ]): java.lang.IllegalStateException at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:50) at org.wildfly.extension.undertow.DeploymentServletDefinition$AbstractMetricsHandler$1.execute(DeploymentServletDefinition.java:175) at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999) at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743) at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467) at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1412) at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:423) at org.jboss.as.controller.ModelControllerImpl.lambda$execute$1(ModelControllerImpl.java:243) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:289) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:255) at org.jboss.as.controller.ModelControllerImpl.execute(ModelControllerImpl.java:243) at org.jboss.as.domain.http.server.DomainApiHandler.handleRequest(DomainApiHandler.java:212) at io.undertow.server.handlers.encoding.EncodingHandler.handleRequest(EncodingHandler.java:72) at org.jboss.as.domain.http.server.DomainApiCheckHandler.handleRequest(DomainApiCheckHandler.java:93) at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.lambda$handleRequest$0(ElytronIdentityHandler.java:62) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:313) at org.wildfly.security.auth.server.SecurityIdentity.runAs(SecurityIdentity.java:270) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:254) at org.jboss.as.controller.AccessAuditContext.doAs(AccessAuditContext.java:225) at org.jboss.as.domain.http.server.security.ElytronIdentityHandler.handleRequest(ElytronIdentityHandler.java:61) at io.undertow.server.handlers.BlockingHandler.handleRequest(BlockingHandler.java:56) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:364) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:830) at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) 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) at org.jboss.threads.JBossThread.run(JBossThread.java:485) {noformat} I have pushed a small reproducer .war application here: https://github.com/philippejulien/test-war -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12048) outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol

by Wolf-Dieter Fink (Jira)

[ https://issues.jboss.org/browse/WFLY-12048?page=com.atlassian.jira.plugin... ] Wolf-Dieter Fink commented on WFLY-12048: ----------------------------------------- The same can be used for other socket-bindings as there are a number of places in the configuration where this could be benefitial. > outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol > ----------------------------------------------------------------------------------------------------------- > > Key: WFLY-12048 > URL: https://issues.jboss.org/browse/WFLY-12048 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 16.0.0.Final > Reporter: Wolf-Dieter Fink > Assignee: Paul Ferraro > Priority: Major > > JGroups configuration can use two different ways to configure cluster detection > ------ older configuration is via protocol properties -- > <protocol type="TCPPING"> > <property name="initial_hosts">host[7600]</property> > ------ new configuration via socket reference > <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/> > ... > <outbound-socket-binding name="ref-a"> > <remote-destination host="127.0.0.1" port="7600"/> > </outbound-socket-binding> > ----------- > with the old option it is possible to use an expression to set all hosts in a cluster. > The new one need to have all outbound connections listed which is harder to maintain. > As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration. > So a configuration like this would enhance that > <outbound-socket-binding-group> > <outbound-socket-binding name="ref-a"> > <remote-destination host="host1" port="7600"/> > </outbound-socket-binding> > <outbound-socket-binding name="ref-b"> > <remote-destination host="host2" port="7600"/> > </outbound-socket-binding> > </outbound-socket-binding-group> -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12049) outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-12049: --------------------------------------- Summary: outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol Key: WFLY-12049 URL: https://issues.jboss.org/browse/WFLY-12049 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 16.0.0.Final Reporter: Wolf-Dieter Fink Assignee: Paul Ferraro JGroups configuration can use two different ways to configure cluster detection ------ older configuration is via protocol properties -- <protocol type="TCPPING"> <property name="initial_hosts">host[7600]</property> ------ new configuration via socket reference <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/> ... <outbound-socket-binding name="ref-a"> <remote-destination host="127.0.0.1" port="7600"/> </outbound-socket-binding> ----------- with the old option it is possible to use an expression to set all hosts in a cluster. The new one need to have all outbound connections listed which is harder to maintain. As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration. So a configuration like this would enhance that <outbound-socket-binding-group> <outbound-socket-binding name="ref-a"> <remote-destination host="host1" port="7600"/> </outbound-socket-binding> <outbound-socket-binding name="ref-b"> <remote-destination host="host2" port="7600"/> </outbound-socket-binding> </outbound-socket-binding-group> -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12048) outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol

by Wolf-Dieter Fink (Jira)

Wolf-Dieter Fink created WFLY-12048: --------------------------------------- Summary: outbound-socket-binding element should allow grouping to be referenced by JGroups socket-discovery-protocol Key: WFLY-12048 URL: https://issues.jboss.org/browse/WFLY-12048 Project: WildFly Issue Type: Enhancement Components: Clustering Affects Versions: 16.0.0.Final Reporter: Wolf-Dieter Fink Assignee: Paul Ferraro JGroups configuration can use two different ways to configure cluster detection ------ older configuration is via protocol properties -- <protocol type="TCPPING"> <property name="initial_hosts">host[7600]</property> ------ new configuration via socket reference <socket-discovery-protocol type="TCPPING" socket-bindings="ref-a ref-b"/> ... <outbound-socket-binding name="ref-a"> <remote-destination host="127.0.0.1" port="7600"/> </outbound-socket-binding> ----------- with the old option it is possible to use an expression to set all hosts in a cluster. The new one need to have all outbound connections listed which is harder to maintain. As an administrator I want to have the possibility to group the connections and only have one reference and the number of connections can be vary without changing multiple point in the configuration. So a configuration like this would enhance that <outbound-socket-binding-group> <outbound-socket-binding name="ref-a"> <remote-destination host="host1" port="7600"/> </outbound-socket-binding> <outbound-socket-binding name="ref-b"> <remote-destination host="host2" port="7600"/> </outbound-socket-binding> </outbound-socket-binding-group> -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3907) [DMN Designer] (DEV) Add visual indicators for imported Nodes

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3907?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-3907: ------------------------------------------- [~jomarko] Good catch! That's an oversight in my mockup. If possible, I would think we would want there too. > [DMN Designer] (DEV) Add visual indicators for imported Nodes > ------------------------------------------------------------- > > Key: DROOLS-3907 > URL: https://issues.jboss.org/browse/DROOLS-3907 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Michael Anstis > Priority: Major > Labels: UX, UXTeam, drools-tools > Fix For: 7.22.0.Final > > Attachments: Screen Shot 2019-04-17 at 11.55.39 AM.png, read-only-gridC2.png, read-only-gridC2.png > > > Imported models are read-only. We need to show some form of visual indicator for both Nodes (Graph View) and Boxed Expressions (Grid View). Please see the attachments for proposals for the Grid View. > Design Resolution: > * Option C: https://issues.jboss.org/secure/attachment/12449764/read-only-gridC2.png > * Keeping the hover highlight per row cell as is, because when those elements are clicked the Property panel is updated/reflects. > * Use lock icon for canvas nodes: In the components list and in the graph nodes, as illustrated in: https://issues.jboss.org/secure/attachment/12449758/Screen%20Shot%202019-... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2311) tshark/wireshark support

by Bela Ban (Jira)

[ https://issues.jboss.org/browse/JGRP-2311?page=com.atlassian.jira.plugin.... ] Bela Ban resolved JGRP-2311. ---------------------------- Resolution: Done Documentation is at http://www.jgroups.org/manual4/index.html#_analyzing_wire_format_packets > tshark/wireshark support > ------------------------ > > Key: JGRP-2311 > URL: https://issues.jboss.org/browse/JGRP-2311 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Major > Fix For: 4.1.0 > > Attachments: tshark-convert.py > > > 1. Dump contents of wireshark/tahsrk/tcpdump-generated (PCAP) files (using {{ParseMessages}} > 2. Do this dynamically, e.g. `tshark -Tfields -e data` | java ParseMessages > In the second instantiation, ParseMessages would read packets from stdin. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3903) DMN Submarine endpoint codegen

by Matteo Mortari (Jira)

[ https://issues.jboss.org/browse/DROOLS-3903?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-3903: ----------------------------------- Sprint: 2019 Week 20-22 (was: 2019 Week 17-19) > DMN Submarine endpoint codegen > ------------------------------ > > Key: DROOLS-3903 > URL: https://issues.jboss.org/browse/DROOLS-3903 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) [DMN Designer] Data Types tab - Add a nested row to a new Structured data type by default

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Guilherme Gomes commented on DROOLS-3892: ----------------------------------------- [~jomarko] Personally, I see this row as something to _help_ users. But, if they want to remove the added row, they should be allowed to do that. There's nothing in the DMN spec saying that a Structure ~Item Definition~ Data Type _must_ have one field at least. > [DMN Designer] Data Types tab - Add a nested row to a new Structured data type by default > ----------------------------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability enhancement request: Reduce the number of clicks / actions to add a nested element. > Solution description: > When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH > h2. Acceptance criteria > - Create new Structure (/) > - Create nested structure (x) See [comment|https://github.com/kiegroup/kie-wb-common/pull/2621#pullrequestre...] > - Create new Simple Data type (/) > - Create nested Simple Data type (/) > - Remove item from structure (x) -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3978) Create unit tests for submarine-codegen module

by Tibor Zimanyi (Jira)

Tibor Zimanyi created DROOLS-3978: ------------------------------------- Summary: Create unit tests for submarine-codegen module Key: DROOLS-3978 URL: https://issues.jboss.org/browse/DROOLS-3978 Project: Drools Issue Type: Task Reporter: Tibor Zimanyi Assignee: Tibor Zimanyi Fix For: 8.0.0.Final There are no tests in module submarine-codegen. The module should be at least unit tested. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 2 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 May 2019