[
https://issues.apache.org/jira/browse/OPENEJB-1955?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13510319#comment-13510319
]
Howard W. Smith, Jr. commented on OPENEJB-1955:
-----------------------------------------------
My persistence.xml looks like below. I thought I saw somewhere that I need to
keep jta and non-jta in persistence.xml. Please confirm.
<?xml version="1.0" encoding="UTF-8"?>
<persistence version="2.0"
xmlns="http://java.sun.com/xml/ns/persistence";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd";>
<persistence-unit name="mcmsPU" transaction-type="JTA">
<provider>org.eclipse.persistence.jpa.PersistenceProvider</provider>
<jta-data-source>jdbc/mcmsJta</jta-data-source>
<non-jta-data-source>jdbc/mcmsNonJta</non-jta-data-source>
<exclude-unlisted-classes>false</exclude-unlisted-classes>
<properties>
<property name="eclipselink.target-database"
value="org.eclipse.persistence.platform.database.DerbyPlatform"/>
<property name="eclipselink.jdbc.cache-statements" value="true" />
<property name="eclipselink.jdbc.cache-statements.size" value="100" />
<property name="eclipselink.logging.parameters" value="false" />
</properties>
</persistence-unit>
</persistence>
> TomEE 1.5.1 SNAPSHOT (and CDI beans) running slow on my production server
> -------------------------------------------------------------------------
>
> Key: OPENEJB-1955
> URL: https://issues.apache.org/jira/browse/OPENEJB-1955
> Project: OpenEJB
> Issue Type: Question
> Components: container system
> Affects Versions: 1.6.0
> Environment: Windows Server 2003, 32-bit, PrimeFaces 3.5 SNAPSHOT,
> PrimeFaces Push (Atmosphere/websockets) configured;
> Internet connection is powered by Verizon Wireless 4G
> Reporter: Howard W. Smith, Jr.
> Priority: Minor
> Labels: 2003, atmosphere, server, tomee, windows
> Fix For: 1.6.0
>
> Attachments: 20121128_profileLogin1_getOrderNumberList.jpg,
> 20121128_profileLogin1.jpg, 20121128_profileLogin2_getOrderNumberList.jpg,
> 20121128_profileLogin2.jpg, 20121128_profileLogin3_getOrderNumberList.jpg,
> 20121128_profileLogin3.jpg, 20121128_profileLogin_filterByDynamicSQL.jpg,
> 20121128_profileLogin_filterByNamedQuery.jpg,
> 20121128_profileLogin_initOrdersController1.jpg,
> 20121128_profileLogin_initOrdersController2.jpg,
> 20121128_profileLogin_initOrdersController3.jpg, catalina.2012-11-27.log,
> jvisualvm_20121127.csv, jvisualvm_20121127.html, jvisualvm_20121127.nps,
> jvisualvm.csv, jvisualvm.html, jvisualvm.nps,
> jvisualvm_tomee_excel_smaller.csv, jvisualvm_tomee.html, jvisualvm_tomee.nps,
> jvisualvm_tomee_smaller.csv, jvisualvm_tomee_smaller.html, web.xml
>
> Original Estimate: 612h
> Remaining Estimate: 612h
>
> I was working with Romain and Mark Struberg on this one, and decided to open
> an issue, so I could attach files and continue discussion here.
> My TomEE/CDI-managed-beans web application is running really slow on
> production server (Windows Server 2003 32-bit Verizon Wireless 4G internet
> connection); runs faster on Windows Server 2008 64bit (cablemodem internet
> connection).
> Currently in production, the Glassfish 3.1.2.2 and JSF-managed-beans version
> of the web application is running much faster than the
> TomEE/CDI-managed-beans version of the web application.
> Per Romain and Mark, I ran jvisualvm to provide some benchmarks.
> Please review attached files and confirm and advise.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
