March 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1496) Parallel agenda freezes when running fireUntilHalt on multiple KieSessions

by Jiri Petrlik (JIRA)

Jiri Petrlik created DROOLS-1496: ------------------------------------ Summary: Parallel agenda freezes when running fireUntilHalt on multiple KieSessions Key: DROOLS-1496 URL: https://issues.jboss.org/browse/DROOLS-1496 Project: Drools Issue Type: Bug Components: core engine Reporter: Jiri Petrlik Assignee: Mario Fusco Parallel agenda freezes when running in multiple KieSessions. Reproducer is in "testMultipleParallelKieSessionsFireUntilHalt" test from https://github.com/kiegroup/drools/pull/1164/commits/b3d8edee350b4e05101f... Reproducer does the following steps: # Create kie base. # Run 5 separate threads. # Each thread creates its own kie session with parallel agenda enabled. # Run fire until halt on its own kie session. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ELY-1027) CS tool, Parameter --salt requires --iteration and vice versa

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/ELY-1027?page=com.atlassian.jira.plugin.s... ] Ilia Vassilev reassigned ELY-1027: ---------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > CS tool, Parameter --salt requires --iteration and vice versa > ------------------------------------------------------------- > > Key: ELY-1027 > URL: https://issues.jboss.org/browse/ELY-1027 > Project: WildFly Elytron > Issue Type: Bug > Components: Command-Line Tool > Reporter: Hynek Švábek > Assignee: Ilia Vassilev > > If I use only one parameter from --salt or --iteration then this one is ignored and result password is in clear text. > {code} > java -jar wildfly-elytron-tool.jar credential-store --add myalias --secret supersecretpassword --location="test.store" --uri "cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS" --password mycspassword --summary --salt="abcdefgh" > {code} > Result of this command is: > {code} > Alias "myalias" has been successfully stored > Credential store command summary: > -------------------------------------- > /subsystem=elytron/credential-store=test:add(uri="cr-store://test?modifiable=true;create=true;keyStoreType=JCEKS",relative-to=jboss.server.data.dir,credential-reference={clear-text="mycspassword"}) > {code} > *There is expected error.* > Please add there this constraint: parameter --salt requires --iteration and vice versa -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8449) EJB contextData not sent back to client in response

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Fedor Gavrilov moved JBEAP-9889 to WFLY-8449: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8449 (was: JBEAP-9889) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EJB (was: EJB) Fix Version/s: (was: 7.1.0.GA) > EJB contextData not sent back to client in response > --------------------------------------------------- > > Key: WFLY-8449 > URL: https://issues.jboss.org/browse/WFLY-8449 > Project: WildFly > Issue Type: Bug > Components: EJB > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Labels: ejb > > With former JBoss versions it was possible to pass context beside the method invocation from the client to the server and back. This was done via (AOP) interceptors. > Since AS7 and WildFly the only possibility is to pass such context from the client to the server. > It should also possible to pass serializeable objects from the server side to the client if the invocation returns and have a client side interceptor to read that informations. > This was used to return i.e. tracking or additional usefull informations. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8448) Upgrade JBoss Metadata from 10.0.0.Final to 10.0.1.Final

by Carlo de Wolf (JIRA)

[ https://issues.jboss.org/browse/WFLY-8448?page=com.atlassian.jira.plugin.... ] Carlo de Wolf moved JBEAP-9888 to WFLY-8448: -------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8448 (was: JBEAP-9888) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Target Release: (was: 7.1.0.GA) > Upgrade JBoss Metadata from 10.0.0.Final to 10.0.1.Final > -------------------------------------------------------- > > Key: WFLY-8448 > URL: https://issues.jboss.org/browse/WFLY-8448 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Carlo de Wolf > Assignee: Carlo de Wolf > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2576) Operation failure descriptions following service start failures are overly noisy.

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2576?page=com.atlassian.jira.plugi... ] Brian Stansberry moved JBEAP-9887 to WFCORE-2576: ------------------------------------------------- Project: WildFly Core (was: JBoss Enterprise Application Platform) Key: WFCORE-2576 (was: JBEAP-9887) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Domain Management (was: Domain Management) > Operation failure descriptions following service start failures are overly noisy. > --------------------------------------------------------------------------------- > > Key: WFCORE-2576 > URL: https://issues.jboss.org/browse/WFCORE-2576 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > An example failure from JBEAP-6887: > {code} > { > "outcome" => "failed", > "failure-description" => { > "WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store-client.cs_not_found_exception" => "org.jboss.msc.service.StartException in service org.wildfly.security.credential-store-client.cs_not_found_exception: WFLYELY00004: Unable to start the service. > Caused by: org.wildfly.security.credential.store.CredentialStoreException: ELY09506: Cannot read credential storage file '/home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks' for the store named 'cs_not_found_exception' > Caused by: java.io.FileNotFoundException: /home/hsvabek/securityworkspace/VERIFICATION/2016_11_02_UX_testing/jboss-eap-7.1.0.DR7/standalone/data/cs/keystore-not_exists.jceks (No such file or directory)"}, > "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.cs_not_found_exception"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > }, > "rolled-back" => true > } > {code} > There is no requirement not to show an exception or stack trace snippet. IMHO it's the best part of the message. And it's not feasible to show nothing else, as there are a number of layers in between. > But, this can certainly be improved, which is what this issue is about: > 1) "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined > This is just noise. I'm quite certain this is already fixed and verified in a different issue though. Reproducing this against current code doesn't show this bit any longer. > 2) "org.jboss.msc.service.StartException in service org.wildfly.security.credential-store-client.cs_not_found_exception: " > This is superfluous, since it follows ""WFLYCTL0080: Failed services" => {"org.wildfly.security.credential-store-client.cs_not_found_exception"" which says the same thing. This can go. > 3) ""WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.security.credential-store-client.cs_not_found_exception"]" > Seems redundant since the only non-installed service listed is the one already reported as failed. This I'm not certain I'll fix as doing so may introduce some other issue. But I'll have a look. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8136) allow JAX-RS @Produces in CDI @Stereotype

by Martin Stefanko (JIRA)

[ https://issues.jboss.org/browse/WFLY-8136?page=com.atlassian.jira.plugin.... ] Martin Stefanko reassigned WFLY-8136: ------------------------------------- Assignee: Martin Stefanko (was: Alessio Soldano) > allow JAX-RS @Produces in CDI @Stereotype > ----------------------------------------- > > Key: WFLY-8136 > URL: https://issues.jboss.org/browse/WFLY-8136 > Project: WildFly > Issue Type: Feature Request > Components: CDI / Weld, REST > Affects Versions: 9.0.1.Final > Environment: Windows 7, JDK 1.8.0_60 > Reporter: Andreas Klemp > Assignee: Martin Stefanko > > A simple JAX-RS REST service can be annotated with @Produces to define the resulting mime-type. However, it is not working anymore, when the annotation is moved to a stereotype. The default application/octet-stream is used. > {code} > @Stereotype > @Produces(MediaType.APPLICATION_JSON) > @Target(ElementType.TYPE) > @Retention(RetentionPolicy.RUNTIME) > public @interface RestService { > } > @Path("/some") > @RestService > public class SomeRestService { > @GET > @Path("/") > public Response getSome() { > return Response.ok().entity("{\"x\" : 42, \"y\" : \"foo\"}").build(); > } > } > {code} > Using the following dependencies in Gradle project. > {noformat} > providedCompile( > [group: 'javax.enterprise', name: 'cdi-api', version: '1.2'], > [group: 'org.jboss.spec.javax.ws.rs', name: 'jboss-jaxrs-api_2.0_spec', version: '1.0.0.Final'], > [group: 'com.fasterxml.jackson.core', name: 'jackson-databind', version: '2.7.4'] > ) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-2563) Missing failure description for incorrect module in Elytron dir-context

by ehsavoie Hugonnet (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2563?page=com.atlassian.jira.plugi... ] ehsavoie Hugonnet reassigned WFCORE-2563: ----------------------------------------- Assignee: ehsavoie Hugonnet (was: Darran Lofthouse) > Missing failure description for incorrect module in Elytron dir-context > ----------------------------------------------------------------------- > > Key: WFCORE-2563 > URL: https://issues.jboss.org/browse/WFCORE-2563 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.0.Beta9 > Reporter: Ondrej Lukas > Assignee: ehsavoie Hugonnet > Labels: user_experience > > In case when {{module}} attribute from Elytron {{dir-context}} includes module which does not exist, then insufficient failure description is provided - it only prints name of given module. It should rather inform that given module does not exist. > See: > {code} > /subsystem=elytron/dir-context=someDirContext:add(url=localhost,module=wrong.module) > { > "outcome" => "failed", > "failure-description" => "wrong.module", > "rolled-back" => true > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1494) Problems with parallel agenda

by Tibor Zimányi (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1494?page=com.atlassian.jira.plugi... ] Tibor Zimányi commented on DROOLS-1494: --------------------------------------- I tried your PR and the results are similar to yours. So I agree that this should be closed. I created a long term JIRA for better enhancement here: https://issues.jboss.org/browse/DROOLS-1495. > Problems with parallel agenda > ----------------------------- > > Key: DROOLS-1494 > URL: https://issues.jboss.org/browse/DROOLS-1494 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta7 > Reporter: Tibor Zimányi > Assignee: Mario Fusco > Labels: reported-by-qe > Fix For: 7.0.0.Beta8 > > > From doc [1] there can be seen that four benchmarks show problems when run with parallel agenda enabled. > Benchmarks _AdvOperators3ExpertBenchmark_ and _RetractFactsFromWmExpertBenchmark_ > falled back to single threaded agenda although they doesn't use features that aren't supported with parallel agenda (e.g. like salience). > Benchmarks StartsStartedbyFusionBenchmark and UpdateFactsInWmExpertBenchmark shows no gain when using parallel agenda although they contain more partitions. > I created runners for debugging here [2], so the benchmarks can be debugged outside of JMH. They are part of master branch in kie-benchmarks, so just pull of new changes is sufficient to get them. > [1] https://docs.google.com/a/redhat.com/spreadsheets/d/1hp5lLcmox_NFEUsqNSNZ... > [2] https://github.com/kiegroup/kie-benchmarks/commit/887f758931b02d096f1e870... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-8447) Change FD to FD_ALL in default TCP JGroups stack

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-8447?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-9884 to WFLY-8447: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8447 (was: JBEAP-9884) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR14) > Change FD to FD_ALL in default TCP JGroups stack > ------------------------------------------------ > > Key: WFLY-8447 > URL: https://issues.jboss.org/browse/WFLY-8447 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > I was speaking to [~belaban] on performance tuning recommendations for the upcoming EAP 7.1 Performance Tuning Guide. > He mentioned that he could see no reason why the default JGroups TCP stack should be using FD instead of FD_ALL for failure detection. (the UDP stack already has FD_ALL as the default). > Rather than instruct customers to change the protocol manually, it would be better if the default TCP stack could be changed to use FD_ALL by default. > Here are the default stacks taken from `standalone-ha.xml` in 7.1.0.DR14: > {code:xml} > <stacks> > <stack name="udp"> > <transport type="UDP" socket-binding="jgroups-udp"/> > <protocol type="PING"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK"/> > <protocol type="FD_ALL"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="UFC"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > </stack> > <stack name="tcp"> > <transport type="TCP" socket-binding="jgroups-tcp"/> > <socket-protocol type="MPING" socket-binding="jgroups-mping"/> > <protocol type="MERGE3"/> > <protocol type="FD_SOCK"/> > <protocol type="FD"/> > <protocol type="VERIFY_SUSPECT"/> > <protocol type="pbcast.NAKACK2"/> > <protocol type="UNICAST3"/> > <protocol type="pbcast.STABLE"/> > <protocol type="pbcast.GMS"/> > <protocol type="MFC"/> > <protocol type="FRAG2"/> > </stack> > </stacks> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-1495) Partition also ObjectTypeNodes when using parallel agenda

by Tibor Zimányi (JIRA)

Tibor Zimányi created DROOLS-1495: ------------------------------------- Summary: Partition also ObjectTypeNodes when using parallel agenda Key: DROOLS-1495 URL: https://issues.jboss.org/browse/DROOLS-1495 Project: Drools Issue Type: Enhancement Components: core engine Affects Versions: 7.0.0.Beta7 Reporter: Tibor Zimányi Assignee: Mario Fusco Priority: Minor Currently we don't parallelize ObjectTypeNodes. They are part of MAIN partition. The parallelization starts then after OTNs. This limitation doesn't introduce performance gains for scenarios, where only one partition is after each OTN. The better approach would be to have the Rete network partitioned right from Entry Point. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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