Re: Does TomEE support EJB 2?

Hi Aaron We didnt drop that support so it should work Le ven. 28 sept. 2018 20:10, Aaron a écrit : > Does TomEE support EJB 2? After upgrading our previous application server, > the new version puked up a bunch of errors about no longer supporting EJB 2 > entities (and that wasn't the only prob

Does TomEE support EJB 2?

Does TomEE support EJB 2? After upgrading our previous application server, the new version puked up a bunch of errors about no longer supporting EJB 2 entities (and that wasn't the only problem we faced). Does TomEE support legacy EJB 2 software, or will it want the code rewritten to be EJB 3 comp

RE: Apache Ignite initialization before EntityManagerFactory

Works like a charm, even with pretty old Progress jdbc driver! Thanks a lot Romain. Cheers, Dmitry -Original Message- From: Romain Manni-Bucau [mailto:rmannibu...@gmail.com] Sent: Thursday, September 27, 2018 10:03 PM To: users@tomee.apache.org Subject: Re: Apache Ignite initialization

Re: jdbc connection pool size 2

I'd just add to Jon's answer that setting a maxWait to 0 will help you to identify these issues, otherwise it can hides some undersizing problem during the tuning phase. Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: jdbc connection pool size 2

I tend to run with small connection pools and only increase them if its really necessary. If you do have something leaking a connection somewhere, its worth solving that rather than increasing the pool size. That said, I'd say a maxactive of 2 is very small, and maybe 10 would be a good starting po

Re: jdbc connection pool size 2

We have very long background processes working intensively with the DB. So I would guess that at least one connection is almost always in use. Two just is too few connections. Even if a much larger pool would maybe not really solve the problem, it would at least make it much less severe. If we las

Re: jdbc connection pool size 2

Yes, although it looks like you're also waiting 30 seconds to get a connection, which suggests maybe those 2 connections aren't coming back to the pool as well. Are you able to get a thread dump of the process? Jon On Fri, Sep 28, 2018 at 12:41 PM clemensx wrote: >

Re: jdbc connection pool size 2

I guess MaxActive 2 is the problem? -- Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Users-f979441.html

The cause of the exception is lost with the implementation of TransactionRolledbackException#writeReplace

We are migrating from OpenEjb 4.5.0 to OpenEjb 7.x and We are facing a regression in a test. The test is a simple scenario in which we store an entity and we expect to have an exception like "MyExampleStoreException". We used to loop into the retrieving throwable exception to check if our except

Re: jdbc connection pool size 2

Hello, are you able to use jmx to dump the datasource mbeans to see the actual config? (ensure to remove your credentials before sharing this ;)). Romain Manni-Bucau @rmannibucau | Blog | Old Blog

jdbc connection pool size 2

Hi, we use TomEE 7.0.4 productively in a Cloud Foundry environment. JDBC connections are only used via JPA (eclipselink). Usually after one day or so uptime we see these errors: org.apache.tomcat.jdbc.pool.PoolExhaustedException: [http-nio-8080-exec-10] Timeout: Pool empty. Unable to fetch a conn