June 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-2475) Upgrade Jackson dependencies.

by Eli Israel (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2475?page=com.atlassian.jira.plugi... ] Eli Israel commented on DROOLS-2475: ------------------------------------ Latest Wildfly is now 12.0.0.Final. Any chance of an updated KIE Execution Server WAR? > Upgrade Jackson dependencies. > ----------------------------- > > Key: DROOLS-2475 > URL: https://issues.jboss.org/browse/DROOLS-2475 > Project: Drools > Issue Type: Bug > Reporter: Petar Tahchiev > Assignee: Maciej Swiderski > Priority: Critical > > Hello, > I'm not sure this is the right place to report this, but I couldn't find a better one. In my project I'm using: > {code} > <dependency> > <groupId>org.kie.server</groupId> > <artifactId>kie-server-jms</artifactId> > <version>7.7.0.Final</version> > </dependency> > {code} > and I believe you guys are using jackson version 2.8.9: > https://github.com/kiegroup/kie-soup/blob/master/pom.xml#L56 > which is already 1 year old. In my app some third-party dependencies are bringing jackson 2.9.5 and because of this mismatch I get the following exception when I run my app: > {code} > Caused by: java.lang.NoSuchMethodError: com.fasterxml.jackson.databind.SerializationConfig.with(Lcom/fasterxml/jackson/databind/AnnotationIntrospector;)Lcom/fasterxml/jackson/databind/SerializationConfig; > at org.kie.server.api.marshalling.json.JSONMarshaller.configureMarshaller(JSONMarshaller.java:153) > at org.kie.server.api.marshalling.json.JSONMarshaller.<init>(JSONMarshaller.java:128) > at org.kie.server.api.marshalling.BaseMarshallerBuilder.build(BaseMarshallerBuilder.java:43) > at org.kie.server.api.marshalling.MarshallerFactory.getMarshaller(MarshallerFactory.java:52) > at org.kie.server.client.impl.AbstractKieServicesClientImpl.<init>(AbstractKieServicesClientImpl.java:83) > at org.kie.server.client.impl.KieServicesClientImpl.<init>(KieServicesClientImpl.java:71) > at org.kie.server.client.KieServicesFactory.newKieServicesClient(KieServicesFactory.java:101) > at com.nemesis.platform.module.ruleservices.config.RuleServicesModuleAutoConfiguration.defaultKieServicesClient(RuleServicesModuleAutoConfiguration.java:160) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Labels: Appformer UX UXTeam (was: UX UXTeam) > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: roundE-scaled.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-2532: ------------------------------------- Uploaded current wireframes, as pdf, covering: * Creating a scenario test asset against a single decision. * Test "model" encompasses both the outline and inputs via a singular via tabular model. * Results as alert messages, along with an alternative design that includes a test results summary. * Right dock for supporting guidance such as syntax cheatsheet. Note: Still working on "Expect" input interaction details. > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: Appformer, UX, UXTeam > Attachments: roundE-scaled.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2532) UX design for scenario simulation

by Liz Clayton (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2532?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-2532: -------------------------------- Attachment: roundE-scaled.pdf > UX design for scenario simulation > --------------------------------- > > Key: DROOLS-2532 > URL: https://issues.jboss.org/browse/DROOLS-2532 > Project: Drools > Issue Type: Task > Reporter: Liz Clayton > Assignee: Liz Clayton > Labels: UX, UXTeam > Attachments: roundE-scaled.pdf > > > As Aimee or Cameron I want to: > * Easily create a test scenario template through the use of variable/data object placeholders so that I can create test scenarios against a single decision. > * Define test scenarios through a UI so I can develop basic task scenarios with minimal engagement from IT. > * Run a test scenario simulation so that I can verify the expected results against test simulation results. > Verification conditions: > Provide wireframe design and click-thru prototype which includes the following views: > * Overview (properties) > * Scenario Template > * Scenarios Input Screen > * Results > * Code View -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Scott Marlow commented on WFLY-8954: ------------------------------------ [~tkraus] is there anything that we should change in [https://github.com/wildfly/wildfly/blob/master/jpa/eclipselink/src/main/j...] for EclipseLink to use the TransactionSynchronizationRegistry on WildFly? [https://github.com/wildfly/wildfly/blob/master/jpa/eclipselink/src/main/j...] is where we add integration properties for EclipseLink, as part of the call to PersistenceProvider#createContainerEntityManagerFactory, we could pass the TransactionSynchronizationRegistry as an integration setting, if EclipseLink supports that. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10279) [JDK9] Xalan - Provider class org.apache.bsf.BSFManager not in module

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-10279?page=com.atlassian.jira.plugin... ] Scott Marlow commented on WFLY-10279: ------------------------------------- I tried the same command on upstream (https://github.com/apache/xalan-j) and see the same response. {quote} jar -d --file ./build/xalan.jar Unable to derive module descriptor for: ./build/xalan.jar Provider class org.apache.bsf.BSFManager not in module {quote} [http://mail.openjdk.java.net/pipermail/jigsaw-dev/2017-April/012147.html] mentions this problem as well. Do we have a documented list of supported (client side) jars that have this problem, that should also mention Xalan? > [JDK9] Xalan - Provider class org.apache.bsf.BSFManager not in module > --------------------------------------------------------------------- > > Key: WFLY-10279 > URL: https://issues.jboss.org/browse/WFLY-10279 > Project: WildFly > Issue Type: Bug > Components: XML Frameworks > Affects Versions: 12.0.0.Final > Reporter: Rostislav Svoboda > Assignee: Scott Marlow > > jar -d --file dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT//modules/system/layers/base/org/apache/xalan/main/xalan-2.7.1.jbossorg-4.jar > Unable to derive module descriptor for: dist/target/wildfly-13.0.0.Alpha1-SNAPSHOT/modules/system/layers/base/org/apache/xalan/main/xalan-2.7.1.jbossorg-4.jar > Provider class org.apache.bsf.BSFManager not in module > CCing [~ropalka] [~dlloyd] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ELY-1531) Use the same gamut of runAs*() methods for both SecurityIdentity and AuthenticationContext

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/ELY-1531?page=com.atlassian.jira.plugin.s... ] Jan Kalina commented on ELY-1531: --------------------------------- ok, in which meaning should they provide same set of run methods in such case? > Use the same gamut of runAs*() methods for both SecurityIdentity and AuthenticationContext > ------------------------------------------------------------------------------------------ > > Key: ELY-1531 > URL: https://issues.jboss.org/browse/ELY-1531 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client, Authentication Server > Reporter: David Lloyd > > Both AuthenticationContext and SecurityIdentity can be captured and restored in a similar manner; they should use the same gamut of {{run*()}} methods. > The methods from {{org.wildfly.common.function.Functions}} can help with this. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3639) Elytron error message less comprehensive in jdk9 compared to jdk8

by Jean-Francois Denise (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3639?page=com.atlassian.jira.plugi... ] Jean-Francois Denise reassigned WFCORE-3639: -------------------------------------------- Assignee: Jean-Francois Denise > Elytron error message less comprehensive in jdk9 compared to jdk8 > ----------------------------------------------------------------- > > Key: WFCORE-3639 > URL: https://issues.jboss.org/browse/WFCORE-3639 > Project: WildFly Core > Issue Type: Bug > Components: CLI > Affects Versions: 4.0.0.Beta1 > Reporter: Martin Choma > Assignee: Jean-Francois Denise > > I like jdk8 error message where there is obvious GS2-KRB5 has been attempted but failed for some reason, PLAIN has been attempted, but failed for some reason. > {code:title=jdk8} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Authentication failed: all available authentication mechanisms failed: > GS2-KRB5: javax.security.sasl.SaslException: GS2-KRB5: Server rejected authentication > PLAIN: javax.security.sasl.SaslException: ELY05053: Callback handler failed for unknown reason [Caused by java.io.IOException: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode.] > {code} > Whereas in jdk9 error message hides the fact GS2-KRB5 was attempted and just prints error for PLAIN mechanism, but does not mention explicitely it is PLAIN mechanism > {code:title=jdk9} > Failed to connect to the controller: Unable to authenticate against controller at localhost:9993: Cannot get password: Failed to read username: Invalid Usage. Prompt attempted in non-interactive mode. Please check commands or change CLI mode. > {code} > This is general question, but I have hit this with this specific use case: > 1. server is configured to use GS2-KRB5 and PLAIN > 2. server is configured with TLS > 3. client is configured to use GS2-KRB5 > 4. expectation is authentication should be not successful because channel binding GS2-KRB5-PLUS should be used. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-279) Pipeline to Istio 0.8.0

by Hayk Hovsepyan (JIRA)

Hayk Hovsepyan created SWSQE-279: ------------------------------------ Summary: Pipeline to Istio 0.8.0 Key: SWSQE-279 URL: https://issues.jboss.org/browse/SWSQE-279 Project: Kiali QE Issue Type: Task Reporter: Hayk Hovsepyan Assignee: Hayk Hovsepyan -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9849) Hibernate session related leak on module undeployment

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-9849?page=com.atlassian.jira.plugin.... ] Scott Marlow closed WFLY-9849. ------------------------------ Resolution: Rejected There is no memory leak, just a weak reference that stays around after undeployment. The weak references should be cleaned up by the Java garbage collector. > Hibernate session related leak on module undeployment > ----------------------------------------------------- > > Key: WFLY-9849 > URL: https://issues.jboss.org/browse/WFLY-9849 > Project: WildFly > Issue Type: Bug > Affects Versions: 11.0.0.Final, 12.0.0.Final > Environment: * Ubuntu 16.04.3 LTS > * OpenJDK 1.8.0_151 > * Wildfly 11.0.0.Final > Seems to occur at least on CentOS 7/OpenJDK 1.8.0_151 also. > Reporter: Joni Syri > Assignee: Scott Marlow > > In some cases it seems that removing deployment from the Wildfly, doesn't free up {{org.hibernate.internal.SessionFactoryImpl}}- instance related to the deployment. (plus some other Hibernate related classes). This can be seen by taking memory dump with VisualVM and looking up {{SessionFactoryImpl}} instances. > This leads to cumulative memory leak in cases, where application is repeatedly deployed/undeployed (or updated). > updated: Seems to occur on 12.0.0.Final also > Memory dumps can be found at https://drive.google.com/drive/folders/1WbHB6hRpr_lrc4yb4yxWLpeObmJlNCzD (wildfly-leak-1 is after first deployment, wildfly-leak-2 after few re-deploys) > server.log https://drive.google.com/file/d/1I32OTnPWeopVEtRC3ol-pjkH2dlkLizD/view?us... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

5 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira June 2018