Possible to configure per connection timeout values?

hi,
please, does anybody know how (or whether or not it is even possible) to configure a "PER CONNECTION" timeout on the connections - created by jndi - to an ldap server?
my understanding is that setting the "com.sun.jndi.ldap.connect.timeout" property on the javax.naming.directory.InitialDirContext sets a _global_ timeout value for _all_ connections created/managed by that InitialDirContext (that is, with a "PER CONTEXT" scope).
however, what i would like to do instead, is somehow configure a different timeout value for each individual connection that a InitialDirContext might know about.
the first solution that will probably pop in your head is "connection pool". however, the app sets "java.naming.ldap.factory.socket" property to a custom socket factory class. according to the following paragraph from the jndi tutorial, that disqualifies the app from using connection pools:
"There are a couple of environment properties that automatically disqualify a Context instance from using a pooled connection. A Context instance cannot use a pooled connection if it has its "java.naming.ldap.factory.socket" property set to a custom socket factory class, or its "java.naming.security.sasl.callback" property set to a custom callback handler class, or its "com.sun.jndi.ldap.trace.ber" property set to enable protocol tracing."
http://java.sun.com/products/jndi/tutorial/ldap/connect/config.html
even if we could use connection pools, we still wouldn't be able to set "per connection" timeout values. would we?
one proposed solution is to completely rip out jndi from the app and replace it with the netscape directory sdk for java. to me, that seems like too drastic a measure though - given the project's time-constraints (the way the app was originally designed does not lend itself to a straight-forward "pop-out/drop-in" type replacement). i was hoping there would be a simpler alternative (a jndi-based configuration type solution, for example).
any suggestions would be gratefully appreciated. thanks in advance for your replies.

Enable the Default Host option in the AirPort Admin Utility, use the IP address you have assigned to your server.

Similar Messages

Help configuring server connection timeout

Hello I'm running JMS 3.6 SP3 in Windows and I'm trying to configure
the time it takes to generate a
[C4002]: Read packet failed. - cause: java.net.SocketException: Connection reset
message.
I've set up the following configuration, but it takes about 1:45-2:00 minutes to get the message.
Here's the configuration:
imqAddressList=mq://localhost:7676/jms
imqPingInterval=10
imqReconnectAttempts=-1
imqReconnectEnabled=true
imqReconnectInterval=10000
I would like this at around 30 seconds or less if possible.
Any help would be appreciated

Thanks for the reply.
In regards to your queustion I am running as JMS as my configuration.
Here's me queue receiver code that you wanted to look at.
import javax.jms.*;
import javax.naming.NamingException;
import java.util.ArrayList;
import java.util.Iterator;
import java.util.List;
import java.util.Date;
public class QueueReceiver extends Thread implements ExceptionListener, JMSListener {
String queueName = null;
QueueConnectionFactory queueConnectionFactory = null;
javax.jms.Queue queue = null;
QueueConnection queueConnection = null;
QueueSession queueSession = null;
QueueReceiver queueReceiver = null;
TextMessage message = null;
TextListener textListener = null;
// List of listeners that will be started from the calling applications
private List listeners = new ArrayList();
public QueueReceiver(String queueName) {
// Store the queueName
this.queueName = queueName;
} // End of QueueReceiver
public void run() {
createConnection();
} // End of run()
public synchronized void addJMSListener(JMSListener l) {
listeners.add(l);
} // End of addJMSListener
public synchronized void removeJMSListener(JMSListener l) {
listeners.remove(l);
} // End of removeJMSListener
* This event will fire off that something has occurred. This will then
* be picked up from the calling application
* @param message String The message to pass back.
private synchronized void fireJMSEvent(String message) {
JMSEvent jmsEvent = new JMSEvent(this, message);
Iterator eventlisteners = listeners.iterator();
while (eventlisteners.hasNext()) {
((JMSListener) eventlisteners.next()).jmsReceived(jmsEvent);
} // End of fireJMSEvent
* This onException event is activated with a JMSException from the JMS Server
* For a complete list of available codes refer to the JavaDevelopers Guide/
* @param e JMSException The exception.
public void onException(JMSException e) {
if (e.getErrorCode() == "C4073") {
fireJMSEvent("Queue in use");
// Kill the Queue
queueConnection.close();
} else{
// This is for all other cases
fireJMSEvent("Network Error");
try{
queueConnection.close();
createConnection();
} catch (Exception ee) {
System.out.println("Attempting reconnection failure");
} //end onException
* This will catch and throw the JMSEvents received by it.
* @param event JMSEvent The JMSEvent
public void jmsReceived(JMSEvent event) {
// This event is from the TextListener stating that a message has been received
if (event.getMessage() == "Message Received") {
fireJMSEvent("Message Received");
} //End of jmsEvent
* Create the connectio to the queue
public void createConnection(){
boolean bolSkip = false;
if (queueConnectionFactory == null){
try {
queueConnectionFactory = SampleUtilities.getQueueConnectionFactory();
} catch (NamingException e) {
System.out.println("Exception = " + e.getMessage());
fireJMSEvent("Invalid name supplied");
bolSkip = true;
if (!bolSkip) {
try {
queueConnection = queueConnectionFactory.createQueueConnection();
queueConnection.setExceptionListener(this);
queueSession = queueConnection.createQueueSession(false,
Session.AUTO_ACKNOWLEDGE);
queue = (javax.jms.Queue) SampleUtilities.jndiLookup(queueName);
} catch (JMSException e) {
onException(e);
bolSkip = true;
} catch (Exception e) {
fireJMSEvent("Server not available");
bolSkip = true;
* Create session and receiver.
* Register message listener (TextListener).
* Start message delivery; listener displays the message obtained.
* Only do this if everything above was ok.
if (!bolSkip) {
try {
queueReceiver = queueSession.createReceiver(queue);
textListener = new TextListener();
textListener.addJMSListener(this);
queueReceiver.setMessageListener(textListener);
queueConnection.start();
// if successful to this point send back to calling app that the server is set up
fireJMSEvent("Server Started");
} catch (JMSException e) {
onException(e);
} // End of Class QueueReceiver
By the way what is the latest version of JMS for Windows?

Windows Fax Connection Timeout Value

Like for most, sending a fax is a rare event and used to work with the currently installed hardware but doesn't with Win 8.1. It has been about a year since I sent a fax so I don't know when it stopped working. What is happening is that the fax number
gets dialed, the fax handshake starts and then Windows disconnects the modem after about 5 second which isn't long enough to complete the fax handshake. The phone line is still active and the receiving fax machine is still trying to complete
the handshake. It seems there should be a configurable setting for how long to allow to complete the handshake but I can't find it. Any suggestions?

Also, make sure the phone cable is securely plugged-in.
Yes, that sounds a bit silly, but I've had a loose cable cause just about the same thing you're describing.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Http connection timeout for business services from proxy service?

I've only done limited experiments in ALSB (2.1) at this point, but a question occurred to me, and I can't find this mentioned in the docs anywhere.
When a proxy service configures a connection to a downstream business service through HTTP, is it possible to configure an http connection timeout value? This will cause the connection attempt to fail if it takes too long to determine whether the connection attempt succeeded or failed.
I've heard that this is one advantage that Axis has over JAXRPC/SAAJ, as a connection timeout value can be specified.

Hello Billy
Thanks for the reply. I thought there may be some implementation of begin_request in another environment that had the option to specify a connect timeout. But as you have explained, it doesn't work like that. As always, I learn something every day!
So realistically if I want to stop the calling process hanging in the event of the server not being available, I need use the message based approach...send a message containing the request to another process via a message queue and attach to the reply queue and wait for a message comming back with a timeout. Does that sound like a reasonable approach?
Thanks
David

ASA TCP Idle Connection Timeout Suspense

Hello I upgraded our Cisco ASA 5520 with a Cisco ASA 5585. Though both ASA were configured with default TCP Idle Connection Timeout values people are now starting to complaint that idle SSH connections are being terminated. This is proper behavior but they were claiming it didn't occur with the old firewall. Our users are setting keepalives for 1800 seconds to get around this before I can bump the setting to infinite (setting 0). Is there a bug with the feature in older ASA OS?

Hi,
Before looking for a bug I would check the ASA logs (hopefully you are storing them to a separate Syslog server) and see why the connections are torn down (Teardown reason) and how long have they been on the ASAs connection table before they were torn down.
You also have the option to perform traffic capture on the ASA for the traffic in question and confirm why or which party terminates the connection.
I guess you can use the MPF on the ASA to configure separate idle timeouts for just these SSH Connections if you do not want to touch the global timeout values.
I have not run into any problems with the timeout settings on the older softwares. In the newer softwares (8.3+) I have run into these problems. In those situation the ASA has not removed the connection that have reached the timeout value. I have seen connection that have been idle for over 1000h.
- Jouni

Re: Can't Connect: Connection Timeout?

What could be the possible reason for getting "connection timeout" after failing to connect to the internet? After going to Network Prefs, clicking on my network, being prompted for my WPA security password and getting the message "connection failed, " this is replaced with connection timeout?
Reset my modem and AEBS (unplugged and plugged back in), and was able to connect.
Any relation to whether or not, under the Airport tab of Network Prefs, "Disconnect from wireless networks when logging out" is checked or not? I don't have it checked, and don't remember having it checked, but someone on the Airport Discussion boards said it should be checked?
What other possible reasons fro getting a connection timeout? MY ISP says there is nothing from their side that would timeout my connection.

After reading this entire thread, I conclude that I am having the same problems. Here's what I'm seeing:
* The problem only happens when using WPA; switching my WAP to WEP or no security makes all my Mac's consistently connect just fine.
* When the problem occurs, I am prompted for the WPA password; when I type in the password and click "connect", it alternates between "Connection timeout" and "Invalid password" (I'm positive that the password is correct; it's short, simple, and I'm using the "show password" checkbox to verify that it's correct).
* My Intel 10.5.2 MBP usually connects ok (airport card -- 802.11b/g).
* My PPC 10.5.2 iMac usually connects ok (airport card -- 802.11b/g, sometimes it asks for the WPA password once even though it's stored in my keychain).
* My Intel 10.5.2 24" iMac rarely connects ok (airport extreme card -- 802.11b/g/n, with the symptoms above).
* Windows laptops connect just fine.
* There seem to be several different WAPs discussed on this thread; I'm wondering if there is some kind of WPA protocol issue in 10.5.2 because I can consistently WPA connect just fine to a Linksys WRT54GL, but I see the symptoms described above with Cisco Aironet 1131AG's.
To reiterate: the problem most consistently occurs on an Intel iMac with an airport extreme card with OS X 10.5.2 when connecting to my Cisco Aironet 1131AG when WPA is enabled. It definitely does not occur when WEP or no wireless security is enabled. It rarely happens with a PPC iMac and an Intel MBP, both with OS X 10.5.2 and airport cards (regardless of network security settings and WAP used).

Changing policy domain timeout value

Hi Idm folks,
Can we configure a different timeout values on policy domains protecting different applications?
For example; policy domain /domain01/... has a 15 miunte idle session timeout and policy doomain02/... would have a 6 hour idle session timeout.
I don't think we can, wanted to check if anyone had ever came across this requirement?
thanks!

For different applications are you using different webgates? In that case you can think of using separate host identifiers for different webgates and create policies for host identifiers and you can have different timeout values for webgates.
BUT, in a SSO scenario what kind of complication it will bring, needs to be evaluated on the environment (mainly the central and application webgate domain for obSSOCookie) and requirements. This can be an interesting exercise, I guess. :)

CSM sticky timeout value - is this an idle timeout value?

We have sticky groups configured in our CSM, with an timeout value of 60 minutes. My question is does the timeout value reference an 'idle' value, such as a user disconnected from the session, and now that timer is counting down from the 60 minutes to 0, to remove the stale session out of CSM?
Or is this some other kind of value? If so, what does the value actually represent?
Group CurrConns Timeout Type
17     290       60       src-ip netmask 255.255.255.255
Also, from this info below, is "this" timeout value in seconds, or should this show in minutes? Or is this a bug that I need to resolve by updating the CSM version? We're still on v2.2(1).
CSM with SSL WS-X6066-SLB-S-K9
Thanks, Tony
switch#sho mod csm 1 sticky group 17
group   sticky-data              real              timeout
17      ip 10.x.x.x            10.x.x.x            3469
17      ip 10.x.x.x            10.x.x.x            3275
17      ip 10.x.x.x            10.x.x.x            3016
17      ip 10.x.x.x            10.x.x.x            2791
17      ip 10.x.x.x            10.x.x.x            879

Hi Ajay, thank you for the response. From your reply, "It appears that you have configured the sticky timeout value higher then the default value. So the sticky timeout value is in minutes," we set each group to have a 60 minute timeout value. I had read from another string that the timeout values I'm seeing in this table were incorrectly displayed, due to an upgraded needed on the CSM. We're running 2.2(1), and I thought I remember reading 4.2.2 was required to correct this bug?
switch#sho mod csm 1 sticky group 17
group   sticky-data              real              timeout
17      ip 10.x.x.x            10.x.x.x            3469
17      ip 10.x.x.x            10.x.x.x            3275
17      ip 10.x.x.x            10.x.x.x            3016
17      ip 10.x.x.x            10.x.x.x            2791
17      ip 10.x.x.x            10.x.x.x            879

Possible wrong default http proxy outgoing connection-timeout in the CDM

FYI Can anyone confirm this?
It appears that the CDM (5.0.3.5) is setting the proxy connection-timeout to a value of 300. The units of the CLI command are in microseconds so this is an extremely low connection timeout for WAN environments. The outgoing proxys are failing. The correct default value should be 300000 which equals 300 milliseconds.
It appears that the CDM default configuration was setup thinking that the units are milliseconds. We added the 300000 value to the device group and saw that the CE no longer displays the timeout value meaning that it is at the default value of 300 milliseconds or 300000 microseconds.

As far as I know, the 5.0 shows the default as 300 milliseconds. The configurable time is also in microseconds. Have you checked if this is a known bug? You may use the Bug Toolkit to check.

Web Service Connection Timeout - Whats the default value?

Does anyone know the default value of connection timeout property in Web Service activity?
One of my web service takes longer time for processing. So just wanted to know this value for debugging.
Thanks,
Nith

Hi Dexter,
In your case, we can try to increasing the size of the connection pool to resolve the issue. By default, the Max Pool Size is 100. You can refer to the similar issue below:
http://social.msdn.microsoft.com/Forums/en-US/c57c0432-c27b-45ab-81ca-b2df76c911ef/timeout-expired-the-timeout-period-elapsed-prior-to-obtaining-a-connection-from-the-pool?forum=adodotnetdataproviders
Since the issue is related with ADO.NET. I suggestion you post the question in the following forum:
http://social.msdn.microsoft.com/Forums/en-US/home?forum=adodotnetdataproviders
It is appropriate and more experts will assist you.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Possibility to configure Freedome VPN connection on unsupported devices

I have this idea, which I think would be useful in this world of many different OSes:
I suggest that you would make it possible to, for example, configure the VPN connection on Windows Phone. Windows Phone has the possibility to configure VPN profiles at the settings, and so do many other OSes that are not supported by Freedome. This would also solve the problem of having no VPN on Linux. Of cource it wouldn't be as easy as pressing a big button, but many privacy-aware users would benefit from it.

Hi Jay,
So, when you say you need to connect your website to your Local Network, is your website a Paas instance or a IaaS instance, i.e., website hosted in a VM using IIS?
Do you have a single instance of the website or multiple instances that have been added to a VNET and need to be connected to the On-Premise Network?
What VPN device are you using to connect Azure to On-Prem?
If you have one website instance that needs to connect to an On-prem network Point-to-Site (P2S) connection would make sense. However, if you have multiple instances of your website in a VNET you would need a Site-to-Site (S2S) connection.
Please be advised that only devices that support Dynamic Routing Gateway would work when configuring P2S connections.
Regards,
Malar.

Would it be possible to configure wi-fi airtime per day/week for my children. They have an iPhone/ipad device and trend to watch the screen every free moment of their time.....

Good morning.
Would it be possible to configure wi-fi airtime per day/week for my children. They have an iPhone/ipad device and trend to watch the screen every free moment of their time.....

Hello rogier111
Maybe this helps:
Open AirPort Utility, select your AirPort Base Station and click Manual Setup.
Select Access Control Tab.
Pick Timed Access from the list.
Now click on the "+" button, enter the MAC adress of the device you want and decide for the network time limits.
Update your Airport.
You can find the MAC adress of an iOS device by going to Settings/General/About.

Is it possible to adjust the extend connect timeout?

When we have a cluster member down and the extend client tries to connect to it, there appears to be a minimum timeout of ~1 second. Is there any way of reducing this so that it is negligible?
I have tried:
<remote-cache-scheme>
     <scheme-name>remote-scheme</scheme-name>
     <service-name>ExtendTcpCacheService</service-name>
     <initiator-config>
          <tcp-initiator>
               <remote-addresses>
                    <socket-address><address>localhost</address><port>10000</port></socket-address>
               </remote-addresses>
               <connect-timeout>1MS</connect-timeout>
          </tcp-initiator>
          <outgoing-message-handler>
               <request-timeout>5s</request-timeout>
          </outgoing-message-handler>
     </initiator-config>
</remote-cache-scheme>However, it still takes ~1 second to realise there is no socket there. Is this a machine level setting perhaps?
(This is in a .Net extend client running under IIS)

Hi all - I found KRD Harris discussion regarding this question - no need to answer.
Thanks.

Oracle 9.0.1 on Solaris/SPARC infinite connection timeouts

Hello, All!
I have the following system configuration:
Solaris 5.9 Maintenance Update 4;
Sun Ultra 10, 1 UltraSPARC IIi 440Mhz CPU, 1024M RAM;
Oracle 9.0.1 (9i Release 1).
The database was created with JServer option turned on (we're using the integrated CORBA functionality); archive log mode is OFF, database cache advice is ON.
In a nutshell,
==============
the problem is in really infinite connection timeouts of Oracle after a long time of inactivity (say, on Monday after two weekend days).
Long description.
=================
Client-side symptoms.
First, I tried to establish a connection to a published CORBA object, and received no response (I am already waiting for 1 hour 40 minutes).
Then, I tried to connect to the database with SQLPlus, remotely:
$ sqlplus /nolog
SQL> CONNECT SYS/change_on_install@ORCL AS SYSDBA;
All the same, I receive no reply. However, the listener is alive, I can establish a network connection to both ports 1521 and 2481. Client-side logs (specified via sqlnet.ora) say the following:
=========== skipped ===========
[09-АВГ-2004 10:27:24:770] nioqsn: entry
[09-АВГ-2004 10:27:24:770] nioqsn: exit
[09-АВГ-2004 10:27:24:770] nioqrc: entry
[09-АВГ-2004 10:27:24:771] nsdo: cid=0, opcode=84, bl=0, what=1, uflgs=0x20, c
[09-АВГ-2004 10:27:24:771] nsdo: rank=64, nsctxrnk=0
[09-АВГ-2004 10:27:24:771] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[09-АВГ-2004 10:27:24:771] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[09-АВГ-2004 10:27:24:771] nsdofls: DATA flags: 0x0
[09-АВГ-2004 10:27:24:771] nsdofls: sending NSPTDA packet
[09-АВГ-2004 10:27:24:771] nspsend: plen=770, type=6
[09-АВГ-2004 10:27:24:771] nttwr: entry
[09-АВГ-2004 10:27:24:771] nttwr: socket 12 had bytes written=770
[09-АВГ-2004 10:27:24:771] nttwr: exit
[09-АВГ-2004 10:27:24:771] nspsend: 770 bytes to transport
[09-АВГ-2004 10:27:24:772] nsdo: nsctxrnk=0
[09-АВГ-2004 10:27:24:772] nsdo: cid=0, opcode=85, bl=0, what=0, uflgs=0x0, cf
[09-АВГ-2004 10:27:24:772] nsdo: rank=64, nsctxrnk=0
[09-АВГ-2004 10:27:24:772] nsdo: nsctx: state=8, flg=0x400d, mvd=0
[09-АВГ-2004 10:27:24:772] nsdo: gtn=127, gtc=127, ptn=10, ptc=2011
[09-АВГ-2004 10:27:24:772] nsdo: switching to application buffer
[09-АВГ-2004 10:27:24:772] nsrdr: recving a packet
[09-АВГ-2004 10:27:24:772] nsprecv: reading from transport...
[09-АВГ-2004 10:27:24:772] nttrd: entry
If I try to connect to the database locally, I receive the same result:
$ sqlplus /nolog
SQL> CONNECT / AS SYSDBA;
-- no reply.
Server-side symptoms.
Oracle logs in ${ORACLE_BASE}/admin/ORCL have no entries referring the last two days. Oracle server debug log (specified via sqlnet.ora) says the following:
========== skipped ===================
nttrd: socket 20 had bytes read=181
nttrd: exit
nsprecv: 181 bytes from transport
nsprecv: tlen=181, plen=181, type=6
nsrdr: got NSPTDA packet
nsrdr: NSPTDA flags: 0x0
nsdo: what=1, bl=2009
nsdo: nsctxrnk=0
nioqrc: exit
nioqsn: entry
nioqrc: entry
nsdo: cid=0, opcode=84, bl=0, what=1, uflgs=0x20, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=8, flg=0x420c, mvd=0
nsdo: gtn=156, gtc=156, ptn=10, ptc=2019
nsdofls: DATA flags: 0x0
nsdofls: sending NSPTDA packet
nspsend: plen=93, type=6
nttwr: entry
nttwr: socket 20 had bytes written=93
nttwr: exit
nspsend: 93 bytes to transport
nsdo: nsctxrnk=0
nsdo: cid=0, opcode=85, bl=0, what=0, uflgs=0x0, cflgs=0x3
nsdo: rank=64, nsctxrnk=0
nsdo: nsctx: state=8, flg=0x420c, mvd=0
nsdo: gtn=156, gtc=156, ptn=10, ptc=2019
nsdo: switching to application buffer
nsrdr: recving a packet
nsprecv: reading from transport...
nttrd: entry
nttrd: socket 20 had bytes read=770
nttrd: exit
nsprecv: 770 bytes from transport
nsprecv: tlen=770, plen=770, type=6
nsrdr: got NSPTDA packet
nsrdr: NSPTDA flags: 0x0
nsdo: what=1, bl=2009
nsdo: nsctxrnk=0
nioqrc: exit
Oracle local client debug log (oracle enterprise manager runs on the same machine) says:
...nsevwait: nsevwait: nsevwait: nsevwait: nsevwait:
nsevwait: nsevwait: nsevwait: nsevwait: nsevwait:
nsevwait: nsevwait: nsevwait: nsevwait: nsevwait: ...
ps -e -o "user,pid,pcpu,pmem,rss,vsz,args" says there're several (3) processes running as oracle, with "args" oracle_ORCL, which eat up nearly all available memory (they have "pmem" values of 25, 25 and 17 per cent, respectively). One of these processes has "pcpu" value varying from 97% to 100%, moreover, this is a user, NOT system time (according to sdtperfmeter, disk/page/swap activity is extremely low; system load holds at value of 4). Here is a sample vmstat output:
cpu
cs us sy id
287 99 1 0
285 100 0 0
280 100 0 0
272 100 0 0
298 98 2 0
275 99 1 0
267 100 0 0
307 97 3 0
282 100 0 0
270 100 0 0
307 98 2 0
287 100 0 0
Here cs is the number of cpu context switches per second;
us is cpu user time;
sy is cpu system time.
The question is: what oracle may be doing and how can I fix the problem?
Thanks in advance.

Now, 3 hours later, the first two (of three) connections got established, but subsequent database queries are in the same nearly dead state.
CPU usage remains about 100%, system load 4.
I know that oracle restart (and/or system restart) will cure the problem -- but only until next weekend.
Can this be oracle misconfiguration?

Database connectivity timeout problem

I am using struts framework for my web application and in between just for a test I have used spring framework database connectivity too in few files. I have deployed my application on tomcat 5.5 server on linux machine. Application is running fine, but sometimes this application shutdown by itself and I have to restart tomcat again (like 3-4 times a month). I wan to run this application continuously. I am getting this error in my log files
1 Error: DAO.SpringInformDAO[ERROR](SpringInformDAO.java:loadTypelessNameIDListProduct:246)org.springframework.dao.DataAccessResourceFailureException: StatementCallback;
2.Caused by: com.mysql.jdbc.CommunicationsException: The last packet successfully received from the server was40524 seconds ago.The last packet sent successfully to the server was 40524 seconds ago, which is longer than the server configured value of 'wait_timeout'. You should consider either expiring and/or testing connection validity before use in your application, increasing the server configured values for client timeouts, or using the Connector/J connection property 'autoReconnect=true' to avoid this problem.
3. Caused by: java.net.SocketException: Broken pipe
Does someone has any idea how to solve this problem?? It would be great help
Thanks

mantoo wrote:
Thanks for reply. Ok let me explain again, may I was using wrong words. Actually, my web application stops automatically after few hours, I don't know know what is the reason, whether it is tomcat or sql sever. What I concluded from various Google search that it might be because of sql server waiting time and connection ideal time difference does not match. By default SQL server's wait_time is 8 hours, so after that this errors occurs. For dealing this I put following attributes in my resource tag in context.xml.
(testWhileIdle="true" timeBetweenEvictionRunsMillis="10000" minEvictableIdleTimeMillis = "60000" )
After doing this I am not getting those errors which I have written in my previous post, but now it is showing this :
ERROR: transport error 202: handshake failed - received >GET http://www< - excepted >JDWP-Handshake< ["transport.c",L41]
JDWP exit error JVMTI_ERROR_NONE(0): could not connect, timeout or fatal errorListening for transport dt_socket at address: 8000So the real problem is that tomcat is exiting. It isn't crashing, just exiting.
Database problems would not cause that. Excluding the possibility that the driver is calling System.exit() - in which case you would be using a non-standard driver.
Other reasons for application exit.
1. Your code, or some library that you use is calling System.exit().
2. Your JNI code or some library that uses JNI code has a library in C/C++ that is calling the OS application exit in that code.
3. Tomcat probably has some API that allows you to stop it - some place the java code is calling it
4. Some other process outside of tomcat is terminating the application.
Greping can potentially eliminate some of the possibilities above.
As for 4 you can analyze the shutdown time to determine if it shuts down at the same time or after the same amount of time.

Possible to configure per connection timeout values?

Similar Messages

Maybe you are looking for