March 2018 - jboss-jira - Jboss List Archives

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

by Jason Greene (JIRA)

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

7 years

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8858?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8858: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

7 years

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-8467?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-8467: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9266) Upgrade Hibernate ORM to 5.2.12.Final

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9266?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9266: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Upgrade Hibernate ORM to 5.2.12.Final > ------------------------------------- > > Key: WFLY-9266 > URL: https://issues.jboss.org/browse/WFLY-9266 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9261) Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9261?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9261: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Cluster connection receives a "consumer created" message from the rebooting node but it has no corresponding binding for it locally > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9261 > URL: https://issues.jboss.org/browse/WFLY-9261 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Flavia Rainone > Assignee: Martyn Taylor > Fix For: 13.0.0.Beta1 > > > When rebooting a cluster node that uses singleton cluster mdbs, we get this error message: > {noformat} > 2017-07-25 16:08:54,426 ERROR [org.apache.activemq.artemis.core.server] (Thread-3 (ActiveMQ-client-global-threads)) AMQ224037: cluster connection Failed to handle message: java.lang.IllegalStateException: Cannot find binding for jms.queue.HelloWorldMDBQueuedea3e995-713c-11e7-85f2-b8f6b112daf7 on ClusterConnectionImpl@1129705701[nodeUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7, connector=TransportConfiguration(name=http-connector, factory=org-apache-activemq-artemis-core-remoting-impl-netty-NettyConnectorFactory) ?httpUpgradeEndpoint=http-acceptor&activemqServerName=default&httpUpgradeEnabled=true&port=9080&host=localhost, address=jms, server=ActiveMQServerImpl::serverUUID=dabaa1fa-713c-11e7-8f3a-b8f6b112daf7] > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.doConsumerCreated(ClusterConnectionImpl.java:1294) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.handleNotificationMessage(ClusterConnectionImpl.java:1029) > at org.apache.activemq.artemis.core.server.cluster.impl.ClusterConnectionImpl$MessageFlowRecordImpl.onMessage(ClusterConnectionImpl.java:1004) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1001) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:49) > at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1124) > at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:101) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9067?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9067: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9415) Add test cases to cover EJB client clustered session creation

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9415?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9415: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Add test cases to cover EJB client clustered session creation > ------------------------------------------------------------- > > Key: WFLY-9415 > URL: https://issues.jboss.org/browse/WFLY-9415 > Project: WildFly > Issue Type: Task > Components: Clustering, Test Suite > Affects Versions: 11.0.0.CR1 > Reporter: Richard Achmatowicz > Assignee: Richard Achmatowicz > Fix For: 13.0.0.Beta1 > > > EJB client session creation involves creating a proxy for a SFSB deployed on a remote server, which has the side effect of creating a session instance on the chosen target node. > Whether or not the operation is successful depends on three factors: > * the connections defined in the EJB client configuration > * the server environment in which the client is executing > * any strong affinity set by the client > These tests consider session creation in a clustered environment. The default server environment is a cluster called "ejb" with two nodes, "node-0" and "node-1". > The following test scenarios are covered: > 1. "normal" scenario > * client configuration: points to node-0 > * server environment: module deployed on cluster "ejb" = {node-0, node-1} > 2. "failover" scenario > * client configuration: points to node-0 > * server environment: module deployed on cluster "ejb" = {node-1} > 3. "bad connection" scenario > * client configuration: points to node-2 (non-existent) > * server environment: module deployed on cluster "ejb" = {node-0, node-1} > As mentioned earlier, these tests operate in a single two-node cluster environment. A third singleton, non-clustered node added to the available environment would permit more complex scenarios (where we could test cluster affinity specification more directly). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9407) Upgrade Artemis 2.4.0

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9407?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9407: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Upgrade Artemis 2.4.0 > --------------------- > > Key: WFLY-9407 > URL: https://issues.jboss.org/browse/WFLY-9407 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > Labels: downstream_dependency > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

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

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9344?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9344: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > 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: 13.0.0.Beta1 > > > 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)

7 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9268) Upgrade Hibernate Search to 5.8.1 with Elasticsearch Support

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-9268?page=com.atlassian.jira.plugin.... ] Jason Greene updated WFLY-9268: ------------------------------- Fix Version/s: 13.0.0.Beta1 (was: 12.0.0.Final) > Upgrade Hibernate Search to 5.8.1 with Elasticsearch Support > ------------------------------------------------------------ > > Key: WFLY-9268 > URL: https://issues.jboss.org/browse/WFLY-9268 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Leandro Kersting de Freitas > Assignee: Jason Greene > Fix For: 13.0.0.Beta1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2018