July 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-4143) Embed CLI failures on IBM jdk - checkLogging

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4143?page=com.atlassian.jira.plugi... ] James Perkins reassigned WFCORE-4143: ------------------------------------- Assignee: James Perkins > Embed CLI failures on IBM jdk - checkLogging > -------------------------------------------- > > Key: WFCORE-4143 > URL: https://issues.jboss.org/browse/WFCORE-4143 > Project: WildFly Core > Issue Type: Bug > Components: Test Suite > Environment: IBM JDK > {noformat} > java version "1.8.0_181" > Java(TM) SE Runtime Environment (build 8.0.5.20 - pxa6480sr5fp20-20180802_01(SR5 FP20)) > IBM J9 VM (build 2.9, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20180731_393394 (JIT enabled, AOT enabled) > OpenJ9 - bd23af8 > OMR - ca1411c > IBM - 98805ca) > JCL - 20180719_01 based on Oracle jdk8u181-b12 > {noformat} > Reporter: Petr Kremensky > Assignee: James Perkins > Priority: Major > > {{testLogging}} for Cli tests in Wildfly-core testsuite fails on IBM JDK. > *reproduce* > cd wildfly-core/testsuite > mvn clean test -fae -Dts.manualmode -pl manualmode,standalone -Dtest=CLIEmbedHostControllerTestCase,CLIEmbedServerTestCase,SilentModeTestCase > ... > [ERROR] Failures: > [ERROR] SilentModeTestCase.testLogging:99->checkIfEmpty:152 > [INFO] > [ERROR] Tests run: 3, Failures: 1, Errors: 0, Skipped: 0 > ... > [ERROR] Failures: > [ERROR] CLIEmbedHostControllerTestCase.testHelp:321->checkLogging:744 > [ERROR] CLIEmbedHostControllerTestCase.testStdOutDefault:160->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 > [ERROR] CLIEmbedHostControllerTestCase.testStdOutDiscard:166->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 > [ERROR] CLIEmbedHostControllerTestCase.testStdOutEcho:172->stdoutTest:188->checkClientSideLogging:231->checkLogging:744 > [ERROR] CLIEmbedServerTestCase.testHelp:543->checkLogging:764 > [ERROR] CLIEmbedServerTestCase.testStdOutDefault:196->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 > [ERROR] CLIEmbedServerTestCase.testStdOutDiscard:202->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 > [ERROR] CLIEmbedServerTestCase.testStdOutEcho:208->stdoutTest:224->checkClientSideLogging:267->checkLogging:764 > [INFO] > [ERROR] Tests run: 51, Failures: 8, Errors: 0, Skipped: 0 > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-163) WildFlyServerStatus is not present in operator description

by Jeff Mesnil (Jira)

[ https://issues.jboss.org/browse/WFWIP-163?page=com.atlassian.jira.plugin.... ] Jeff Mesnil resolved WFWIP-163. ------------------------------- Resolution: Done Fixed by https://github.com/wildfly/wildfly-operator/issues/30 in upstream project > WildFlyServerStatus is not present in operator description > ----------------------------------------------------------- > > Key: WFWIP-163 > URL: https://issues.jboss.org/browse/WFWIP-163 > Project: WildFly WIP > Issue Type: Bug > Components: OpenShift > Environment: *openshift:* {{v3.11.82}} > *operator image:* {{quay.io/wildfly/wildfly-operator:0.2.0}} > *runtime image:* {{quay.io/wildfly/wildfly-centos7:17.0}} > *application image:* {{pkremens/simple-jaxrs-wildfly}} > Reporter: Petr Kremensky > Assignee: Jeff Mesnil > Priority: Blocker > Attachments: wildfly-operator.txt > > > According to the [operator api documentation|https://github.com/wildfly/wildfly-operator/blob/master/doc...], the deployment pods status should be pard of operator description, but I failed to find such on OCP. > Install the wildfly operator on OCP as described by [wildfly-operator - openshift|https://github.com/wildfly/wildfly-operator#openshift] section. > *steps to reproduce* > {noformat} > $ cat << EOF > simple-jaxrs-wildfly.yaml > apiVersion: wildfly.org/v1alpha1 > kind: WildFlyServer > metadata: > name: simple-jaxrs-wildfly > spec: > applicationImage: "pkremens/simple-jaxrs-wildfly" > size: 2 > EOF > $ oc apply -f simple-jaxrs-wildfly.yaml > $ oc expose service/simple-jaxrs-wildfly-loadbalancer > # verify that application is accessible > $ ROUTE=$(oc get route.route.openshift.io/simple-jaxrs-wildfly-loadbalancer --template='{{ .spec.host }}') > $ curl $ROUTE/ping > pong > $ oc describe wildflyserver simple-jaxrs-wildfly > Name: simple-jaxrs-wildfly > Namespace: myproject > Labels: <none> > Annotations: kubectl.kubernetes.io/last-applied-configuration={"apiVersion":"wildfly.org/v1alpha1","kind":"WildFlyServer","metadata":{"annotations":{},"name":"simple-jaxrs-wildfly","namespace":"myproject"},"spec":... > API Version: wildfly.org/v1alpha1 > Kind: WildFlyServer > Metadata: > Creation Timestamp: 2019-07-02T13:11:58Z > Generation: 1 > Resource Version: 4318 > Self Link: /apis/wildfly.org/v1alpha1/namespaces/myproject/wildflyservers/simple-jaxrs-wildfly > UID: f8eb76bf-9cca-11e9-b8ee-52540043aed8 > Spec: > Application Image: pkremens/simple-jaxrs-wildfly > Size: 2 > Events: <none> > {noformat} > Operator status is not part of the object. > For wildfly operator pod logs see [^wildfly-operator.txt] attachment. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4553) Logging on IBM Java doesn't create log

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4553?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-4553: --------------------------------------- Good catch [~mkopecky]. You're probably correct and I'll test that locally and see if I can't get that issue resolved as well with this fix. > Logging on IBM Java doesn't create log > -------------------------------------- > > Key: WFCORE-4553 > URL: https://issues.jboss.org/browse/WFCORE-4553 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Environment: * IBM Java 1.8 > * RHEL6 & RHEL7 > Reporter: Vratislav Marek > Assignee: James Perkins > Priority: Major > > On application output found: > {code} > Bad level value for property: handler.CLIFILE.level > {code} > handler.CLIFILE.level is the name of a property from the test property file used in standalone testsuite > Stack trace: > {code} > java.lang.AssertionError > at org.junit.Assert.fail(Assert.java:86) > at org.junit.Assert.assertTrue(Assert.java:41) > at org.junit.Assert.assertTrue(Assert.java:52) > at org.jboss.as.test.integration.management.cli.SilentModeTestCase.checkIfEmpty(SilentModeTestCase.java:152) > at org.jboss.as.test.integration.management.cli.SilentModeTestCase.testLogging(SilentModeTestCase.java:99) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) > at java.lang.reflect.Method.invoke(Method.java:508) > at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50) > at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12) > at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47) > at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17) > at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) > at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26) > at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109) > at org.junit.runners.Suite.runChild(Suite.java:128) > at org.junit.runners.Suite.runChild(Suite.java:27) > at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290) > at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71) > at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288) > at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58) > at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268) > at org.junit.runners.ParentRunner.run(ParentRunner.java:363) > at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83) > at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75) > at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158) > at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383) > at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344) > at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417) > {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10057) EJB subsystem configure max threads and core threads independently

by Cheng Fang (Jira)

[ https://issues.jboss.org/browse/WFLY-10057?page=com.atlassian.jira.plugin... ] Cheng Fang commented on WFLY-10057: ----------------------------------- Analysis document proposal: https://github.com/wildfly/wildfly-proposals/pull/227 > EJB subsystem configure max threads and core threads independently > ------------------------------------------------------------------ > > Key: WFLY-10057 > URL: https://issues.jboss.org/browse/WFLY-10057 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Affects Versions: 12.0.0.Final > Reporter: Richard Janik > Assignee: Cheng Fang > Priority: Major > > EJB3 subsystem currently only allows setting the {{max-threads}}, not {{core-threads}}. > {noformat} > [standalone@localhost:9990 /] /subsystem=ejb3/thread-pool=default:write-attribute(name= > keepalive-time max-threads thread-factory > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1525) When SSO is enabled, multipart form and form enconding stop working.

by Darran Lofthouse (Jira)

[ https://issues.jboss.org/browse/ELY-1525?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1525: --------------------------------------- Do you have any further information regarding how the MultiPartParserDefinition is breaking the data? Is their a bug in the parser definition or is it definitely the case we are using the wrong definition? > When SSO is enabled, multipart form and form enconding stop working. > -------------------------------------------------------------------- > > Key: ELY-1525 > URL: https://issues.jboss.org/browse/ELY-1525 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.6.Final, 1.2.1.Final > Reporter: Estevão Freitas > Assignee: Darran Lofthouse > Priority: Critical > Fix For: 1.10.0.CR3 > > Attachments: 0001-ELY-1525-Initialize-FormParserFactory-with-FormEncod.patch, ely-1515-reproducer.zip > > > I developed a JSF application with "h:inputFile" component and it requires a form with " enctype="multipart/form-data" ". > I use this tutorial for SSO: https://docs.jboss.org/author/display/WFLY/Web+Single+Sign-On . > When I execute the last step: " /subsystem=undertow/application-security-domain=other/setting=single-sign-on:add(key-store=example-keystore, key-alias=localhost, domain=localhost, credential-reference=clear-text=secret}) ", all commandButtons stop working. > If I remove the "h:inputFile" component and " enctype="multipart/form-data" " from form all buttons works again, but all words with accents are corrupted. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4243) Test Scenario: rule scenarios with maps of simple types are failing

by Emily Murphy (Jira)

[ https://issues.jboss.org/browse/DROOLS-4243?page=com.atlassian.jira.plugi... ] Emily Murphy commented on DROOLS-4243: -------------------------------------- [~kkufova] please review the section in the release notes: [RHPAM draft|http://file.ork.redhat.com/~emmurphy/rhpam-7.4-rn/] [RHDM draft|http://file.ork.redhat.com/~emmurphy/rhdm-7.4-rn/] > Test Scenario: rule scenarios with maps of simple types are failing > ------------------------------------------------------------------- > > Key: DROOLS-4243 > URL: https://issues.jboss.org/browse/DROOLS-4243 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > > Create a map of simple type as value (i.e. Map<String, String>) and try to use it -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4259) Scenario can not access parent data object fields

by Emily Murphy (Jira)

[ https://issues.jboss.org/browse/DROOLS-4259?page=com.atlassian.jira.plugi... ] Emily Murphy commented on DROOLS-4259: -------------------------------------- [~aashishdalmia] thanks. I've updated. Please review the draft: [RHPAM draft|http://file.ork.redhat.com/~emmurphy/rhpam-7.4-rn/] [RHDM draft|http://file.ork.redhat.com/~emmurphy/rhdm-7.4-rn/] > Scenario can not access parent data object fields > ------------------------------------------------- > > Key: DROOLS-4259 > URL: https://issues.jboss.org/browse/DROOLS-4259 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.24.0.Final > Reporter: Jozef Marko > Assignee: Daniele Zonca > Priority: Critical > Labels: ScenarioSimulation, rhpam74releasenote > Attachments: Screenshot from 2019-06-26 08-56-23.png, inheritance.zip > > > Scenario Designer can not access parent data object fields, even if the field has public getter and setter. If you check the attached project there are two fields - *price* and *size* while *size* is declared in parent class. If you try to run the scenario, error about not possible initialization of the data object appears. > If you move the *size* field from *Picture* into *Advertisement* class and rerun the scenario, everything works fine. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13

by Scott Marlow (Jira)

[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-12063: ------------------------------------- [~gbadner] Has Hibernate 5.3.10 seen any reports of this failure with ByteBuddy? > ClassFormatError on JDK13 > ------------------------- > > Key: WFLY-12063 > URL: https://issues.jboss.org/browse/WFLY-12063 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Richard Opalka > Assignee: Scott Marlow > Priority: Critical > Labels: blocker-WF18 > Attachments: server.log, test.log > > > The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly. > Affected tests are: > --- > [ERROR] Errors: > [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment > [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment > [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment > [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment > [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment > [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy... > [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment > [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment > [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment > [INFO] > [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14 > --- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12184) WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12184?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka commented on WFLY-12184: ----------------------------------------- [~kabirkhan] thanks! :0) I created a PR for this issue. > WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12184 > URL: https://issues.jboss.org/browse/WFLY-12184 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The ejb over http (aka. InitialContext lookup using the {{http://}} protocol) should be working fine (see https://issues.jboss.org/browse/WFLY-5029) but the transaction propagation does not work as the http-client provider is not integrated with WFTC. > The integration needs to be fixed. A naive way of fixing this is here: > https://github.com/ochaloup/wildfly/commit/e8e011b9597113a6fd80e9c2b26004... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12184) WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls

by Ondrej Chaloupka (Jira)

[ https://issues.jboss.org/browse/WFLY-12184?page=com.atlassian.jira.plugin... ] Ondrej Chaloupka updated WFLY-12184: ------------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/12420 > WFTC is not integrated with http-client and transaction propagation does not work for server to server ejb over HTTP calls > -------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12184 > URL: https://issues.jboss.org/browse/WFLY-12184 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 17.0.0.Final > Reporter: Ondrej Chaloupka > Assignee: Ondrej Chaloupka > Priority: Major > > The ejb over http (aka. InitialContext lookup using the {{http://}} protocol) should be working fine (see https://issues.jboss.org/browse/WFLY-5029) but the transaction propagation does not work as the http-client provider is not integrated with WFTC. > The integration needs to be fixed. A naive way of fixing this is here: > https://github.com/ochaloup/wildfly/commit/e8e011b9597113a6fd80e9c2b26004... -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 10 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 July 2019