February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9067) Clean JASPIC Implementation with WildFly Elytron

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9067?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9067: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Clean JASPIC Implementation with WildFly Elytron > ------------------------------------------------ > > Key: WFLY-9067 > URL: https://issues.jboss.org/browse/WFLY-9067 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 12.0.0.CR1 > > > This may be broken down into smaller steps but initially this is the main integration. > h3. Analysis Document: - > https://developer.jboss.org/docs/DOC-56012 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9007) The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9007?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9007: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > The bin/product.conf and the org.jboss.as.product:<xxx> module should come in via an FP > --------------------------------------------------------------------------------------- > > Key: WFLY-9007 > URL: https://issues.jboss.org/browse/WFLY-9007 > Project: WildFly > Issue Type: Task > Components: Server > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Fix For: 12.0.0.CR1 > > > For WFLY-4692 we moved the "product" stuff out of [servlet-]feature-pack and into [servlet-]dist. But this means it doesn't end up in the skinny dist produced by the "[servlet-]build" module. Plus it makes the "dist" a kind of FP of its own. > The stuff in [servlet-]dist/src/distribution should be its own FP. That one *perhaps* depends on the related normal feature-pack. Then build and dist use the new FP in addition to or instead of the regular feature-pack. > So, the regular feature-pack is independently usable, in other dists, but our offiical build/dist, which has our official product module, picks up the new FP. > Whether the new "product" FP depends on the regular feature-pack depends on how we want to use it; i.e. can this bin/product.conf and module be used in some other flavor of dist besides the official one. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8954: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > 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 > Fix For: 12.0.0.CR1 > > > 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)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8858) Remove JPA container check for deprecated hibernate.ejb.use_class_enhancer

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8858?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8858: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Remove JPA container check for deprecated hibernate.ejb.use_class_enhancer > -------------------------------------------------------------------------- > > Key: WFLY-8858 > URL: https://issues.jboss.org/browse/WFLY-8858 > Project: WildFly > Issue Type: Task > Components: JPA / Hibernate > Reporter: Scott Marlow > Assignee: Scott Marlow > Fix For: 12.0.0.CR1 > > > Applications can instead use the jboss.as.jpa.classtransformer property to control whether the application can use entity class rewriting. Starting with Hibernate ORM 5.0+, Hibernate defaults to always rewrite entity classes. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8467) simple-election-policy is not sufficiently descriptive

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8467?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8467: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > simple-election-policy is not sufficiently descriptive > ------------------------------------------------------ > > Key: WFLY-8467 > URL: https://issues.jboss.org/browse/WFLY-8467 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.Alpha1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.CR1 > > > simple-election-policy was originally a port of http://anonsvn.jboss.org/repos/jbossas/trunk/cluster/src/main/java/org/jb... > It's time to revisit this. > 1. The term "simple" doesn't at all describe how the policy elects the primary node. > 2. "position" isn't intuitive either - until you realize that it is a reference to the underlying data structure. > 3. Is the ability to specify the nth youngest or oldest node a realistic requirement? > We can generalize this policy as doing 2 things: > a. Sorts the candidates based on some criteria (e.g. age, name) > b. Select the head of the sorted list > This is logically equivalent to: > members.stream().sort(comparator).findFirst(); > Proposal: > <age-election-policy sort="DESCENDING|ASCENDING"/> > <name-election-policy sort="ASCENDING|DESCENDING"/> -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8449?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8449: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > 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: downstream_dependency, ejb > Fix For: 12.0.0.CR1 > > > 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.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9346) Race condition during ORB startup

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9346?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9346: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Race condition during ORB startup > --------------------------------- > > Key: WFLY-9346 > URL: https://issues.jboss.org/browse/WFLY-9346 > Project: WildFly > Issue Type: Bug > Components: IIOP, Security > Affects Versions: 11.0.0.CR1 > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Fix For: 12.0.0.CR1 > > > In the code, there is not direct dependency between ORB service and the security which occasionally may lead to the following error: > {code} > 2017-09-10 22:06:57,015 WARNING [javax.enterprise.resource.corba._INITIALIZING_.rpc.presentation] (MSC service thread 1-3) "IOP01210227: (BAD_OPERATION) Error in running ORB configurator": org.omg.CORBA.BAD_OPERATION: vmcid: SUN minor code: 227 completed: No > at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:558) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at com.sun.corba.se.impl.logging.ORBUtilSystemException.orbConfiguratorError(ORBUtilSystemException.java:576) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:485) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at com.sun.corba.se.impl.orb.ORBImpl.set_parameters(ORBImpl.java:543) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at org.omg.CORBA.ORB.init(ORB.java:353) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at org.wildfly.iiop.openjdk.service.CorbaORBService.start(CorbaORBService.java:126) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:2032) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1955) [jboss-msc-1.2.7.SP1-redhat-1.jar:1.2.7.SP1-redhat-1] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [rt.jar:1.8.0_144] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [rt.jar:1.8.0_144] > at java.lang.Thread.run(Thread.java:748) [rt.jar:1.8.0_144] > Caused by: java.lang.RuntimeException: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain > at org.wildfly.iiop.openjdk.security.LegacySSLSocketFactory.setORB(LegacySSLSocketFactory.java:86) [wildfly-iiop-openjdk-7.1.0.GA-redhat-SNAPSHOT.jar:7.1.0.GA-redhat-SNAPSHOT] > at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.initializeTransport(ORBConfiguratorImpl.java:271) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at com.sun.corba.se.impl.orb.ORBConfiguratorImpl.configure(ORBConfiguratorImpl.java:149) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > at com.sun.corba.se.impl.orb.ORBImpl.postInit(ORBImpl.java:483) [openjdk-orb-8.0.8.Final-redhat-1.jar:8.0.8.Final-redhat-1] > ... 8 more > Caused by: javax.naming.ConfigurationException: WFLYIIOP0051: Error configuring domain socket factory: failed to lookup JSSE security domain > ... 12 more > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9344) Let Infinispan manage eviction for distributed web sessions and @Stateful EJBs

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9344?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9344: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Let Infinispan manage eviction for distributed web sessions and @Stateful EJBs > ------------------------------------------------------------------------------ > > Key: WFLY-9344 > URL: https://issues.jboss.org/browse/WFLY-9344 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Affects Versions: 11.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 12.0.0.CR1 > > > With Infinispan's transition to Caffeine to implement its data container, WF should finally be able to offload eviction to Infinispan, by configuring caffeine to use a specific Weigher that returns 0 for non-primary session entries, where max-active-sessions is configured as the maximumWeight. From an Infinispan configuration perspective, this corresponds to a custom EntrySizeCalculator that returns 0 for non-primary session entries, and a maxSize equal to the max-active-sessions. The remaining entries would rely on cascading eviction (i.e. manually evicting from a via passivation callback). > As of Infinispan 9.1, the requisite DataContainer configuration attributes are deprecated - thus we need to lobby to expose the mechanisms for overriding the entry size calculator to be able to ensure this solution will be supported in the future. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9314) Upgrade JBeret to 1.2.5.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9314?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9314: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Upgrade JBeret to 1.2.5.Final > ----------------------------- > > Key: WFLY-9314 > URL: https://issues.jboss.org/browse/WFLY-9314 > Project: WildFly > Issue Type: Component Upgrade > Components: Batch > Reporter: Leandro Kersting de Freitas > Assignee: Cheng Fang > Fix For: 12.0.0.CR1 > > > https://issues.jboss.org/projects/JBERET/versions/12335093 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9294) Add encryption/authentication configuration for infinispan remote cache store

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-9294?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-9294: ----------------------------- Fix Version/s: 12.0.0.CR1 (was: 12.0.0.Beta1) > Add encryption/authentication configuration for infinispan remote cache store > ----------------------------------------------------------------------------- > > Key: WFLY-9294 > URL: https://issues.jboss.org/browse/WFLY-9294 > Project: WildFly > Issue Type: Enhancement > Components: Clustering > Reporter: Paul Ferraro > Assignee: Radoslav Husar > Fix For: 12.0.0.CR1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 February 2018