[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jan-Willem Gmelig Meyling (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jan-Willem Gmelig Meyling commented on WFLY-10531:
--------------------------------------------------
Imho the regression is severe enough for it to be included in WF15. Given the rather trivial and well-tested fix, I don't see why not to include it. +1 for including it in WF15 here.
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (DROOLS-3061) [DMN Designer] Automatic Layout Feature
by Jozef Marko (Jira)
[ https://issues.jboss.org/browse/DROOLS-3061?page=com.atlassian.jira.plugi... ]
Jozef Marko commented on DROOLS-3061:
-------------------------------------
[~roger600] thanks for the summary, I filed issues below so we can plan for next sprints.
Please anyone feel free to add more details, however I think more details we be added later, just before implementation start. Also please notice that probably each BAPL will be cloned to community project to not assign community jiras epic from BAPL project.
- BAPL-1097
- BAPL-1099
- BAPL-1100
- BAPL-1101
- BAPL-1102
> [DMN Designer] Automatic Layout Feature
> ---------------------------------------
>
> Key: DROOLS-3061
> URL: https://issues.jboss.org/browse/DROOLS-3061
> Project: Drools
> Issue Type: Epic
> Components: DMN Editor
> Reporter: Jozef Marko
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> DMN Designer should *autolayout* new imported DMN models. The *autolayout* should position DRG diagram nodes into horizontal layers to minimize crossing of connectors with respect of *Top-Down* importance. It means if nodes *Layer B* are inputs for nodes in *Layer A* then the *Layer B* will be below *Layer A*. The *autolayout* should also try to minimize scrolling needed to see whole DRG diagram.
> User should also have possibility to invoke *autolayout* feature any time during designing the diagram. In this case the action should be undoable with the *Undo* toolbar button.
> The approach used to achieve this is the Sugiyama Method, which is done in 4 steps. Each step have its own set of algorithms. For each step, we selected one of the available algorithms to implement, based on our current needs and time to develop:
> *Step 1 - Cycle breaking:* We break cycles in diagram by reversing some edges (they are de-reversed in the end). This step are required because we need ending points in step 2 while sweeping through graph;
> *Step 2 - Layering:* We sweep through graph (diagram) and put each node (vertex) in a layer, based on it's distance from others node. For edges that crosses multiple layers, we create virtual vertices connecting those. They are removed at the end.
> This approach usually puts the start nodes at the top and the deepest nodes at the end. In the current implementation we're using Longest Path algorithm. A better approach can be developed in future using Network Simplex;
> *Step 3 - Node Ordering:* We order each node (vertex) inside its layers in order to reduce crossing, using median. Another approach that can be used is barycenter.
> *Step 4 - Node Positioning:* We de-reverse nodes reversed in step 1 and remove virtual nodes reconnecting the concrete nodes. Then we calculate the position of each node. This step can be divided in two steps: one for horizontal position and other for vertical for better positioning. Currently we're using a simple approach: every block of nodes inside the layers is centered and the distance between layers is the same. So it will produce results like the attachment "Automatic Layout Demo".
> *Architecture*
> From the design of view the goals are:
> * +Layout Public interface & DMN implementation+
> ** The goal for this API is to provide the layout declaration data for an input Graph (DMN, BPMN, etc) instance. It will NOT mutate the graph structure and/or data at all. This way it will provide methods for calculating the candidate locations for the graph elements. even could be the case the elements must be resized as well, and it returns on some result data object that specifies the necessary updates to be done on the elements. So the resulting layout data will be consumed by another component that will use the _command API_ in order to perform the necessary updates (location, size) for the graph' elements.
> ** Build a well defined layout API (shared) on some _api_ module
> ** Build the requested layout implementation specific for DMN inside some DMN shared module (considering the implementation is shared between client and server)
> ** Any other common or base classes can be placed inside the _commons_ module
> * +Designer integration+
> ** Once having the layout API and implementations, next step is to consume this API in order to obtain the layout data and use it to mutate the graph structure. So we need some kind of component for this, for example we can name it as _LayoutExecutor_.
> ** Create some default layout executor which will consume the layout API and use the command API to perform the updates on the model (graph) via "commands", this way we can undo/redo all the operations on the designer
> ** [Optional] This designer integration can be done as generic, and so reuse it for other domains like BPMN, or just specific for DMN
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (ELY-1680) IBM, failing KeyStoreSuiteChild.testGetCertificateChainBinary
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/ELY-1680?page=com.atlassian.jira.plugin.s... ]
Jiri Ondrusek reassigned ELY-1680:
----------------------------------
Assignee: Jiri Ondrusek
> IBM, failing KeyStoreSuiteChild.testGetCertificateChainBinary
> -------------------------------------------------------------
>
> Key: ELY-1680
> URL: https://issues.jboss.org/browse/ELY-1680
> Project: WildFly Elytron
> Issue Type: Bug
> Components: Testsuite
> Affects Versions: 1.6.1.Final
> Reporter: Martin Choma
> Assignee: Jiri Ondrusek
> Priority: Major
> Fix For: 1.7.0.CR4
>
> Attachments: ldap-keystore-gen.sh
>
>
> {code}
> [ERROR] testGetCertificateChainBinary(org.wildfly.security.ldap.KeyStoreSuiteChild) Time elapsed: 0.057 s <<< FAILURE!
> org.junit.ComparisonFailure: expected:<CN=[firefly_binary], OU=Elytron, O=Elyt...> but was:<CN=[localhost], OU=Elytron, O=Elyt...>
> at org.wildfly.security.ldap.KeyStoreSuiteChild.testGetCertificateChainBinary(KeyStoreSuiteChild.java:136)
> at org.wildfly.security.ldap.DirContextFactoryRule$1.evaluate(DirContextFactoryRule.java:218)
> {code}
> If I switch order of certificates in chain, then test passes.
> {code}
> diff --git a/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java b/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java
> index d8095867a..cda635beb 100644
> --- a/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java
> +++ b/src/test/java/org/wildfly/security/ldap/KeyStoreSuiteChild.java
> @@ -133,8 +133,8 @@ public class KeyStoreSuiteChild {
> Certificate[] chain = keyStore.getCertificateChain("firefly_binary");
> Assert.assertNotNull(chain);
> Assert.assertEquals(2, chain.length);
> - Assert.assertEquals("CN=firefly_binary, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[0]).getSubjectDN().toString());
> - Assert.assertEquals("CN=localhost, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[1]).getSubjectDN().toString());
> + Assert.assertEquals("CN=firefly_binary, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[1]).getSubjectDN().toString());
> + Assert.assertEquals("CN=localhost, OU=Elytron, O=Elytron, L=Elytron, ST=Elytron, C=UK", ((X509Certificate)chain[0]).getSubjectDN().toString());
> }
> {code}
> -For some reason I want able to debug code with -Dmaven.surefire.debug (Breakpoint was never hit) to find out which calls switch the order.-
> It takes long (5min) for debugger to attach to code.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11198) Session draining on stopped worker won't complete if further requests are made on balancer
by Jan Kašík (Jira)
[ https://issues.jboss.org/browse/WFLY-11198?page=com.atlassian.jira.plugin... ]
Jan Kašík updated WFLY-11198:
-----------------------------
Description:
When disabling worker with {{/subsystem=modcluster/proxy=default:stop(waittime=0)}}, the contexts are switched to {{disabled}} state. If there no further requests (on the same context which session currently times out) are made on a balancer, session correctly times out, contexts switch to {{stopped}} state and everything is OK.
However, when I run same stop operation, wait until contexts are switched into {{disabled}} state and in time in which sessions time out I make more requests on balancer, contexts will never switch to {{stopped}} state and session draining never completes. This happens intermittently (~60% of cases with 10 requests made after {{disabled}} state is in place).
was:
When disabling worker with {{/subsystem=modcluster/proxy=default:stop(waittime=0)}}, the contexts are switched to {{disabled}} state. If there no further requests (on the same context which session currently times out) are made on a balancer, session correctly times out, contexts switches to {{stopped}} state and everything is OK.
However, when I run same stop operation, wait until contexts are switched into disabled state and in time in which sessions time out I make more requests on balancer, contexts will never switch to {{stopped}} state and session draining never completes. This happens intermittently (~60% of cases with 10 requests made after {{disabled}} state is in place).
> Session draining on stopped worker won't complete if further requests are made on balancer
> ------------------------------------------------------------------------------------------
>
> Key: WFLY-11198
> URL: https://issues.jboss.org/browse/WFLY-11198
> Project: WildFly
> Issue Type: Bug
> Components: mod_cluster
> Affects Versions: 15.0.0.Alpha1
> Reporter: Jan Kašík
> Assignee: Radoslav Husar
> Priority: Major
>
> When disabling worker with {{/subsystem=modcluster/proxy=default:stop(waittime=0)}}, the contexts are switched to {{disabled}} state. If there no further requests (on the same context which session currently times out) are made on a balancer, session correctly times out, contexts switch to {{stopped}} state and everything is OK.
> However, when I run same stop operation, wait until contexts are switched into {{disabled}} state and in time in which sessions time out I make more requests on balancer, contexts will never switch to {{stopped}} state and session draining never completes. This happens intermittently (~60% of cases with 10 requests made after {{disabled}} state is in place).
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11122) javassist-3.22.0-GA.jar shipped with WildFly 12 is incompatible with Java 11
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-11122?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski resolved WFLY-11122.
---------------------------------------
Resolution: Out of Date
✘-INT ~/redhat/git/wildfly [master|⚑ 1]
10:50 $ mvn dependency:list | grep javassist
[INFO] org.javassist:javassist:jar:3.23.1-GA:test
[INFO] org.javassist:javassist:jar:3.23.1-GA:compil
> javassist-3.22.0-GA.jar shipped with WildFly 12 is incompatible with Java 11
> ----------------------------------------------------------------------------
>
> Key: WFLY-11122
> URL: https://issues.jboss.org/browse/WFLY-11122
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Environment: java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> Linux
> uname -r
> 3.10.0-229.el7.x86_64
> Reporter: Kausik Ghatak
> Assignee: Bartosz Baranowski
> Priority: Major
>
> 'javassist-3.22.0-GA.jar' is incompatible with Java 11 (see https://github.com/jboss-javassist/javassist/issues/194 ). Below a stack trace is provided.
> We also noticed that replacing this jar with 3.23 fixes the issue.
> Request to provide a patch for WildFly12 with appropriate javassist jar that is compatible with Java 11.
> =================================================
> 2018-10-05 16:06:09,730 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.persistenceunit."our-app.ear/server-core.jar#ourmod_model_persistence": org.jboss.msc.service.StartException in service jboss.persistenceunit."our-app.ear/server-core.jar#ourmod_model_persistence": javax.persistence.PersistenceException: [PersistenceUnit: ourmod_model_persistence] Unable to build Hibernate SessionFactory
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:195) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:125) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.wildfly.security.elytron-private@1.2.2.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:650)
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:209) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834) [java.base:]
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: ourmod_model_persistence] Unable to build Hibernate SessionFactory
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:953) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:883) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate.jipijapa-hibernate5//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:167) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> ... 9 more
> Caused by: org.hibernate.MappingException: Could not get constructor for org.hibernate.persister.entity.SingleTableEntityPersister
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:123) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:77) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:354) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:422) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:880) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> ... 11 more
> Caused by: org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:91) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:116) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:388) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:518) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:124) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java.base:]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [java.base:]
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [java.base:]
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) [java.base:]
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:96) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 15 more
> Caused by: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java.base:]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [java.base:]
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [java.base:]
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) [java.base:]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:88) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 24 more
> Caused by: java.lang.NullPointerException
> at org.javassist//javassist.util.proxy.SecurityActions.setAccessible(SecurityActions.java:103) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass3(DefineClassHelper.java:151) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass2(DefineClassHelper.java:134) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass(DefineClassHelper.java:95) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:131) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:530) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:515) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:451) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:422) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.hibernate//org.hibernate.proxy.pojo.javassist.JavassistProxyFactory.postInstantiate(JavassistProxyFactory.java:72) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:164) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:164) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:60) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 29 more
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-11122) javassist-3.22.0-GA.jar shipped with WildFly 12 is incompatible with Java 11
by Bartosz Baranowski (Jira)
[ https://issues.jboss.org/browse/WFLY-11122?page=com.atlassian.jira.plugin... ]
Bartosz Baranowski reassigned WFLY-11122:
-----------------------------------------
Assignee: Bartosz Baranowski (was: Jason Greene)
> javassist-3.22.0-GA.jar shipped with WildFly 12 is incompatible with Java 11
> ----------------------------------------------------------------------------
>
> Key: WFLY-11122
> URL: https://issues.jboss.org/browse/WFLY-11122
> Project: WildFly
> Issue Type: Bug
> Components: Server
> Affects Versions: 12.0.0.Final
> Environment: java -version
> java version "11" 2018-09-25
> Java(TM) SE Runtime Environment 18.9 (build 11+28)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11+28, mixed mode)
> Linux
> uname -r
> 3.10.0-229.el7.x86_64
> Reporter: Kausik Ghatak
> Assignee: Bartosz Baranowski
> Priority: Major
>
> 'javassist-3.22.0-GA.jar' is incompatible with Java 11 (see https://github.com/jboss-javassist/javassist/issues/194 ). Below a stack trace is provided.
> We also noticed that replacing this jar with 3.23 fixes the issue.
> Request to provide a patch for WildFly12 with appropriate javassist jar that is compatible with Java 11.
> =================================================
> 2018-10-05 16:06:09,730 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.persistenceunit."our-app.ear/server-core.jar#ourmod_model_persistence": org.jboss.msc.service.StartException in service jboss.persistenceunit."our-app.ear/server-core.jar#ourmod_model_persistence": javax.persistence.PersistenceException: [PersistenceUnit: ourmod_model_persistence] Unable to build Hibernate SessionFactory
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:195) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:125) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.wildfly.security.elytron-private@1.2.2.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:650)
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:209) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1378)
> at java.base/java.lang.Thread.run(Thread.java:834) [java.base:]
> at org.jboss.threads@2.3.1.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
> Caused by: javax.persistence.PersistenceException: [PersistenceUnit: ourmod_model_persistence] Unable to build Hibernate SessionFactory
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:953) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:883) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate.jipijapa-hibernate5//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
> at org.jboss.as.jpa//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:167) [wildfly-jpa-12.0.0.Final.jar:12.0.0.Final]
> ... 9 more
> Caused by: org.hibernate.MappingException: Could not get constructor for org.hibernate.persister.entity.SingleTableEntityPersister
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:123) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:77) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:354) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:422) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:880) [hibernate-entitymanager-5.1.10.Final.jar:5.1.10.Final]
> ... 11 more
> Caused by: org.hibernate.HibernateException: Unable to instantiate default tuplizer [org.hibernate.tuple.entity.PojoEntityTuplizer]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:91) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructDefaultTuplizer(EntityTuplizerFactory.java:116) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.EntityMetamodel.<init>(EntityMetamodel.java:388) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.entity.AbstractEntityPersister.<init>(AbstractEntityPersister.java:518) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.persister.entity.SingleTableEntityPersister.<init>(SingleTableEntityPersister.java:124) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java.base:]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [java.base:]
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [java.base:]
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) [java.base:]
> at org.hibernate//org.hibernate.persister.internal.PersisterFactoryImpl.createEntityPersister(PersisterFactoryImpl.java:96) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 15 more
> Caused by: java.lang.reflect.InvocationTargetException
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [java.base:]
> at java.base/jdk.internal.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) [java.base:]
> at java.base/jdk.internal.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [java.base:]
> at java.base/java.lang.reflect.Constructor.newInstance(Constructor.java:490) [java.base:]
> at org.hibernate//org.hibernate.tuple.entity.EntityTuplizerFactory.constructTuplizer(EntityTuplizerFactory.java:88) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 24 more
> Caused by: java.lang.NullPointerException
> at org.javassist//javassist.util.proxy.SecurityActions.setAccessible(SecurityActions.java:103) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass3(DefineClassHelper.java:151) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass2(DefineClassHelper.java:134) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.DefineClassHelper.toClass(DefineClassHelper.java:95) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.FactoryHelper.toClass(FactoryHelper.java:131) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass3(ProxyFactory.java:530) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass2(ProxyFactory.java:515) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass1(ProxyFactory.java:451) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.javassist//javassist.util.proxy.ProxyFactory.createClass(ProxyFactory.java:422) [javassist-3.22.0-GA.jar:3.22.0-GA]
> at org.hibernate//org.hibernate.proxy.pojo.javassist.JavassistProxyFactory.postInstantiate(JavassistProxyFactory.java:72) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.PojoEntityTuplizer.buildProxyFactory(PojoEntityTuplizer.java:164) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.AbstractEntityTuplizer.<init>(AbstractEntityTuplizer.java:164) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> at org.hibernate//org.hibernate.tuple.entity.PojoEntityTuplizer.<init>(PojoEntityTuplizer.java:60) [hibernate-core-5.1.10.Final.jar:5.1.10.Final]
> ... 29 more
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months
[JBoss JIRA] (WFLY-10531) Wildfly leaks ActiveMQ connections
by Jiri Ondrusek (Jira)
[ https://issues.jboss.org/browse/WFLY-10531?page=com.atlassian.jira.plugin... ]
Jiri Ondrusek commented on WFLY-10531:
--------------------------------------
[~sebek64] Unfortunately I'm not the right person to answer this question.
May I ask you, [~jmesnil] , if there is any chance to merge it into wildfly 15?
> Wildfly leaks ActiveMQ connections
> ----------------------------------
>
> Key: WFLY-10531
> URL: https://issues.jboss.org/browse/WFLY-10531
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 13.0.0.Final
> Environment: openjdk 8 / openjdk 9, Linux
> Reporter: Marcel Šebek
> Assignee: Jeff Mesnil
> Priority: Major
> Attachments: WFLY-10531-ear-1.0.ear, WFLY10531.zip
>
>
> After upgrading our application from wildfly 12 to 13, the app started to crash after a while (hours, days, depending on circumstances). It crashes on
> IJ000453: Unable to get managed connection for java:/JmsXA
> and other errors (it simply cannot perform all the jobs it contains). I found that when shutting down the server which has been running for a while, I can see a bunch of these messages in the log:
> WARN [org.jboss.jca.core.connectionmanager.pool.strategy.PoolByCri] (ServerService Thread Pool -- 117) [:::] IJ000615: Destroying active connection in pool: ActiveMQConnectionDefinition (org.apache.activemq.artemis.ra.ActiveMQRAManagedConnection@2f37f69)
> Bascially, the longer the server was running, more of these messages are shown. I cannot find a way how to reproduce the issue. When the server runs for short time but with some load, no connection is leaked (or just one, rarely). On the other side, it leaks connections even without any particularly high load (just a few requests and @Schedule jobs) when running for longer time.
> It may also be a bug in our application, which just happen to have more serious impact with the new wildfly version.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 9 months