[JNDI/Naming/Network] - Connection pool socket timeouts - appropriate recovery
by ousie
Hi,
We have a very unique issue at the moment with the following setup:
1. JBoss 4.0.3 SP1
2. Installed on Linux - Gentoo
3. MSSQL 2005 database
About once a day, at random times, a connection will just die to the database. By "just die" I mean a JBoss thread waits forever on:
| java.net.SocketInputStream.socketRead0(Native Method)
| java.net.SocketInputStream.read(SocketInputStream.java:129)
| java.io.DataInputStream.readFully(DataInputStream.java:178)
| java.io.DataInputStream.readFully(DataInputStream.java:152)
| net.sourceforge.jtds.jdbc.SharedSocket.readPacket(SharedSocket.java:826)
|
We discovered that the query was not even executed on the database, so query-timeout settings have no effect, it literally waits forever and we have to restart JBoss to fix this problem.
Is there a way to set the following socket timeouts on the connections in the connection pool:
1. timeout to wait for the connection to be established
2. timeout to wait for data to be returned on the socket
Thanks,
Gerrit
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179176#4179176
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179176
17 years, 7 months
[Remoting] - Re: Setting codebase in jboss ejb3 application has no efffec
by ron.sigal@jboss.com
Hi Emil,
Your question isn't related to Remoting, so I'm going to suggest you try the "Installation, Configuration & DEPLOYMENT" forum at http://www.jboss.com/index.html?module=bb&op=viewforum&f=61.
For what it's worth, I can point you to the $JBOSS/server/$CONFIG/conf/jboss-service.xml file, where you'll find the MBean configurations
| <!-- ==================================================================== -->
| <!-- Class Loading -->
| <!-- ==================================================================== -->
|
| <!-- A mini webserver used for dynamic and class and resource loading -->
| <mbean code="org.jboss.web.WebService"
| name="jboss:service=WebService">
| <!-- The Bind address and Port -->
| <attribute name="BindAddress">${jboss.bind.address}</attribute>
| <attribute name="Port">8083</attribute>
| <!-- The address to use for the host portion of the RMI codebase URL -->
| <attribute name="Host">${java.rmi.server.hostname}</attribute>
| <!-- Should non-EJB .class files be downloadable -->
| <attribute name="DownloadServerClasses">true</attribute>
| <!-- Should resources other than .class files be downloadable. Both
| DownloadServerClasses and DownloadResources must be true for resources
| to be downloadable. This is false by default because its generally a
| bad idea as server configuration files that container security
| information can be accessed.
| -->
| <attribute name="DownloadResources">false</attribute>
|
| <!-- Use the default thread pool for dynamic class loading -->
| <depends optional-attribute-name="ThreadPool"
| proxy-type="attribute">jboss.system:service=ThreadPool</depends>
| </mbean>
|
| <!-- ==================================================================== -->
| <!-- JBoss RMI Classloader - only install when available -->
| <!-- ==================================================================== -->
| <mbean code="org.jboss.util.property.jmx.SystemPropertyClassValue"
| name="jboss.rmi:type=RMIClassLoader">
| <attribute name="Property">java.rmi.server.RMIClassLoaderSpi</attribute>
| <attribute name="ClassName">org.jboss.system.JBossRMIClassLoader</attribute>
| </mbean>
|
Good luck, and if you solve your problem, it would be great if you could come back and post the solution.
-Ron
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4179165#4179165
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4179165
17 years, 7 months