Maximum No.of connections in Jboss

[Sujith manikkothu]

Hii,
How we can set the maximum No. of connections in Jboss? Which xml file we have to edit?I am using jboss 3.0.8 ..
Thanks,
Sujith

[Damanjit Kaur]

Hi,

Its in deploy directory , depending on which database u are using. if its hypersonic the default database then file name is hsqldb-service.xml

u will find the settings in
<mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" ....

for max,min no. of connections.

[Sujith manikkothu]

Hii,
In hsqldb-service.xml the maximum NO. of connections set is 50.But still i am getting error for 1 user out of 6 , when i tested with load runner and the exception shown in the server is sql exception...Can u help me to resolve this issue.
Thanks,
Sujith

[Damanjit Kaur]

Hi,

try again by changing the Criteria attribute in
<mbean code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool" ....

to ByNothing

I just know it has effect on connection pool since it distiguish between diff. connections according to this criteria.

[Damanjit Kaur]

also u have to be sure which directory u have specified in ur project for deploy, i mean is it all or default.

[Sujith manikkothu]

Hiii,
I am using default directory for deploying.But i think the problem is with connection.B'coz the exception in the server is :

2004-10-20 11:48:25,703 ERROR [STDERR] java.sql.SQLException: No operations allowed after connection closed.

Connection was closed explicitly by the application at the following location:

** BEGIN NESTED EXCEPTION **

java.lang.Throwable

STACKTRACE:

java.lang.Throwable
at com.mysql.jdbc.Connection.close(Connection.java:1061)
at com.aig.dashboard.common.SuperServlet.callJSP(SuperServlet.java:25)
at com.aig.dashboard.servlet.RoutingServlet.performTask(RoutingServlet.java:28)
at com.aig.dashboard.common.SuperServlet.doPost(SuperServlet.java:87)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:360)
at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294)
at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:558)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1714)
at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:505)
at org.mortbay.http.HttpContext.handle(HttpContext.java:1664)
at org.mortbay.http.HttpServer.service(HttpServer.java:879)
at org.jboss.jetty.Jetty.service(Jetty.java:460)
at org.mortbay.http.HttpConnection.service(HttpConnection.java:770)
at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:932)
at org.mortbay.http.HttpConnection.handle(HttpConnection.java:787)
at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:201)
at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:289)
at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:454)


** END NESTED EXCEPTION **


Is it because of not closing the connection properly??

With lots of thanks,
Sujith

[Damanjit Kaur]

Hi,

which bean type are u using. then also check settings in standardjboss.xml file for that bean type in container-configuration tag. there u will find diff. time settings. for each bean type.