Are you sure that under Tomcat the application is really using the Tomcat
connection pool? If not that would certainly account for the differences.
Even if Tomcat DBCP is configured, checking that the pool configurations
are similar would seem like an important check.
-Brett
On Mon, Apr 13,
I don't think that's the problem:
1. The same amount of heap is configured
2. I've checked with VisualVM and it uses much less than the provided
memory(ca. 250mbyte vs. 1024mbyte heap).
On Mon, Apr 13, 2015 at 4:54 AM, Bryan Pendleton
bpendleton.de...@gmail.com wrote:
I've tried to figure out
I know the Tomcat setup isn't using the clientdriver when it slows
down, because when I first tried to switch to the ClientDriver it
failed. After I copied the derbyclient.xxx.jar to tomcat/lib/, it
worked.
On Mon, Apr 13, 2015 at 9:51 AM, Dyre Tjeldvoll
dyre.tjeldv...@oracle.com wrote:
On
I'll be trying to do more logging.
Do you have any handy pointers to documentation?
To log SQL statements seems like the most promising:
https://db.apache.org/derby/docs/10.11/ref/rrefproper43517.html
I didn't find anything to log connection IDs (distinct/count).
I never tried JMX mbeans
And, by testing with a network server I think you can access JMX mbeans
with VisualVM/JConsole to check connection counts.
--
Kristian
13. apr. 2015 13:12 skrev Kristian Waagan krist...@apache.org:
Hi Øivind,
Have you turned on SQL-logging/-tracing in Derby to check the activity?
Possible
Hi Øivind,
Have you turned on SQL-logging/-tracing in Derby to check the activity?
Possible things to check:
o connection IDs (distinct/count)
o expensive connection validation queries (not all of these are direct SQL,
check pool docs/conf)
o commits?
o different queries?
While one would expect
Have you put the app under a profiler to see what components are taking
the most time in each container? Seems like the best way to get some
facts on the table.
On Sun, 2015-04-12 at 23:50 +0200, Øyvind Harboe wrote:
Hi,
I'm having problems with performance degrading dramatically when I
I did. See the stacktrace in my initial post.
On Apr 13, 2015 3:18 PM, Tim Watts t...@cliftonfarm.org wrote:
Have you put the app under a profiler to see what components are taking
the most time in each container? Seems like the best way to get some
facts on the table.
On Sun, 2015-04-12