March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2509) Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true"

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2509?page=com.atlassian.jira.plugi... ] Darran Lofthouse moved WFLY-7081 to WFCORE-2509: ------------------------------------------------ Project: WildFly Core (was: WildFly) Key: WFCORE-2509 (was: WFLY-7081) Component/s: Security (was: Security) Fix Version/s: 3.0.0.Beta8 (was: 11.0.0.Alpha1) > Elytron + https-listener in undertow listener doesn't work with enable-http2 set to "true" > ------------------------------------------------------------------------------------------ > > Key: WFCORE-2509 > URL: https://issues.jboss.org/browse/WFCORE-2509 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Hynek Švábek > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 3.0.0.Beta8 > > > When I want to use HTTPS settings in combination with Elytron subsystem then I have to set "enable-http2" to "false" value. > For settings I followed this blog post http://darranl.blogspot.cz/2016/02/wildfly-elytron-ssl-configuration.html > And as keystore I used default application.keystore -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1471) Unable to marshall a kieSession running in stream mode.

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1471?page=com.atlassian.jira.plugi... ] Mario Fusco commented on DROOLS-1471: ------------------------------------- Sorry but it is impossible for me to investigate and eventually fix this issue without a reproducer. Can you please provide one? Also there's a chance that this issue has been already solved in drools 6.5. Did you give it a try? > Unable to marshall a kieSession running in stream mode. > ------------------------------------------------------- > > Key: DROOLS-1471 > URL: https://issues.jboss.org/browse/DROOLS-1471 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 6.4.0.Final > Reporter: Manjunath S Paramesan > Assignee: Mario Fusco > > Runtime exceptions are thrown when Marshalling a KieSession in runtime. Please see the stack trace below: > java.util.concurrent.ExecutionException: java.lang.NullPointerException > at java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.util.concurrent.FutureTask.get(FutureTask.java:206) > at drools.tester.drools.marshallng.tester.ReproducerTest.test(ReproducerTest.java:91) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > 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.RunBefores.evaluate(RunBefores.java:24) > 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.runners.ParentRunner.run(ParentRunner.java:363) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:86) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192) > Caused by: java.lang.NullPointerException > at org.drools.core.util.index.TupleList.removeFirst(TupleList.java:142) > at org.drools.core.phreak.RuleExecutor.getNextTuple(RuleExecutor.java:167) > at org.drools.core.phreak.RuleExecutor.fire(RuleExecutor.java:107) > at org.drools.core.phreak.RuleExecutor.evaluateNetworkAndFire(RuleExecutor.java:74) > at org.drools.core.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:1007) > at org.drools.core.common.DefaultAgenda.fireLoop(DefaultAgenda.java:1350) > at org.drools.core.common.DefaultAgenda.fireUntilHalt(DefaultAgenda.java:1269) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1345) > at org.drools.core.impl.StatefulKnowledgeSessionImpl.fireUntilHalt(StatefulKnowledgeSessionImpl.java:1324) > at drools.tester.drools.marshallng.tester.ReproducerTest$1.run(ReproducerTest.java:73) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 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) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-760) Code style formatters are not up-to-date

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-760?page=com.atlassian.jira.plugin... ] Petr Široký commented on DROOLS-760: ------------------------------------ My understanding was that this JIRA is mainly about not having up-to-date formatters for IDEs, which I believe got mostly fixed? We can keep this open until _everything_ gets fixed, but that may very well never happen. > Code style formatters are not up-to-date > ---------------------------------------- > > Key: DROOLS-760 > URL: https://issues.jboss.org/browse/DROOLS-760 > Project: Drools > Issue Type: Task > Reporter: Tibor Zimányi > Assignee: Petr Široký > Priority: Minor > Labels: reported-by-qe > Attachments: code-styleQE.zip > > > Code style formatters in git repo are not actual. Or not widely used. This causes that different styles are used in code. > There should be some agreement about how the code should be written and this should be forced in PRs. This can remove many problems with whitespaces in PR diffs. > Attached code style templates can be used as a base for new templates that (hope) will be used in Drools projects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-760) Code style formatters are not up-to-date

by Petr Široký (JIRA)

[ https://issues.jboss.org/browse/DROOLS-760?page=com.atlassian.jira.plugin... ] Petr Široký updated DROOLS-760: ------------------------------- Summary: Code style formatters are not up-to-date (was: Code style formatters are not actual) > Code style formatters are not up-to-date > ---------------------------------------- > > Key: DROOLS-760 > URL: https://issues.jboss.org/browse/DROOLS-760 > Project: Drools > Issue Type: Task > Reporter: Tibor Zimányi > Assignee: Petr Široký > Priority: Minor > Labels: reported-by-qe > Attachments: code-styleQE.zip > > > Code style formatters in git repo are not actual. Or not widely used. This causes that different styles are used in code. > There should be some agreement about how the code should be written and this should be forced in PRs. This can remove many problems with whitespaces in PR diffs. > Attached code style templates can be used as a base for new templates that (hope) will be used in Drools projects. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-956) Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-956?page=com.atlassian.jira.plugin.sy... ] Martin Choma commented on ELY-956: ---------------------------------- Ok. Feel free to close. > Coverity static analysis: Synchronization on java.util.concurrent object in ElytronPolicyConfigurationFactory > ------------------------------------------------------------------------------------------------------------- > > Key: ELY-956 > URL: https://issues.jboss.org/browse/ELY-956 > Project: WildFly Elytron > Issue Type: Bug > Affects Versions: 1.1.0.Beta24 > Reporter: Martin Choma > Assignee: Ilia Vassilev > Priority: Minor > > Coverity static-analysis scan found a synchronization on java.util.concurrent.ConcurrentHashMap object in: > * {{ElytronPolicyConfigurationFactory.getPolicyConfiguration}} > * {{ElytronPolicyConfigurationFactory.inService}} > If policyConfiguration synchronization is concern, it should be enough to synchronize on policyConfiguration object. > > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... > https://scan7.coverity.com/reports.htm#v23632/p11778/fileInstanceId=84902... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8306) Soap attachments are being truncated when moving from jboss 7 to wildfly9/10

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8306?page=com.atlassian.jira.plugin.... ] Stuart Douglas closed WFLY-8306. -------------------------------- Resolution: Rejected > Soap attachments are being truncated when moving from jboss 7 to wildfly9/10 > ---------------------------------------------------------------------------- > > Key: WFLY-8306 > URL: https://issues.jboss.org/browse/WFLY-8306 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Windows > Reporter: Einat Peretz > Assignee: Stuart Douglas > > Client access wildfly 9 or 10 web service (soap using Axis2) using https with zip attachment and the zip is received truncated on the server. > The same deployed application with same client worked fine on Jboss 7.3. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-996) Incorrect class loader is used for loading custom Initial context factory in Elytron dir-context

by Bartosz Baranowski (JIRA)

Bartosz Baranowski created ELY-996: -------------------------------------- Summary: Incorrect class loader is used for loading custom Initial context factory in Elytron dir-context Key: ELY-996 URL: https://issues.jboss.org/browse/ELY-996 Project: WildFly Elytron Issue Type: Bug Reporter: Bartosz Baranowski Assignee: Darran Lofthouse -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-996) Incorrect class loader is used for loading custom Initial context factory in Elytron dir-context

by Bartosz Baranowski (JIRA)

[ https://issues.jboss.org/browse/ELY-996?page=com.atlassian.jira.plugin.sy... ] Bartosz Baranowski reassigned ELY-996: -------------------------------------- Assignee: Bartosz Baranowski (was: Darran Lofthouse) > Incorrect class loader is used for loading custom Initial context factory in Elytron dir-context > ------------------------------------------------------------------------------------------------ > > Key: ELY-996 > URL: https://issues.jboss.org/browse/ELY-996 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Bartosz Baranowski > Assignee: Bartosz Baranowski > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8306) Soap attachments are being truncated when moving from jboss 7 to wildfly9/10

by Einat Peretz (JIRA)

[ https://issues.jboss.org/browse/WFLY-8306?page=com.atlassian.jira.plugin.... ] Einat Peretz commented on WFLY-8306: ------------------------------------ Sorry about that, after looking at this more thoroughly, I found out it is a bug in the soap framework. Thank you for your help. > Soap attachments are being truncated when moving from jboss 7 to wildfly9/10 > ---------------------------------------------------------------------------- > > Key: WFLY-8306 > URL: https://issues.jboss.org/browse/WFLY-8306 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 10.1.0.Final > Environment: Windows > Reporter: Einat Peretz > Assignee: Stuart Douglas > > Client access wildfly 9 or 10 web service (soap using Axis2) using https with zip attachment and the zip is received truncated on the server. > The same deployed application with same client worked fine on Jboss 7.3. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8326) Enabling statistics on caches shouldn't require reload of server

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8326?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-9435 to WFLY-8326: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8326 (was: JBEAP-9435) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) (was: 7.1.0.DR13) > Enabling statistics on caches shouldn't require reload of server > ---------------------------------------------------------------- > > Key: WFLY-8326 > URL: https://issues.jboss.org/browse/WFLY-8326 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > {noformat} > /subsystem=infinispan/cache-container=ejb/distributed-cache=dist:write-attribute(name=statistics-enabled,value=true){allow-resource-service-restart=true} > { > "outcome" => "success", > "response-headers" => { > "operation-requires-reload" => true, > "process-state" => "reload-required" > } > } > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 March 2017