I used Apache TomEE in my previous job for operating online election. 8
Apache TomEE instances with 2 Apache as frontend.

El dl., 31 ag. 2015 a les 17:42, Jonathan Fisher (<
[email protected]>) va escriure:

> We have 100+ instances of TomEE in production server hundreds of thousands
> of requests per day. We use every part of the JEE spec, from JSF, JMS, JTA,
> JAXB, EJB, CDI, JAXRS...
>
> *Jonathan S. Fisher*
> *VP - Information Technology*
>
> On Mon, Aug 31, 2015 at 4:25 AM, [email protected] <
> [email protected]> wrote:
>
> > Hi, I've been using first OpenEJB then TomEE in production for years. I'm
> > currently consulting for a company using TomEE in an 8 instance cluster
> > serving tens of millions of transactions per day 24/7 and currently 98.7%
> > up time over a two year period. We upgraded 1.6.0.2 to 1.7.3 (internal
> > Tomitribe supported version) last month, and we're still at 100% up time.
> > All container pools have been tuned upwards to fit the specific memory
> > profiles. Tuning is always use case specific, but rule of thumb is to
> > increase everything in moderation and benchmark after each increase. It's
> > fair to say that TomEE is extremely stable and most issues arise due to
> > application code. I know I'm biased, but you should have no doubts about
> > using TomEE in a production environment.
> >
> > Andy.
> >
> > [email protected]
> > http://www.tomitribe.com
> >
> > Sent from my mobile device.
> >
> > ----- Reply message -----
> > From: "Abdelhamid Meddeb" <[email protected]>
> > To: <[email protected]>
> > Subject: TomEE in production, feedback request
> > Date: Sat, Aug 29, 2015 10:16
> >
> > Hi guys,
> >
> > I appreciate so much the TomEE concept. I have done some works that
> > target it. But I have never faced its use in a real environment into
> > production with intensive use.
> >
> > I am looking for any feedback about this.
> >
> > Thanks in advance.
> >
> > --
> > *Abdelhamid Meddeb*
> > http://www.meddeb.net
> >
>
> --
> Email Confidentiality Notice: The information contained in this
> transmission is confidential, proprietary or privileged and may be subject
> to protection under the law, including the Health Insurance Portability and
> Accountability Act (HIPAA). The message is intended for the sole use of the
> individual or entity to whom it is addressed. If you are not the intended
> recipient, you are notified that any use, distribution or copying of the
> message is strictly prohibited and may subject you to criminal or civil
> penalties. If you received this transmission in error, please contact the
> sender immediately by replying to this email and delete the material from
> any computer.
>

Reply via email to