April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-13405: -------------------------------------- [~algolua7] Is there something special about your environment? Are you by chance using an embedded server? I'm trying to figure out how slf4j would end up on the call stack as jboss-logging should be binding to the jboss-logmanager. When I run this locally I see the following which is still wrong but doesn't break anything: {code} 08:23:45,015 DEBUG [org.jboss.as.connector] (MSC service thread 1-2) Started CommonDeployment %s {code} > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5280) List Filter expression returning single item and nested within arithmetic expression fails to evaluate

by Tracy Hires (Jira)

[ https://issues.redhat.com/browse/DROOLS-5280?page=com.atlassian.jira.plug... ] Tracy Hires updated DROOLS-5280: -------------------------------- Affects Version/s: 7.36.0.Final 7.34.0.Final > List Filter expression returning single item and nested within arithmetic expression fails to evaluate > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5280 > URL: https://issues.redhat.com/browse/DROOLS-5280 > Project: Drools > Issue Type: Bug > Affects Versions: 7.34.0.Final, 7.36.0.Final > Reporter: Tracy Hires > Assignee: Mario Fusco > Priority: Major > Attachments: MySpace_Relation.zip > > > the expression `addend + listOfStructure[field1="some value"].numberField`, where `field1="some value"` filters `listOfStructure` to a single item and `addend` and `numberField` are both non-null numbers, fails to evaluate. It's possible to work around this by placing `listOfStructure[field1="some value"]` into a separate decision. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5280) List Filter expression returning single item and nested within arithmetic expression fails to evaluate

by Tracy Hires (Jira)

[ https://issues.redhat.com/browse/DROOLS-5280?page=com.atlassian.jira.plug... ] Tracy Hires updated DROOLS-5280: -------------------------------- Component/s: dmn engine > List Filter expression returning single item and nested within arithmetic expression fails to evaluate > ------------------------------------------------------------------------------------------------------ > > Key: DROOLS-5280 > URL: https://issues.redhat.com/browse/DROOLS-5280 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.34.0.Final, 7.36.0.Final > Reporter: Tracy Hires > Assignee: Mario Fusco > Priority: Major > Attachments: MySpace_Relation.zip > > > the expression `addend + listOfStructure[field1="some value"].numberField`, where `field1="some value"` filters `listOfStructure` to a single item and `addend` and `numberField` are both non-null numbers, fails to evaluate. It's possible to work around this by placing `listOfStructure[field1="some value"]` into a separate decision. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13405: ----------------------------------------- [~jamezp] No, I didn't try to reproduce; I just saw the fix was obvious but went down the rabbit hole a bit to try and guess why it happened to Alexander but not to tons of people over the last 4-5 years. > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13387) Expose Jaeger Client Metrics

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13387?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFLY-13387: --------------------------------------- Component/s: (was: MP Metrics) Assignee: Emmanuel Hugonnet (was: Jeff Mesnil) [~jmesnil] [~ehugonnet] I'm dropping MP Metrics from this one and changing the assignee. My assumption is anything for this would involve adding standard WildFly management metrics, which then come through MP Metrics the same way all other subsystem metrics do. So nothing specific to MP Metrics about it. > Expose Jaeger Client Metrics > ---------------------------- > > Key: WFLY-13387 > URL: https://issues.redhat.com/browse/WFLY-13387 > Project: WildFly > Issue Type: Feature Request > Components: MP OpenTracing > Reporter: Tobias Stadler > Assignee: Emmanuel Hugonnet > Priority: Major > > I would be nice, if the internal jaeger client metrics could be exposed via mp metrics endpoint. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2474) Messages about dropped queued message when using IpAddressUUID

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2474?page=com.atlassian.jira.plugin... ] Bela Ban commented on JGRP-2474: -------------------------------- {{IpAddressUUID}} has been removed in 5. Reason: nobody ever used it, it added complexity and it was never well tested. I'm reluctant to look into something that has been pulled from the codebase in the next version. If you want readable information, I suggest use {{ExtendedUUID}} or create your own subclass of {{UUID}} that includes a name, so it is visible in the database table. > Messages about dropped queued message when using IpAddressUUID > -------------------------------------------------------------- > > Key: JGRP-2474 > URL: https://issues.redhat.com/browse/JGRP-2474 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.3 > Reporter: Mirko Streckenbach > Assignee: Bela Ban > Priority: Major > Attachments: JGR.java, log-fail-1.txt > > > We upgraded from 4.0.14 to 4.1.8 and ever since then, we had some messages like > {code} > Apr 27, 2020 10:30:54 AM org.jgroups.protocols.UNICAST3 addQueuedMessages > WARNING: i2:1709: dropped queued message i1:1609#2 as its conn_id (0) did not match (entry.conn_id=1) > {code} > when ever an application is restarted. Our setup is as follows (most due to network restrictions): > * Fixed port numbers > * JDBC_PING > * We use IpAddressUUID in order to have a "readable" information in the jgroupsping table > I could track this down to 4.1.2 / 4.1.3: 4.1.2 works as expected, from 4.1.3 I'm seeing the effect observed above. > I attached a simple example that demonstrates the problem: starts two stacks, shuts down the second (non-coordindator) and starts it again after a couple of seconds. With 4.1.2 this works as expected (no warnings), but 4.1.3 and more recent versions (including 4.2.3) produce warnings. The exact behavior is not completely consistent: in most cases, starting the second app again results in some timeouts and the second app becomes a coordinator itself and a merge view is established later (log attached). In some cases it only creates the warnings shown above (this is what we observe in our real application) and in some cases everything works fine. > I don't have any warnings in the log if I don't set an AddressGenerator, but I'd like to avoid this. > While running this on higher debug levels, I observed the following: 4.1.2 will not require an > ACK for the LEAVE_RSP message. 4.1.3 will. The second app sends the ACK, but the coordinator does not seem to receive or process it properly and retransmits the LEAVE_RSP message again and again. This is independent of the AddressGenerator used, -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by James Perkins (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] James Perkins commented on WFLY-13405: -------------------------------------- I definitely think it's strange that the {{Slf4jLocationAwareLogger}} is on the call stack. [~brian.stansberry] were you able to reproduce this? If so can you let me know the steps so I can have a look. > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13405) Update CommonDeploymentService in release.

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13405?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFLY-13405: ------------------------------------ Component/s: JCA > Update CommonDeploymentService in release. > ------------------------------------------ > > Key: WFLY-13405 > URL: https://issues.redhat.com/browse/WFLY-13405 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 19.0.0.Final > Reporter: Alexander Golovko > Assignee: Brian Stansberry > Priority: Major > Attachments: debug.log > > > Current calls of ROOT_LOGGER.debugf("Started/Stopped CommonDeployment %s", new Object[0]); are errors. They raise MissingFormatArgumentException exception since new Object[0] is an empty array and is not compatible with %s in format argument. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-107) Upgrade WildFly Elytron to 1.11.4.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-107?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-107. ------------------------------------- Resolution: Done > Upgrade WildFly Elytron to 1.11.4.Final > --------------------------------------- > > Key: ELYWEB-107 > URL: https://issues.redhat.com/browse/ELYWEB-107 > Project: Elytron Web > Issue Type: Component Upgrade > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELYWEB-106) Release Elytron Web 1.7.1.Final

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/ELYWEB-106?page=com.atlassian.jira.plugi... ] Darran Lofthouse resolved ELYWEB-106. ------------------------------------- Resolution: Done > Release Elytron Web 1.7.1.Final > ------------------------------- > > Key: ELYWEB-106 > URL: https://issues.redhat.com/browse/ELYWEB-106 > Project: Elytron Web > Issue Type: Release > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.7.1.CR1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 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 April 2020