September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4577) Rule containing expired event and additional constraint incorrectly fired

by Mario Fusco (Jira)

[ https://issues.jboss.org/browse/DROOLS-4577?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-4577: -------------------------------- Sprint: 2019 Week 38-40 (from Sep 16) > Rule containing expired event and additional constraint incorrectly fired > ------------------------------------------------------------------------- > > Key: DROOLS-4577 > URL: https://issues.jboss.org/browse/DROOLS-4577 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.27.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > > Migrating a project from Drools 6.5.x to 7.x results in a rule getting fired incorrectly when the following is involved: > * expired event > * additional constraint -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4575?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4575: -------------------------------- Description: If user opens a scesim file and then close it, no confirmation message should be opened h2. Manual Acceptance Test - Opening and closing without changes - Open, change data in cell, close - Open, add column, remove column, change column binding, close - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close was:If user opens a scesim file and then close it, no confirmation message should be opened > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.jboss.org/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > > If user opens a scesim file and then close it, no confirmation message should be opened > h2. Manual Acceptance Test > - Opening and closing without changes > - Open, change data in cell, close > - Open, add column, remove column, change column binding, close > - Open, Change settings on the settings panel (e.g. ruleflow group, kie session), close -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4575) Test Scenario: unsaved changes warning appears even if file has not been changed

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4575?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4575: -------------------------------- Tester: Anna Dupliak > Test Scenario: unsaved changes warning appears even if file has not been changed > -------------------------------------------------------------------------------- > > Key: DROOLS-4575 > URL: https://issues.jboss.org/browse/DROOLS-4575 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Major > Labels: CustomerFocus > > If user opens a scesim file and then close it, no confirmation message should be opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-274) Pre-Java 1 Bytecode has slightly different format which is not accounted for

by Janmm14 Janmm14 (Jira)

Janmm14 Janmm14 created JASSIST-274: --------------------------------------- Summary: Pre-Java 1 Bytecode has slightly different format which is not accounted for Key: JASSIST-274 URL: https://issues.jboss.org/browse/JASSIST-274 Project: Javassist Issue Type: Bug Affects Versions: 3.20.0-GA Reporter: Janmm14 Janmm14 Assignee: Shigeru Chiba Affects bytecode major version 45 and minor version up to 2. https://github.com/ItzSomebody/StopDecompilingMyJava/blob/master/decompil... Example JAR: https://github.com/ItzSomebody/StopDecompilingMyJava/raw/master/decompile... -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4685) The legacy core-feature-pack doesn't install the .well-known/acme-challenge dir

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4685: ---------------------------------------- Summary: The legacy core-feature-pack doesn't install the .well-known/acme-challenge dir Key: WFCORE-4685 URL: https://issues.jboss.org/browse/WFCORE-4685 Project: WildFly Core Issue Type: Bug Components: Build System, Security Affects Versions: 10.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry The WFCORE-3396 feature missed adding the .well-known/acme-challenge directory in the legacy feature pack. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12190) Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config

by Tomasz Adamski (Jira)

[ https://issues.jboss.org/browse/WFLY-12190?page=com.atlassian.jira.plugin... ] Tomasz Adamski reassigned WFLY-12190: ------------------------------------- Assignee: Tomasz Adamski (was: Flavia Rainone) > Reintroduce EJB over HTTP/HTTPS capability with HTTP Loadbalancer - server to server config > ------------------------------------------------------------------------------------------- > > Key: WFLY-12190 > URL: https://issues.jboss.org/browse/WFLY-12190 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Brad Maxwell > Assignee: Tomasz Adamski > Priority: Major > > Wildfly/EAP added EJB over HTTP through load balancer, but we missed adding the ability to configure this server to server in the standalone.xml remoting subsystem like the other EJB server to server configs. > The remoting outbound connection would need an http option , currently it only allows http*-remoting, remote and remote+http*. > {code} > /subsystem=remoting/remote-outbound-connection=remote-ejb-connection:write-attribute(name=protocol, > value=) > http-remoting https-remoting remote remote+http remote+https > {code} > Also, Undertow defaults to http://host:8080/wildfly-services for the provider URL to be used, the remote-outbound-configuration for http would need to be able to accept the path, as the path can be configured to a different path from wildfly-services. It might be good to default to wildfly-services if no path is specified. > {code} > /subsystem=undertow/server=default-server/host=default-host/setting=http-invoker:write-attribute(name=path,value=ejbOverHttp) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4684) The legacy core-feature-pack doesn't install the .well-known/acme-challenge dir

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4684: ---------------------------------------- Summary: The legacy core-feature-pack doesn't install the .well-known/acme-challenge dir Key: WFCORE-4684 URL: https://issues.jboss.org/browse/WFCORE-4684 Project: WildFly Core Issue Type: Bug Components: Build System, Security Affects Versions: 10.0.0.Final Reporter: Brian Stansberry Assignee: Brian Stansberry The WFCORE-3396 feature missed adding the .well-known/acme-challenge directory in the legacy feature pack. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12607) Add Galleon layers testing to testsuite/integration/elytron

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12607?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12607: ----------------------------------------- WFLY-12464 doesn't really 'block' WFLY-12607 but it's the cleanest way of allowing a test to pass in both the normal environment and the Galleon slimmed one. > Add Galleon layers testing to testsuite/integration/elytron > ----------------------------------------------------------- > > Key: WFLY-12607 > URL: https://issues.jboss.org/browse/WFLY-12607 > Project: WildFly > Issue Type: Task > Components: Build System, Security, Test Suite > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Major > > Follow up on the WFLY-12394 work by adding a profile triggered by -Dts.layers to testsuite/integration/elytron. Provision a slimmed server using the test-feature-pack cloud-server layer and execute the portions of the testsuite that are compatible with such a server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12607) Add Galleon layers testing to testsuite/integration/elytron

by Brian Stansberry (Jira)

Brian Stansberry created WFLY-12607: --------------------------------------- Summary: Add Galleon layers testing to testsuite/integration/elytron Key: WFLY-12607 URL: https://issues.jboss.org/browse/WFLY-12607 Project: WildFly Issue Type: Task Components: Build System, Security, Test Suite Reporter: Brian Stansberry Assignee: Brian Stansberry Follow up on the WFLY-12394 work by adding a profile triggered by -Dts.layers to testsuite/integration/elytron. Provision a slimmed server using the test-feature-pack cloud-server layer and execute the portions of the testsuite that are compatible with such a server. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12606) Unable to configure system-jmx module in standalone.xml

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12606?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12606: ----------------------------------------- The org.jboss.as.system-jmx does not provide an extension so adding that element won't work. If what your app needs is just classloading visiblility of the classes in that module, that should be configured in the deployment. See sections 1.5.1 or 1.7 of https://docs.wildfly.org/17/Developer_Guide.html for two ways to do that, either via a Dependencies entry in a MANIFEST.mf or by an entry in a jboss-deployment-structure.xml. > Unable to configure system-jmx module in standalone.xml > ------------------------------------------------------- > > Key: WFLY-12606 > URL: https://issues.jboss.org/browse/WFLY-12606 > Project: WildFly > Issue Type: Bug > Components: Class Loading > Affects Versions: 17.0.1.Final > Reporter: Shashank Singhal > Assignee: Richard Opalka > Priority: Major > Attachments: standalone.xml > > > I am trying to migrate a project from Jboss 4 to wildfly 17 which doesn't have much except JMS queue related stuff. > I am getting following error: > 11:46:53,671 WARN [org.jboss.modules.define] (MSC service thread 1-8) Failed to define class com.XXXXX.ifmbase.controller.IFMController in Module "deployment.ifmdxb-ear.ear.ifmbase-ejb.jar" from Service Module Loader: > java.lang.NoClassDefFoundError: Failed to link XXXXXXXXXX (Module "deployment.ifmdxb-ear.ear.ifmbase-ejb.jar" from Service Module Loader): Failed to link XXXXXXXXXX (Module "deployment.ifmdxb-ear.ear.ifmbase-ejb.jar" from Service Module Loader): org/jboss/system/ServiceMBean > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1095) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:424) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) > at org.jboss.modules.Module.loadModuleClass(Module.java:731) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.base/java.lang.ClassLoader.defineClass1(Native Method) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016) > at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1095) > at org.jboss.modules.ModuleClassLoader.doDefineOrLoadClass(ModuleClassLoader.java:424) > at org.jboss.modules.ModuleClassLoader.defineClass(ModuleClassLoader.java:555) > at org.jboss.modules.ModuleClassLoader.loadClassLocal(ModuleClassLoader.java:339) > at org.jboss.modules.ModuleClassLoader$1.loadClassLocal(ModuleClassLoader.java:126) > at org.jboss.modules.Module.loadModuleClass(Module.java:731) > at org.jboss.modules.ModuleClassLoader.findClass(ModuleClassLoader.java:247) > at org.jboss.modules.ConcurrentClassLoader.performLoadClassUnchecked(ConcurrentClassLoader.java:410) > at org.jboss.modules.ConcurrentClassLoader.performLoadClass(ConcurrentClassLoader.java:398) > at org.jboss.modules.ConcurrentClassLoader.loadClass(ConcurrentClassLoader.java:116) > at java.base/java.lang.Class.forName0(Native Method) > at java.base/java.lang.Class.forName(Class.java:415) > at org.jboss.as.sar@17.0.0.Final//org.jboss.as.service.ReflectionUtils.getClass(ReflectionUtils.java:139) > at org.jboss.as.sar@17.0.0.Final//org.jboss.as.service.ReflectionUtils.getClassHierarchy(ReflectionUtils.java:148) > at org.jboss.as.sar@17.0.0.Final//org.jboss.as.service.ParsedServiceDeploymentProcessor.addServices(ParsedServiceDeploymentProcessor.java:119) > at org.jboss.as.sar@17.0.0.Final//org.jboss.as.service.ParsedServiceDeploymentProcessor.deploy(ParsedServiceDeploymentProcessor.java:109) > at org.jboss.as.server@9.0.1.Final//org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:176) > at org.jboss.msc@1.4.7.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1737) > at org.jboss.msc@1.4.7.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1699) > at org.jboss.msc@1.4.7.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1557) > 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:1363) > at java.base/java.lang.Thread.run(Thread.java:835) > In effort to try fixing this, I was trying to add the system-jmx module in wildfly-17.0.1.Final\modules\system\layers\base\org\jboss\as folder and tried defining it in standalone.xml as follows under extensions: > <extension module="org.jboss.as.system-jmx"/> > That also didn't seem to work out and got error as: > 10:03:09,457 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configurati > on > at org.jboss.as.controller@9.0.2.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143) > at org.jboss.as.server@9.0.2.Final//org.jboss.as.server.ServerService.boot(ServerService.java:385) > at org.jboss.as.controller@9.0.2.Final//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:374) > at java.base/java.lang.Thread.run(Thread.java:835) > Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.jboss.as.system-jmx > at org.jboss.as.controller@9.0.2.Final//org.jboss.as.controller.parsing.DeferredExtensionContext.load(DeferredExtensionContext.java:100) > at org.jboss.as.server@9.0.2.Final//org.jboss.as.server.parsing.StandaloneXml_10.readServerElement(StandaloneXml_10.java:237) > at org.jboss.as.server@9.0.2.Final//org.jboss.as.server.parsing.StandaloneXml_10.readElement(StandaloneXml_10.java:137) > at org.jboss.as.server@9.0.2.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:126) > at org.jboss.as.server@9.0.2.Final//org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:52) > at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122) > at org.jboss.staxmapper@1.3.0.Final//org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76) > at org.jboss.as.controller@9.0.2.Final//org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 2019