I think Java Application Servers left a bad impression on alot of people back
in the early ejb2/jsf1 days. It wasn't only the specs that were not great
(ie. ejb2 entity beans) but also the containers that were implemented were
incredibly resource hungry memory pigs that took an eternity to boot up
Hi Pierre,
First maybe check under a more recent version (and official one ;)).
Then it is surely that stateful are not released properly (@remove).
Do you have a sample maven project showing this behavior easily?
Romain Manni-Bucau
Twitter: @rmannibucau
Blog: http://rmannibucau.wordpress.com/
Hi,
I've an application running on oe 3.1.4-xa-3 and I noticed that
StatefulEjbObjectHanlder are growing in memory.
I suspect a memory leak.
--
View this message in context:
http://openejb.979440.n4.nabble.com/statefulejbobjecthandler-growing-tp4669235.html
Sent from the OpenEJB User mailing
Hi
read quickly and will answer the same way.
Basically my opinion today is dev have a lot of needs. EE is not
perfect but matches one important need: something shareable and stable
enough to let enterprises base their future on it.
Of course you can use directly netty and disruptor to do someth
http://www.slideshare.net/ewolff/java-application-servers-are-dead
http://blog.paralleluniverse.co/2014/05/08/modern-java-pt2/
I like to get on Hacker News and read what what's new. Java is usually
flogged by the dynamic language mob, so I was surprised to see some
positive articles about Java.
I
Working with any issue :)
with apache-tomee-1.6.1-20140508.041112-152-jaxrs.zip
Thanks!!!
2014-05-06 10:02 GMT-05:00 José Luis Cetina :
> Ok, i will test it today.
>
>
> 2014-04-24 7:28 GMT-05:00 Andy Gumbrecht :
>
> I just updated and tested this on the 1.6.1-SNAPSHOT and it looks good to
>> g
Well, Andy has finished the 1.6.0.2 which is under VOTE.
He's starting to prepare everything for the 1.7.0 release. So hopefully he
can start maybe next week a VOTE on this.
It takes 3 days to VOTE and then one more to publish and get everything
synchronized.
>From my experience, the first shoot i
Hi,
I think you misunderstand CDI. CDI runs in a container and this container
manages the Beans you want to inject and inject other beans in this. If you
use the "new" Keyword from Java, then you instantiate the Bean/Class by
yourself and the container won't see it.
If you don't want to inject "E
Sorry bad question, as you mentionned its part of the 1.6.1, do you know when
this version will be released?
--
View this message in context:
http://openejb.979440.n4.nabble.com/Stateful-EJB-not-removed-after-Remove-annontation-tp4667763p4669206.html
Sent from the OpenEJB User mailing list arch
