December 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (DROOLS-5883) GDT editor generates wrong DRL if operator 'contains' is used with string literal containing space

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-5883?page=com.atlassian.jira.plug... ] Jozef Marko moved RHPAM-3340 to DROOLS-5883: -------------------------------------------- Project: Drools (was: Red Hat Process Automation Manager) Key: DROOLS-5883 (was: RHPAM-3340) Workflow: GIT Pull Request workflow (was: CDW with docs v1) Docs QE Status: NEW Component/s: Guided Decision Table Editor (was: Business Central) Affects Version/s: 7.47.0.Final (was: 7.9.0.GA) QE Status: NEW > GDT editor generates wrong DRL if operator 'contains' is used with string literal containing space > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-5883 > URL: https://issues.redhat.com/browse/DROOLS-5883 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.47.0.Final > Reporter: Jozef Marko > Assignee: Toni Rikkola > Priority: Major > Labels: guided_decision_table, support > > Guided Decision Table editor generate wrong DRL when using 'contains' operator with a string literal containing space., which causes evaluation/build error like. > [KBase: defaultKieBase]: [ERR 102] Line 7:45 mismatched input ')' in rule "Row 1 rule2" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13949) JNDI lookup for JMS Queue failing

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13949?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet closed WFLY-13949. ------------------------------------ Resolution: Done > JNDI lookup for JMS Queue failing > --------------------------------- > > Key: WFLY-13949 > URL: https://issues.redhat.com/browse/WFLY-13949 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 20.0.1.Final > Reporter: Francis Griffin > Assignee: Emmanuel Hugonnet > Priority: Major > Attachments: dpsrTest.tgz, dpsrTest.tgz, dpsrTest.tgz > > > I have a JMS app which has been running successfully under WF10 for some years. I'm trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK is OpenJDK 11. > I've tried to make the reproducible case as simple as possible. The server is unpacked from the downloaded tar.gz, and is not modified except to add a guest user for JMS (which is not needed for the reproducible case, since we never actually create a Connection). The queue is the DLQ queue defined in the distribution. > The error is a NameNotFoundException: > Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203) > at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123) > at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.base/java.lang.Thread.run(Thread.java:834) > No matter what queue name I use, the lookup is failing on the string jms/queue rather than the expected jms/queue/DLQ. > I fully expect that this is some stupid error on my part, something I'm looking at and just not seeing, because I know of others (albeit using Windows) who are using 20.0.1.Final for the full app without issue. But I can't for the life of me see what it is. > Tha actual full application looks up a ConnectionFactory of "jms/RemoteConnectionFactory" and creates Connections and Sessions before looking up the Queue name. The lookup for the factory name works perfectly, as does the other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown above. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (ELY-2051) No acceptedIssuers is sent when CRLs are configured

by David MAFFRAND (Jira)

[ https://issues.redhat.com/browse/ELY-2051?page=com.atlassian.jira.plugin.... ] David MAFFRAND commented on ELY-2051: ------------------------------------- Bugs seems located to org.wildfly.extension.elytron.SSLDefinitions of wildfly-core, after : {code:java} builder.setTrustStore(keyStore); builder.setTrustManagerFactory(trustManagerFactory); {code} There's no call to builder.setAcceptedIssuers > No acceptedIssuers is sent when CRLs are configured > --------------------------------------------------- > > Key: ELY-2051 > URL: https://issues.redhat.com/browse/ELY-2051 > Project: WildFly Elytron > Issue Type: Bug > Components: Authentication Mechanisms > Affects Versions: 1.12.1.Final > Reporter: David MAFFRAND > Priority: Major > > When CRLs are configured there're no client certificate CA names sent for a tls 2 way connexion. > Method setAcceptedIssuers of X509RevocationTrustManager builder is never called, so acceptedIssuers is always empty. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13949) JNDI lookup for JMS Queue failing

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13949?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13949: ------------------------------------------ The name is wrong, you should use /subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:jboss/exported/jms/queue/test1"]) instead of /subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:{color:#de350b}*/*{color}jboss/exported/jms/queue/test1"]) and your test works > JNDI lookup for JMS Queue failing > --------------------------------- > > Key: WFLY-13949 > URL: https://issues.redhat.com/browse/WFLY-13949 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 20.0.1.Final > Reporter: Francis Griffin > Assignee: Emmanuel Hugonnet > Priority: Major > Attachments: dpsrTest.tgz, dpsrTest.tgz, dpsrTest.tgz > > > I have a JMS app which has been running successfully under WF10 for some years. I'm trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK is OpenJDK 11. > I've tried to make the reproducible case as simple as possible. The server is unpacked from the downloaded tar.gz, and is not modified except to add a guest user for JMS (which is not needed for the reproducible case, since we never actually create a Connection). The queue is the DLQ queue defined in the distribution. > The error is a NameNotFoundException: > Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193) > at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189) > at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203) > at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123) > at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430) > at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.base/java.lang.Thread.run(Thread.java:834) > No matter what queue name I use, the lookup is failing on the string jms/queue rather than the expected jms/queue/DLQ. > I fully expect that this is some stupid error on my part, something I'm looking at and just not seeing, because I know of others (albeit using Windows) who are using 20.0.1.Final for the full app without issue. But I can't for the life of me see what it is. > Tha actual full application looks up a ConnectionFactory of "jms/RemoteConnectionFactory" and creates Connections and Sessions before looking up the Queue name. The lookup for the factory name works perfectly, as does the other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown above. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5218) Upgrade JBoss Remoting to 5.0.20.Final

by Flavia Rainone (Jira)

[ https://issues.redhat.com/browse/WFCORE-5218?page=com.atlassian.jira.plug... ] Flavia Rainone moved JBEAP-20665 to WFCORE-5218: ------------------------------------------------ Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-5218 (was: JBEAP-20665) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.5.GA) > Upgrade JBoss Remoting to 5.0.20.Final > -------------------------------------- > > Key: WFCORE-5218 > URL: https://issues.redhat.com/browse/WFCORE-5218 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Flavia Rainone > Assignee: Ilia Vassilev > Priority: Major > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFWIP-366) MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run

by Martin Choma (Jira)

Martin Choma created WFWIP-366: ---------------------------------- Summary: MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase failing in bootable jar run Key: WFWIP-366 URL: https://issues.redhat.com/browse/WFWIP-366 Project: WildFly WIP Issue Type: Bug Reporter: Martin Choma Assignee: Kabir Khan {code} mvn clean install -B -fae -Dmaven.test.failure.ignore=true -Dts.bootable -Dtestsuite.ee.galleon.pack.version=22.0.0.Beta1-SNAPSHOT -Dtestsuite.ee.galleon.pack.artifactId=wildfly-galleon-pack -Dtestsuite.ee.galleon.pack.groupId=org.wildfly -Dversion.org.wildfly.jar.plugin=2.0.2.Final -Dtest=MicroProfileMetricsSecuredEndpointTestCase,MicroProfileVendorMetricsBootTestCase ... [INFO] Results: [INFO] [ERROR] Failures: [ERROR] MicroProfileMetricsSecuredEndpointTestCase.securedHTTPEndpoint:89 expected:<200> but was:<401> [ERROR] MicroProfileVendorMetricsBootTestCase.testVendorMetricsDeployAfterBoot:159->checkResponse:188 connected=true cleanInit=true overallResponseCode=401 overallSawVendor=false scopedResponseCode=401 scopedSawVendor=false expected:<[200]> but was:<[401]> [INFO] [ERROR] Tests run: 3, Failures: 2, Errors: 0, Skipped: 0 {code} Looking into tested bootable jar It seems strange I still see security-enabled="false" {code} <subsystem xmlns="urn:wildfly:microprofile-metrics-smallrye:2.0" security-enabled="false" exposed-subsystems="*" prefix="${wildfly.metrics.prefix:wildfly}"/> {code} and mgmt-users.properties is empty no user expected by test "testSuite", "testSuitePassword" -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (DROOLS-5853) Rule relationship analysis core : convert model into graph

by Toshiya Kobayashi (Jira)

[ https://issues.redhat.com/browse/DROOLS-5853?page=com.atlassian.jira.plug... ] Toshiya Kobayashi updated DROOLS-5853: -------------------------------------- Story Points: 7 (was: 4) > Rule relationship analysis core : convert model into graph > ---------------------------------------------------------- > > Key: DROOLS-5853 > URL: https://issues.redhat.com/browse/DROOLS-5853 > Project: Drools > Issue Type: Feature Request > Components: core engine > Affects Versions: 7.46.0.Final > Reporter: Toshiya Kobayashi > Assignee: Toshiya Kobayashi > Priority: Major > > Convert model into navigable graph which is the basis of visualization (regardless of visualization methods). > See https://github.com/mariofusco/drools-impact-analysis -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14171) Upgrade jbossws-spi from 3.3.0.Final to 3.3.1.Final

by Jim Ma (Jira)

Jim Ma created WFLY-14171: ----------------------------- Summary: Upgrade jbossws-spi from 3.3.0.Final to 3.3.1.Final Key: WFLY-14171 URL: https://issues.redhat.com/browse/WFLY-14171 Project: WildFly Issue Type: Component Upgrade Components: Web Services Affects Versions: 22.0.0.Alpha1 Reporter: Jim Ma Assignee: Jim Ma Fix For: 22.0.0.Beta1 Upgrade jbossws-spi from 3.3.0.Final to 3.3.1.Final to fix some jakarta ee9 tck failures. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14170) Remove wildfly-ee and wildfly-servlet feature pack's dependency on the wildfly-core feature pack

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14170: --------------------------------------- Summary: Remove wildfly-ee and wildfly-servlet feature pack's dependency on the wildfly-core feature pack Key: WFLY-14170 URL: https://issues.redhat.com/browse/WFLY-14170 Project: WildFly Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 22.0.0.Beta1 Have the wildfly-ee and wildfly-servlet feature packs incorporate the source used for the wildfly-core feature pack instead of having a feature pack dependency. As the relevant source is in a different git repo, use GAL-319 to incorporate the source. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 7 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-14169) Remove wildfly-ee feature pack dependency on wildfly-servlet

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-14169: --------------------------------------- Summary: Remove wildfly-ee feature pack dependency on wildfly-servlet Key: WFLY-14169 URL: https://issues.redhat.com/browse/WFLY-14169 Project: WildFly Issue Type: Task Components: Build System Reporter: Brian Stansberry Assignee: Brian Stansberry Fix For: 22.0.0.Beta1 Have the wildfly-ee feature pack share source with the wildfly-servlet feature pack instead of having a feature pack dependency. As the relevant source is in the same git repo as the wildfly-ee fp's maven module this source sharing would be via maven resource plugin copying during the build, not via GAL-319. -- This message was sent by Atlassian Jira (v7.13.8#713008)

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