January 2021 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5512) Unsaved changes dialog for a Test Scenario executed right after creation

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5512?page=com.atlassian.jira.plug... ] Jozef Marko updated DROOLS-5512: -------------------------------- Fix Version/s: 7.49.0.Final > Unsaved changes dialog for a Test Scenario executed right after creation > ------------------------------------------------------------------------ > > Key: DROOLS-5512 > URL: https://issues.redhat.com/browse/DROOLS-5512 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.41.0.Final > Reporter: Jan Stastny > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > Fix For: 7.49.0.Final > > > There is once again an Unsaved Changes dialog presented to user even though no changes has been made. > This time it is when user creates Test Scenario, fills in facts and values, saves and executes the test scenario right away. When clicking save and trying to close again it does not appear again. There us not commit in niogit connected with the second save. > When user closes and reopens editor between save and run, all works fine. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (AG-154) Connection leak when DB connection closed during transaction rollback

by Wojciech Kopciewicz (Jira)

[ https://issues.redhat.com/browse/AG-154?page=com.atlassian.jira.plugin.sy... ] Wojciech Kopciewicz commented on AG-154: ---------------------------------------- Hi [~lbarreiro], Any updates on this? This starts to become blocking for us. > Connection leak when DB connection closed during transaction rollback > --------------------------------------------------------------------- > > Key: AG-154 > URL: https://issues.redhat.com/browse/AG-154 > Project: Agroal > Issue Type: Bug > Components: narayana, pool > Affects Versions: 1.9 > Reporter: Wojciech Kopciewicz > Assignee: Luis Barreiro > Priority: Major > > We are using Quarkus 1.9.2 with Hibernate and Agroal to access PostgreSQL DB. > It looks like Agroal is leaking connections when connection is closed (somewhere) on the server side during transaction rollback. > The following log was observed: > Error trying to transactionRollback local transaction: This connection has been closed. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14006) Consider having the Extension implementation for extensions with deprecated subsystems register themselves as such

by Yeray Borges Santana (Jira)

[ https://issues.redhat.com/browse/WFLY-14006?page=com.atlassian.jira.plugi... ] Yeray Borges Santana reassigned WFLY-14006: ------------------------------------------- Assignee: Yeray Borges Santana > Consider having the Extension implementation for extensions with deprecated subsystems register themselves as such > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-14006 > URL: https://issues.redhat.com/browse/WFLY-14006 > Project: WildFly > Issue Type: Task > Components: Management > Reporter: Brian Stansberry > Assignee: Yeray Borges Santana > Priority: Minor > > ExtensionContext.registerSubsystem has an overloaded variant that takes a boolean 'deprecated' parameter. We never use it. > For deprecated subsystems we *perhaps* should. > I think most of our deprecated subsystems are using the SimpleResourceDefinition.setDeprecated API to trigger deprecation logging if the subsystem is actually added. So this extension call really is just for the case where the extension is included in the config but is not used for adding a subsystem. That's kind of a corner case so it's a valid question whether we want to add this setting and end up writing *two* messages to the log. > So this issue is to track at least considering it. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5247: ---------------------------------------------- [~soul2zimate], thank-you very much for sharing your findings, [~parsharma] will surely benefit from it! > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Parul Sharma > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Chao Wang (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Chao Wang commented on WFCORE-5247: ----------------------------------- OK, I will put my found below and leave the fix and test to [~parsharma]. This looks a general issue as it not only limits to the {{system-property}} address. For example, below commands reproduce same exception. {code:xml} [standalone@localhost:9990 /] cd subsystem [standalone@localhost:9990 system-property] read-attribute TAB {code} https://github.com/wildfly/wildfly-core/blob/master/cli/src/main/java/org... looks not right, in case of {{node.getName()}} is null, it tries to set {{null}} as ModelNode value. > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Parul Sharma > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Jean Francois Denise reassigned WFCORE-5247: -------------------------------------------- Assignee: Parul Sharma (was: Jean Francois Denise) > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Parul Sharma > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5247) IllegalArgumentException and CLI crash with read-attribute in /system-property

by Jean Francois Denise (Jira)

[ https://issues.redhat.com/browse/WFCORE-5247?page=com.atlassian.jira.plug... ] Jean Francois Denise commented on WFCORE-5247: ---------------------------------------------- [~soul2zimate], [~parsharma] is starting to look into it as her first WF issue! I need to change the assignee. > IllegalArgumentException and CLI crash with read-attribute in /system-property > ------------------------------------------------------------------------------ > > Key: WFCORE-5247 > URL: https://issues.redhat.com/browse/WFCORE-5247 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 14.0.0.Final > Reporter: David Le Borgne > Assignee: Jean Francois Denise > Priority: Major > Attachments: stack_trace.txt > > > Pressing TAB after typing "read-attribute " in /system-property displays a java.lang.IllegalArgumentException: newValue is null message and exits JBoss CLI. > > {{/opt/wildfly/bin/jboss-cli.sh --connect}} > {{[standalone@localhost:9990 /] cd /system-property}} > {{[standalone@localhost:9990 system-property] read-attribute <TAB>}} > {{Exception in thread "CLI Terminal Connection (uninterruptable)" java.lang.IllegalArgumentException: newValue is null}} -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5254) Kernel domain-management module has a couple OSHs populating the runtime with data from the operation, not the model

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-5254: ---------------------------------------- Summary: Kernel domain-management module has a couple OSHs populating the runtime with data from the operation, not the model Key: WFCORE-5254 URL: https://issues.redhat.com/browse/WFCORE-5254 Project: WildFly Core Issue Type: Bug Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry LegacyConfigurationChangeResourceDefinition and InMemoryAuditLogHandlerResourceDefinition populate the runtime from the operation. They should populate from the Resource tree's model. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-3307) Parameters passed to standalone.sh are not printed on startup

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFCORE-3307?page=com.atlassian.jira.plug... ] James Perkins closed WFCORE-3307. --------------------------------- Resolution: Rejected The parameters passed to scripts, with very few exceptions, are not processed by the script itself. They are passed to the main entry point and processed there after the JVM has been started. With the example {{-Djboss.socket.binding.port-offset=100}} that is not passed to the JVM in the {{JAVA_OPTS}}. That is passed to the entry point in the {{org.jboss.as.standalone}} module. > Parameters passed to standalone.sh are not printed on startup > ------------------------------------------------------------- > > Key: WFCORE-3307 > URL: https://issues.redhat.com/browse/WFCORE-3307 > Project: WildFly Core > Issue Type: Enhancement > Components: Scripts > Affects Versions: 3.0.3.Final, 8.0.0.Beta5 > Environment: linux / windows > Reporter: jamie smith > Assignee: James Perkins > Priority: Minor > > Parameters passed to standalone.sh should also be printed on startup (like JAVA_OPTS). > Actually I think something like the output of `ps aux | grep "org.jboss.as.standalone"` should also be printed, when jboss starts. > Not printing them causes confusion between what is printed and what is actually applied. > If for example someone runs this: `standalone.sh -Djboss.socket.binding.port-offset=100` and at the same time `-Djboss.socket.binding.port-offset=0` exists in JAVA_OPTS, then the latter will be printed but the first will be used. > Someone might argue about setting only JAVA_OPTS before running standalone.sh. > The reason I avoid setting JAVA_OPTS is that if I set them before running standalone.sh, then the default Wildfly opts (-Djava.net.preferIPv4Stack=true" -Djboss.modules.system.pkgs=$JBOSS_MODULES_SYSTEM_PKGS -Djava.awt.headless=true") are never used, which causes other problems. This could be a bug byitself, but for now I consider it as expected behaviour. > So the most clean approach that I see for setting options in a single place (both with -D and custom flags (e.g. -b)) is appending them as params to standalone.sh (e.g. inside a wrapper script myapp-run.sh). > It should be possible however to be able to see them being printed somewhere. -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14355) Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly

by Roberto Oliveira (Jira)

[ https://issues.redhat.com/browse/WFLY-14355?page=com.atlassian.jira.plugi... ] Roberto Oliveira updated WFLY-14355: ------------------------------------ Affects Version/s: 22.0.0.Final > Move missing MP Opentracing and MP REST Client licenses from wildfly-ee to wildfly > ---------------------------------------------------------------------------------- > > Key: WFLY-14355 > URL: https://issues.redhat.com/browse/WFLY-14355 > Project: WildFly > Issue Type: Task > Affects Versions: 22.0.0.Final > Reporter: Roberto Oliveira > Assignee: Roberto Oliveira > Priority: Major > > Jira WFLY-14148 moved MicroProfile Opentracing from wildfly-ee to wildfly but the following licenses missed to be moved: jaeger-core, jaeger-thrift, microprofile-opentracing-api > Jira WFLY-14156 moved MicroProfile REST Client from wildfly-ee to wildly but the following licenses missed to be moved: microprofile-rest-client-api, resteasy-client-microprofile -- This message was sent by Atlassian Jira (v8.13.1#813001)

3 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira January 2021