March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2508) Wildfly OpenSSL 1.0.0.Beta7

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2508?page=com.atlassian.jira.plugi... ] Stuart Douglas moved JBEAP-9434 to WFCORE-2508: ----------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2508 (was: JBEAP-9434) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Wildfly OpenSSL 1.0.0.Beta7 > --------------------------- > > Key: WFCORE-2508 > URL: https://issues.jboss.org/browse/WFCORE-2508 > Project: WildFly Core > Issue Type: Component Upgrade > Reporter: Stuart Douglas > Assignee: Stuart Douglas > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8325) Connector module 'authentication-context' attributes should not support expressions and should be capability references if the target resource provides a capability

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-8325?page=com.atlassian.jira.plugin.... ] Brian Stansberry moved JBEAP-9432 to WFLY-8325: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8325 (was: JBEAP-9432) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JCA (was: JCA) > Connector module 'authentication-context' attributes should not support expressions and should be capability references if the target resource provides a capability > -------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8325 > URL: https://issues.jboss.org/browse/WFLY-8325 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > > The various "authentication-context" attributes added into the connector module for the elytron integration say they support expressions. They shouldn't, as model references should not support expressions as these interfere with model referential integrity checks. > Also, where possible the attribute definitions should be configured as capability references, thus automatically turning on the kernel's referential integrity checks and allowing CLI and HAL value completion. > The latter is only possible for ADs where the containing resource exposes a capability itself. The DS and XA DS resources do. I'm not sure about RAs but I suspect they don't yet. -- 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 commented on WFLY-8306: -------------------------------------- It seems unlikely to be an undertow problem, 891 has no special significance for undertow. Do you have a reproducer? > 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-6290) XTS does not work with jbossws.undefined.host in WS config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-6290?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-6290: ----------------------------------------------- Radovan STANCEL <rstancel(a)redhat.com> changed the Status of [bug 1333968|https://bugzilla.redhat.com/show_bug.cgi?id=1333968] from ASSIGNED to NEW > XTS does not work with jbossws.undefined.host in WS config > ---------------------------------------------------------- > > Key: WFLY-6290 > URL: https://issues.jboss.org/browse/WFLY-6290 > Project: WildFly > Issue Type: Bug > Components: XTS > Reporter: Gytis Trikleris > Assignee: Ivo Studensky > Fix For: 10.2.0.Final > > > XTS uses ServerConfig to initialise it's configuration. However, we should rely on jboss.bind.address instead, because wsdl-host could take "jbossws.undefined.host" as a value. > "jbossws.undefined.host" will cause UnknownHostException, because address rewriting is not executed in XTS. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8324) Missing Elytron integration with Weld SecurityServices

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-8324?page=com.atlassian.jira.plugin.... ] Stuart Douglas moved JBEAP-9431 to WFLY-8324: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8324 (was: JBEAP-9431) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: CDI / Weld Security (was: CDI / Weld) (was: Security) Affects Version/s: (was: 7.1.0.DR13) > Missing Elytron integration with Weld SecurityServices > ------------------------------------------------------ > > Key: WFLY-8324 > URL: https://issues.jboss.org/browse/WFLY-8324 > Project: WildFly > Issue Type: Bug > Components: CDI / Weld, Security > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Priority: Critical > > [7:34 PM] Brian Stansberry: @StuartDouglas do we need an elytron equivalent to https://github.com/wildfly/wildfly/blob/master/weld/subsystem/src/main/ja.... ? > [7:35 PM] Brian Stansberry: a lazy JIRA search didn't reveal any open issue > Jean-François Denise left the room > [7:35 PM] Stuart Douglas: we do indeed > [7:39 PM] Brian Stansberry: i've been chasing down uses of SimpleSecurityManagerService.SERVICE_NAME which is why I saw that > [7:44 PM] Brian Stansberry: @StuartDouglas I'll file a JIRA. Unfortunately I have no clue what elytron construct would do the equivalent > [7:45 PM] Stuart Douglas: I am not 100% sure either > [7:45 PM] Stuart Douglas: at the moment it is mapped at either a Web or EJB level > [7:46 PM] Stuart Douglas: Actually I think I know > [7:46 PM] Brian Stansberry: the current stuff is doing thread local lookups > [7:46 PM] Stuart Douglas: It would just be SecurityDomain.getCurrent().getSecurityIdentity() > [7:46 PM] Brian Stansberry: i.e. the picketbox stuff, SimpleSecurityManager > [7:48 PM] Stuart Douglas: If you are going to file a JIRA can you assign it to me? > [7:49 PM] Stuart Douglas: and I can have a look at it after I am done with what I am currently working on -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2337) Removal of overlay in a server group fails inside a composite

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2337?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-2337: ------------------------------------- Steps to Reproduce: In domain mode, deploy some content. Then run the following composite: {code} { "operation" => "composite", "address" => [], "steps" => [ { "address" => [ ("server-group" => "main-server-group"), ("deployment-overlay" => "ov1"), ("deployment" => "toto.war") ], "operation" => "remove", "redeploy-affected" => true }, { "address" => [ ("server-group" => "main-server-group"), ("deployment-overlay" => "ov1") ], "operation" => "remove" }, { "address" => [ ("server-group" => "other-server-group"), ("deployment-overlay" => "ov1"), ("deployment" => "toto.war") ], "operation" => "remove", "redeploy-affected" => true }, { "address" => [ ("server-group" => "other-server-group"), ("deployment-overlay" => "ov1") ], "operation" => "remove" } ] } {code} was: In domain mode, deploy some content. Then run the following composite: { "operation" => "composite", "address" => [], "steps" => [ { "address" => [ ("server-group" => "main-server-group"), ("deployment-overlay" => "ov1"), ("deployment" => "toto.war") ], "operation" => "remove", "redeploy-affected" => true }, { "address" => [ ("server-group" => "main-server-group"), ("deployment-overlay" => "ov1") ], "operation" => "remove" }, { "address" => [ ("server-group" => "other-server-group"), ("deployment-overlay" => "ov1"), ("deployment" => "toto.war") ], "operation" => "remove", "redeploy-affected" => true }, { "address" => [ ("server-group" => "other-server-group"), ("deployment-overlay" => "ov1") ], "operation" => "remove" } ] } > Removal of overlay in a server group fails inside a composite > ------------------------------------------------------------- > > Key: WFCORE-2337 > URL: https://issues.jboss.org/browse/WFCORE-2337 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Jean-Francois Denise > Assignee: ehsavoie Hugonnet > Fix For: 3.0.0.Beta8 > > > Removing the overlay of a serverGroup inside a composite operation fails. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6607) Broadcast/Discovery group is possible to create with just a name

by Chao Wang (JIRA)

[ https://issues.jboss.org/browse/WFLY-6607?page=com.atlassian.jira.plugin.... ] Chao Wang updated WFLY-6607: ---------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/9518 > Broadcast/Discovery group is possible to create with just a name > ---------------------------------------------------------------- > > Key: WFLY-6607 > URL: https://issues.jboss.org/browse/WFLY-6607 > Project: WildFly > Issue Type: Bug > Components: JMS, Web Console > Affects Versions: 10.0.0.Final > Reporter: Chen Maoqian > Assignee: Chen Maoqian > > When defining new broadcast-group in Configuration: Subsystems Subsystem: Messaging - ActiveMQ Messaging Provider: default > user must define name, at least one connector and then either socket-binding or jgroups-channel-name (not both of them, just one) > At this moment it's possible to create broadcast group with just a name which is wrong. -- 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 actual

by Kirill Gaevskii (JIRA)

[ https://issues.jboss.org/browse/DROOLS-760?page=com.atlassian.jira.plugin... ] Kirill Gaevskii commented on DROOLS-760: ---------------------------------------- Hi [~psiroky], we decided to use actual formatter in Stunner, I saw some tries in other repositories like Uberfire, but mine goal was Stunner only, so I can't guarantee another repositories use it. > Code style formatters are not actual > ------------------------------------ > > 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-1471) Unable to marshall a kieSession running in stream mode.

by Manjunath S Paramesan (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1471?page=com.atlassian.jira.plugi... ] Manjunath S Paramesan updated DROOLS-1471: ------------------------------------------ Description: 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) > 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-1471) Unable to marshall a kieSession running in stream mode.

by Manjunath S Paramesan (JIRA)

Manjunath S Paramesan created DROOLS-1471: --------------------------------------------- Summary: 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 -- 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