September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9339) Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9339?page=com.atlassian.jira.plugin.... ] Brian Stansberry edited comment on WFLY-9339 at 9/11/17 11:38 PM: ------------------------------------------------------------------ Fix is at https://github.com/wildfly/wildfly/compare/master...bstansberry:WFLY-9339... but I won't send up a PR until I correct the core issue I mentioned in the description. That fix is at https://github.com/wildfly/wildfly-core/pull/2793 was (Author: brian.stansberry): Fix is at https://github.com/wildfly/wildfly/compare/master...bstansberry:WFLY-9339... but I won't send up a PR until I correct the core issue I mentioned in the description. > Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9339 > URL: https://issues.jboss.org/browse/WFLY-9339 > Project: WildFly > Issue Type: Bug > Components: JCA, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > UndertowTransformersTestCase isn't setting up the AdditionalInitialization on the legacy controller side so the boot ops fail due to missing capabilities. > DatasourcesSubsystemTestCase in one test is using a config with an enum value the legacy hosts can't understand, and in another it's not correcting a rejected value causing the test to fail when it continues. > Simple fixes, although the undertow one has revealed issues in how core deals with legacy controllers that will have to be corrected before the tests can pass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9339) Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9339?page=com.atlassian.jira.plugin.... ] Brian Stansberry commented on WFLY-9339: ---------------------------------------- Fix is at https://github.com/wildfly/wildfly/compare/master...bstansberry:WFLY-9339... but I won't send up a PR until I correct the core issue I mentioned in the description. > Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed > ------------------------------------------------------------------------------------------------ > > Key: WFLY-9339 > URL: https://issues.jboss.org/browse/WFLY-9339 > Project: WildFly > Issue Type: Bug > Components: JCA, Web (Undertow) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > UndertowTransformersTestCase isn't setting up the AdditionalInitialization on the legacy controller side so the boot ops fail due to missing capabilities. > DatasourcesSubsystemTestCase in one test is using a config with an enum value the legacy hosts can't understand, and in another it's not correcting a rejected value causing the test to fail when it continues. > Simple fixes, although the undertow one has revealed issues in how core deals with legacy controllers that will have to be corrected before the tests can pass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9339) Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed

by Brian Stansberry (JIRA)

Brian Stansberry created WFLY-9339: -------------------------------------- Summary: Datasource and Undertow transformer tests have bugs that are revealed when WFCORE-3259 is fixed Key: WFLY-9339 URL: https://issues.jboss.org/browse/WFLY-9339 Project: WildFly Issue Type: Bug Components: JCA, Web (Undertow) Reporter: Brian Stansberry Assignee: Brian Stansberry UndertowTransformersTestCase isn't setting up the AdditionalInitialization on the legacy controller side so the boot ops fail due to missing capabilities. DatasourcesSubsystemTestCase in one test is using a config with an enum value the legacy hosts can't understand, and in another it's not correcting a rejected value causing the test to fail when it continues. Simple fixes, although the undertow one has revealed issues in how core deals with legacy controllers that will have to be corrected before the tests can pass. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4919) Jandex backward compatibility issue

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-4919?page=com.atlassian.jira.plugin.... ] Jason Greene resolved WFLY-4919. -------------------------------- Resolution: Out of Date I think this one was resolved awhile back, reopen if its still an issue > Jandex backward compatibility issue > ----------------------------------- > > Key: WFLY-4919 > URL: https://issues.jboss.org/browse/WFLY-4919 > Project: WildFly > Issue Type: Bug > Reporter: Alessio Soldano > Assignee: Jason Greene > > Starting few days ago, I'm seeing a regression in JBossWS testsuite caused by the latest upgrade of Jandex in WFLY. > The exception on server log says: > {noformat} > 2015-07-14 00:28:09,492 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."jaxws-samples-wsse-policy-trust-sts-holderofkey.war".INSTALL: org.jboss.msc.service.StartException in service jboss.deployment.unit."jaxws-samples-wsse-policy-trust-sts-holderofkey.war".INSTALL: WFLYSRV0153: Failed to process phase INSTALL of deployment "jaxws-samples-wsse-policy-trust-sts-holderofkey.war" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948) > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0024: Could not configure component TestSecurityTokenService > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:96) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156) > ... 5 more > Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYEE0058: No matching field found for 'ObjectType' > at org.jboss.as.ee.component.FieldInjectionTarget.getField(FieldInjectionTarget.java:82) > at org.jboss.as.ee.component.FieldInjectionTarget.isStatic(FieldInjectionTarget.java:61) > at org.jboss.as.ee.component.AbstractComponentConfigurator.mergeInjectionsForClass(AbstractComponentConfigurator.java:80) > at org.jboss.as.ee.component.DefaultComponentConfigurator$1.handle(DefaultComponentConfigurator.java:78) > at org.jboss.as.ee.component.ClassDescriptionTraversal.run(ClassDescriptionTraversal.java:54) > at org.jboss.as.ee.component.DefaultComponentConfigurator.configure(DefaultComponentConfigurator.java:80) > at org.jboss.as.ee.component.deployers.EEModuleConfigurationProcessor.deploy(EEModuleConfigurationProcessor.java:82) > ... 6 more > {noformat} > JBossWS install scripts overwrites some libraries in WildFly modules, including Apache CXF jars. In particular, the cxf-rt-ws-security-jandex jar is replaced with one generated by the jbossws build, which currently relies on Jandex 1.0.3.Final (but I've tried with 1.1.0.Final too, same issue). > I tried moving to the same Jandex version that's in WildFly (2.0.0.Beta3) and replacing the cxf-rt-ws-security-jandex jar only and that solves the problem. > Now, I can likely modify the jbossws build to use different jandex versions depending on the target container, but I wonder if this is some kind of backward compatiblity issue that needs to be dealt with more in general on the WildFly side. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9337) servlet container has no UTF-8 encoding default set, produces garbage on form submissions

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-9337?page=com.atlassian.jira.plugin.... ] Stuart Douglas commented on WFLY-9337: -------------------------------------- Browsers do not generally send an encoding when performing form submission, which is why the default is used. If you do not want to rely on the Servlet containers default it is up to you to set the request encoding before the data is parsed. > servlet container has no UTF-8 encoding default set, produces garbage on form submissions > ----------------------------------------------------------------------------------------- > > Key: WFLY-9337 > URL: https://issues.jboss.org/browse/WFLY-9337 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Mr Gruust > Assignee: Stuart Douglas > > The problem described over there https://stackoverflow.com/questions/31205287/encoding-servlets-with-utf-8... still exists with the latest release. I had to explicitly set UTF-8 as default encoding to make resteasy properly decode form submissions and not decode UTF-8 as latin-1 (at least it looks a lot like that to me). > On top of that, persisting session ids to file store (without using <distributable/> in web.xml) tends to lose the session store when reloading the (unmanaged) webapp too fast during development. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9337) servlet container has no UTF-8 encoding default set, produces garbage on form submissions

by Mr Gruust (JIRA)

[ https://issues.jboss.org/browse/WFLY-9337?page=com.atlassian.jira.plugin.... ] Mr Gruust closed WFLY-9337. --------------------------- Resolution: Rejected > servlet container has no UTF-8 encoding default set, produces garbage on form submissions > ----------------------------------------------------------------------------------------- > > Key: WFLY-9337 > URL: https://issues.jboss.org/browse/WFLY-9337 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Mr Gruust > Assignee: Stuart Douglas > > The problem described over there https://stackoverflow.com/questions/31205287/encoding-servlets-with-utf-8... still exists with the latest release. I had to explicitly set UTF-8 as default encoding to make resteasy properly decode form submissions and not decode UTF-8 as latin-1 (at least it looks a lot like that to me). > On top of that, persisting session ids to file store (without using <distributable/> in web.xml) tends to lose the session store when reloading the (unmanaged) webapp too fast during development. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9337) servlet container has no UTF-8 encoding default set, produces garbage on form submissions

by Mr Gruust (JIRA)

[ https://issues.jboss.org/browse/WFLY-9337?page=com.atlassian.jira.plugin.... ] Mr Gruust reopened WFLY-9337: ----------------------------- > servlet container has no UTF-8 encoding default set, produces garbage on form submissions > ----------------------------------------------------------------------------------------- > > Key: WFLY-9337 > URL: https://issues.jboss.org/browse/WFLY-9337 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Mr Gruust > Assignee: Stuart Douglas > > The problem described over there https://stackoverflow.com/questions/31205287/encoding-servlets-with-utf-8... still exists with the latest release. I had to explicitly set UTF-8 as default encoding to make resteasy properly decode form submissions and not decode UTF-8 as latin-1 (at least it looks a lot like that to me). > On top of that, persisting session ids to file store (without using <distributable/> in web.xml) tends to lose the session store when reloading the (unmanaged) webapp too fast during development. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9337) servlet container has no UTF-8 encoding default set, produces garbage on form submissions

by Mr Gruust (JIRA)

[ https://issues.jboss.org/browse/WFLY-9337?page=com.atlassian.jira.plugin.... ] Mr Gruust commented on WFLY-9337: --------------------------------- The fact that changing the default fixes the problem, does not imply that the shipping default is the actual cause of the issue. Actually, it indicates that request decoding erroneously relies on this default. > servlet container has no UTF-8 encoding default set, produces garbage on form submissions > ----------------------------------------------------------------------------------------- > > Key: WFLY-9337 > URL: https://issues.jboss.org/browse/WFLY-9337 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 11.0.0.CR1 > Reporter: Mr Gruust > Assignee: Stuart Douglas > > The problem described over there https://stackoverflow.com/questions/31205287/encoding-servlets-with-utf-8... still exists with the latest release. I had to explicitly set UTF-8 as default encoding to make resteasy properly decode form submissions and not decode UTF-8 as latin-1 (at least it looks a lot like that to me). > On top of that, persisting session ids to file store (without using <distributable/> in web.xml) tends to lose the session store when reloading the (unmanaged) webapp too fast during development. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-123) [QE] - JMAN4-125 - Stop an EAP Domain - Sprint-68

by Hayk Hovsepyan (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-123?page=com.atlassian.jira.pl... ] Hayk Hovsepyan commented on HAWKULARQE-123: ------------------------------------------- Test cases created and executed, issues logged, test plan is updated with all links. > [QE] - JMAN4-125 - Stop an EAP Domain - Sprint-68 > ------------------------------------------------- > > Key: HAWKULARQE-123 > URL: https://issues.jboss.org/browse/HAWKULARQE-123 > Project: Hawkular QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Labels: 5.0, mm-integration-hawkular-qe > > See [JMAN4-125|https://issues.jboss.org/browse/JMAN4-125] > Requirement's Test Plan: https://mojo.redhat.com/docs/DOC-1141233 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3273) sharedState is passed null by PluginAuthenticationCallbackHandler

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3273?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-3273: ------------------------------------------------- automation(a)ovirt.org changed the Status of [bug 1490383|https://bugzilla.redhat.com/show_bug.cgi?id=1490383] from NEW to POST > sharedState is passed null by PluginAuthenticationCallbackHandler > ----------------------------------------------------------------- > > Key: WFCORE-3273 > URL: https://issues.jboss.org/browse/WFCORE-3273 > Project: WildFly Core > Issue Type: Bug > Components: Security > Environment: Fedora 26, using ovirt-engine-wildfly package > Reporter: Roy Golan > Assignee: Darran Lofthouse > > oVirt's ovirt-engine uses an authorization plugin [1] for management interface that recently after upgrading to Wildfly 11 stopped working. The reason is the sharedState passed to the plugin constructor is now null. > A current workaround this would be to avoid adding to plugin into the shareState but that means any delegating plugin would fail to find this plugin and possibly other bad stuff I'm not aware of. > [1] https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=backend/manag... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017