2 reasons :
1) SQL Server sends "transaction started" and "transaction rolled
back/committed" messages to the driver "in band" with a query's execution
results (update counts, result sets, errors). The driver can't "see" the
messages until the results that precede them have been processed. S
Hello,
Context :
We are having a problem on the productive environment. We have an Enterprise
Application deplioyed on JBoss-4.0.3 with Hibernate 3.2.3 and SQLServer 2005.
We use sqljdbc driver version 1.1. We know there has been version 1.2 and 2.0
but the benchmark on our app is not so goood
I have used visualVM to count the active threads when I start the server and
test with 10 users :
- JBoss 4.2.3 : 120
- JBoss 5.0RC2 = 350
Here is the reason why my server is running out of native memory on JBoss 5.0
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewt
found this : http://jroller.com/rreyelts/date/20040909
After running some tests with the JVM, I've come to the conclusion that Sun's
JDK 1.4 allocates about 256K of address space per thread. I also ran some tests
with JDK 1.5, which seem to indicate that it was allocating about 1M of address
s
Hi Peter,
Thanks for that.
To be honest, I strongly doubt there is any problem on the physical server. I
have been using it for a couple of months doing intensive testing on my app
running on JBoss 4.2.3 with both JRE5 and JRE6 without encountering any JVM
problem. Since this JVM crash on JB
Please correct the above : the correct JVM setting that allows us to run our
test is :
| jvm_args: -Dprogram.name=pdm.bat -Xms768m -Xmx768m -XX:PermSize=512m
-XX:MaxPermSize=512m -XX:+Dis
|
| ableExplicitGC
|
However, if this works for 5, 10, 20 simulatenous users, it eventualy cras
Hi Peter,
Thanks for your feedback. My Windows 2003 SP2 server running in 32 bits mode
(with /3GB option in boot.ini) is set up with 4GB memory and 4GB paging.
The problem has been reproduced with both JRE-1.6.0_7 and JRE-1.5.0_15.
So I have tried to change my JVM options with increased Perm si
woops : forget to mention our JVM option at startup time :
| jvm_args: -Dprogram.name=pdm.bat -Xms1024m -Xmx1024m -XX:PermSize=256m
-XX:MaxPermSize=256m -XX:+DisableExplicitGC
|
Also : this is running on HP Server Quad Core / Windows 2003 SP2 / 4GB Memory.
When the JVM crashes the GC out
We have a JEE application running with EJB2 that we have migrated to EJB3.
Before migration, this app runs perfectly on JBoss 423 compiled on JDK5 with
runtime JRE5 and JRE6 (not at the same time though) up to 50 simulatneous users
on a single JBoss instance.
After migration to EJB3, we are ex
