Uniform HTTP Timeout setting?
Hi all
I used HttpConnection for a few years and now I have a need to set the timeout for HTTP connections within 2 minutes. I searched in this forum and elsewhere and learned that I should use either ConnectionFactory, who has the ability to set a timeout, or can I use HttpConnection and the timer and interrupt the flow of HTTP.
BUT - as far as I know, these two methods have varying results. HttpConnection/Timer methods and the ConnectionFactory seem to work differently in the OS 5, 6 and 7 appear to better work in simulators than devices physical (I tested on OS5 and OS7.1 BlackBerry).
My best results occur when I use ConnectionFactory and has my timeout value, setTimeLimit(), and setConnectionTimeout(), and then I add a Timer to the same timeout value. The code checks the sufficient connectivity using getCoverageStatus() just before trying to open the HTTP connection. It seems to work well on OS5, 6 and 7 sims and on live devices for OS5 and OS7.1.
I'm still having a problem. There are moments where nothing stops the connection before HTTP mark two minutes. This happens when I simulate bad reception, just as the connection starts. I simulate the threshold of reception by starting the connection and then placing the BlackBerry in one box to cut the front desk. Most of the time, the works of timeout. My timeout is set to 16 seconds. On a live device 5.0, the timeout takes more than 30 seconds (not what I want, but it says my code is to have an effect).
But if I open the box for 30 seconds and check every 15 seconds with a quick glance, I had the timeout of 2 minutes and 40 seconds - much longer than the time limit of 2 minutes by default. I connect where it happens and the 02:40 delay occurs inside this section of code:
ConnectionFactory myConFactory = new ConnectionFactory();
myConFactory.setTimeLimit (myFactoryTimeout);
myConFactory.setConnectionTimeout (myFactoryTimeout);
ConnectionDescriptor myConDesc = myConFactory.getConnection (pURL);
Ignorant if I emphasize connectivity incorrectly performing this test at all, my questions for the experts of the forum are:
I'm doing something wrong, and is there anything else I can do to get a specific time frame in all cases?
Is there an explanation for this failure of timeout?
The code follows. I've slightly simplified. Thank you!
Request code:
public static String HttpGetResponseString (String pURL, int pConnectionTimeoutSeconds)
throws IOException {UnanticipatedHttpResponseException}
String myReturn = "";
HttpConnection myConn = null;
InputStream myInput = null;
Timer connectionTimerConnect = null;
long myConnectionTimeoutSeconds = pConnectionTimeoutSeconds * 1000;
long myFactoryTimeout = myConnectionTimeoutSeconds;
try {}
If the internet is not available.
If (! getIsCoverageSufficient())
throw new UnanticipatedHttpResponseException ("no cover available");
HttpTimerTask timerTaskConnect = new HttpTimerTask (null);
connectionTimerConnect = new Timer();
connectionTimerConnect.schedule (timerTaskConnect, myConnectionTimeoutSeconds); Kill demand after x seconds
If (Constants.DEBUG_MODE)
Prefs.getInstance () .writeErrorLog ("Start Timer:" + myConnectionTimeoutSeconds + "ms");
Connection request
ConnectionFactory myConFactory = new ConnectionFactory();
myConFactory.setTimeLimit (myFactoryTimeout);
myConFactory.setConnectionTimeout (myFactoryTimeout);
ConnectionDescriptor myConDesc = myConFactory.getConnection (pURL);
If (myConDesc is nothing)
throw new Exception ("factory connections do not return a descriptor");
If (timerTaskConnect.hasInterrupted ())
throw new UnanticipatedHttpResponseException("Interrupted-Open");
myConn = (HttpConnection) myConDesc.getConnection ();
final int responseCode = myConn.getResponseCode ();
If (timerTaskConnect.hasInterrupted ())
throw new UnanticipatedHttpResponseException ("Interrupted-response code');
If (responseCode! = HttpConnection.HTTP_OK) {}
throw new UnanticipatedHttpResponseException ("Invalid ResponseCode:" + Integer.toString (responseCode));
} else {}
myInput = myConn.openInputStream ();
ResponseData = new ubyte [] byte [10000];
int length = 0;
StringBuffer rawResponse = new StringBuffer();
{While (-1! = (length = {myInput.read (responseData)))}
rawResponse.append (new String (responseData, 0, length));
If (timerTaskConnect.hasInterrupted ())
throw new UnanticipatedHttpResponseException("Interrupted-Read");
}
myReturn = rawResponse.toString ();
}
} catch (Exception e) {}
Prefs.getInstance () .writeErrorLog ("Exception:" + e.getMessage ());
throw new UnanticipatedHttpResponseException (e.getMessage ());
} {Finally
If (connectionTimerConnect! = null)
{
connectionTimerConnect.cancel ();
connectionTimerConnect = null;
}
try {}
If (myInput! = null) {}
myInput.close ();
myInput = null;
}
} catch (Exception e) {}
try {}
If (myConn! = null) {}
myConn.close ();
myConn = null;
}
} catch (Exception e) {}
Closed connection Exception
}
}
Return myReturn;
}
The Timertask:
SerializableAttribute public class HttpTimerTask extends TimerTask {}
HttpConnection _myConn = null;
Thread _myThread = null;
Boolean _myHasInterrupted = false;
public HttpTimerTask (HttpConnection myConn)
{
_myConn = myConn;
_myThread = Thread.currentThread ();
}
public boolean hasInterrupted()
{
Return _myHasInterrupted;
}
public void run() {}
String myErrorName = "HttpTimerTask:"; "
try {}
If (_myConn! = null)
{
_myConn.close ();
_myConn = null;
If (Constants.DEBUG_MODE)
Prefs.getInstance () .writeErrorLog (myErrorName + "Closed connection");
}
If (_myThread! = null)
{
_myThread.interrupt ();
_myHasInterrupted = true;
If (Constants.DEBUG_MODE)
Prefs.getInstance () .writeErrorLog (myErrorName + "Interrupts the thread");
}
} catch (IOException e) {}
}
}
Ok.
«... Add a second timer.
It is probably more effective if you can get your first Timer to perform the two functions, i.e. giving him the connection when you have an and the code check to see if there is a connection of paving? I'm always hesitant to start further discussions on a camera like the BB.
Please let us know how you go, because your logic could provide a good model for others.
Tags: BlackBerry Developers
Similar Questions
-
Hi all
I'm trying to set the timeout on my http connection; This code works fine on the Simulator, but survey java.io.IOException: invalid url parameter.
on the real device (storm). Any ideas would be greatly appreciated! and yes I look the http missions... Here is my code-
StreamConnection streamConn;
If {(_longTimeouts)
streamConn = (StreamConnection) Connector.open
(urlstring + ";" ConnectionTimeout = 60000; deviceside = false');
} else {}
streamConn = (StreamConnection) Connector.open
(urlstring + ";" ConnectionTimeout = 10000; deviceside = false');
}
HttpConnection hc = (HttpConnection) streamConn;Thank you
UDI
Hi Doug,.
On the money! rather than delete, I had to change the deviceside = true, works like magic
Thank you!
UDI
-
field SESSIONTIMEOUT of PSWEBPROFILE table has something to do with the websever time-out setting? If Yes, then in my case, change the values in the table doesn't have no effect or the time-out expires, or PIA setting!
Wait times can be defined in many places.
Web profile
On the whitelists
Application server
to name a few...http://docs.Oracle.com/CD/E38689_01/pt853pbr0/Eng/PT/tsvt/task_WebServerTimeouts-071144.html#WebServerTimeouts-071144__pt0020183
http://docs.Oracle.com/CD/E38689_01/pt853pbr0/Eng/PT/tsvt/task_PIATimeouts-07114a.html#portletsFrame
http://docs.Oracle.com/CD/E38689_01/pt853pbr0/Eng/PT/tsvt/task_ApplicationServerTimeouts-071147.html#portletsFrameThere are several types of wait times and you should read the documentation to understand how they interact together. I recommend leaving weblogic, only, unless specifically requested to change by the documentation. PeopleSoft will tell weblogic what to do.
Changing the value of update SQL is also not recommended. Change the web profile you use online, especially if you are not familiar with the options. If you're updating just SESSIONTIMEOUT you never change the pop-up warning that has a separate clock. Which can have a negative impact on users.
Delays of the web of PeopleSoft are JavaScript engine. If they are changed the web profile needs to be recharged. Restart the PIA after change of any web profile. Clear the cache of the browser and PIA as well. The JavaScript file defined in the code of timeout will be cached and sometimes after PIA restart the browser can be stubborn and always used the updated copy cached.
The JavaScript timeout is in the HTML PT_SAVEWARNINGSCRIPT object if you want to watch.
-
OK, maybe not weird, but weird. It's WL7sp7.
In the std newspapers in our production environment, we see the following message "the server could not send the HTTP message during the timeout value configured. The socket has been closed. ». You can see this message only to a second interval specific than a minute... that is, in the log below, extract as the second "33" (11: 52:33, 11:55:33, 12:11:33, etc..). After a reboot, we will see only this message to the second "21" (15: 13:21, 3:21:21 PM PST, etc.).
The problem, it is a DOTNET fact http post for this app WL application... If the messages at the wrong time DOTNET application (e.. g, to the second '33' minute) the http post fails. The DOTNET application logs the remote server took of disconnection. If you look at the logs to stdout for the same time, we see the connection timeout message. The post and the response would only last a second or two and little almost always succeeds wait for these applications, which falls on the 'bad' (milli?) second of the minute.
I don't know if I've explained clearly this strange phenomenon. If this is not the case, let me know. An excerpt from our newspapers std:
grep /tmp/WLPRODSVR04-stdout.log "the server could not send the HTTP message"
# < 5 November 2008 11:52:33 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '2' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 11:55:33 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '20' to the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 12:11:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 12:34:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '4' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 12:42:33 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '2' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 12:53:34 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 12:57:34 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
....
[reboot]
.....
# < 5 November 2008 3:13:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 3:21:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 3:29:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 3:30:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 3:38:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 5 November 2008 16:30:21 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 16:41:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '27' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 17:56:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 18:01:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 18:08:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 18:55:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 19:11:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 19:50:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 8:00:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 8:07:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 8:20:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 9:15:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '25' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 9:34:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 9:41:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 10:14:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 10:17:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 10:24:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 10:38:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 11:04:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '25' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 11:09:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 11:28:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 11:49:21 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 12:20:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 12:47:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '20' to the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 12:56:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 1:10:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 1:18:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 3:29:21 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 6 November 2008 16:19:21 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 5:23:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 17:59:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 18:31:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 6:51:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 19:24:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 19:31:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '26' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 19:41:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 8:00:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '30' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 8:21:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 8:47:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 9:15:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 9:20:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '23' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 9:34:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '22' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 10:06:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 10:12:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '21' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 10:54:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "28" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 11:05:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 11:12:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 11:28:17 AM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '27' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
....
[reboot]
.....
# < 7 November 2008 12:24:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: that of the "31" to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 12:31:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "14" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 12:31:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: "14" for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 12:35:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '16' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 1:14:09 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '17' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 1:15:09 pm PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '10' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 1:32:10 PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '19' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 2:03:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '15' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 2:12:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '11' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 2:12:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '11' for queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 2:24:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '24' to queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >
# < 7 November 2008 3:39:10 PM PST > < Info > < HTTP > < credpwy01swlc04 > < WLPRODSVR04 > < ExecuteThread: '29' for the queue: 'default' > < identity kernel > <>< 101325 > < server could not send the HTTP message during the timeout value configured. The socket has been closed. >Its a known problem with WLS 7.0 SP7 (CR300032 and CR196369) associated with CompleteHTTPMessageTimeout. WebLogic Server closes a connection intermittently while responding to the slow clients. If you have a support contract, you can open a service request and download the patch and details of the Czech Republic.
-
Sync connection timeout setting
Our directors have recently set up a new app server on our test environment for the system and switched the mobile instance to the new platform.
Since then, we have a problem where the synchronization sessions that are "slow" because of not channeled to the client for more than 300 seconds of data fails with "discioonnected network during synchronization" even if the query of database by selecting the data continues.
System test environment is a very slow database box and there are a few problems with submission with watercourse causing poor performance, but before setting up the new application server, the synchronization sessions have no timeout. The two settings Mobile Server and client are the same, as far as I can see, so I don't think it's a mobile related setting causing the disconnection, but I don't know where else to look at (and the DBA is not a lot of help)
Anyone have any ideas?Hi Gary,.
You use SV or stand alone? If the OAS, then your Apache server could be timing your exit. Here are a couple of settings that you can watch:
httpd.conf:
#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 3000On the webtogo.ora servers
[CONSOLIDATOR]
SOCKET_TIMEOUT = 900 - if you see a lot of FC_TIMEOUT mistakes in your debug.txt, this helps keep the network socket open for the optimal transport of data.Under the polite.ini synchronization
TIMEOUT_MAX = 900
RESUME_CLIENT_TIMEOUT = 900Also, how many times you run stats on MOBILEADMIN? Do you use histograms? If you are, don't.
You're all partition mapping and community cards? This could help with performance as well.
My rule of thumb is that your queries will ever-more than 60 seconds then start to carry data. It, then you run more then in addition to problems of overall performance, which is not good for any application on the server. The same goes for MGP as well as SYNC.
-
How to replace the timeout set on the message in Weblogic 10.3.3
Life is set on the message by the message producer. The message is sent to a Destination imported FAS in a field and then transmitted to the destination stone on another remote server in Weblogic.
The value of life is defined as 7 days on the message of the message producer. I would like to replace with a much shorter duration. The following steps have been completed,
1A allowed SAF SAF destination queue default Time-to-Live
2 FAS by default, Time-to-Live is set to 10 seconds on the destination queue parameters
3. set the default Time-to-Live to 10 seconds for the factory of connections in queue on the remote server (where the destination queue)
But the message expiration date remains that 7 days, the original value. I missed something? How can this be accomplished?
Thank you
HongHmm, it should work then. Do you have any substitution of time-to-live on the remote destination?
-
HTTP Timeout - Explorer vs Firefox
I discovered that if you make a request, using URLLoader or other type of request objects, if the connection fails to connect browsers react differently. The issue I encountered is with Firefox, it does not appear any time. If she fails to connect you will never get an onFault, or response onComplete.
Has anyone else seen elsewhere? Is my best option to create my own Timer with a time-out?
To reproduce: you can use the code example provided on:
http://livedocs.Adobe.com/Flex/2/langref/Flash/NET/URLRequest.html#includeExamplesSummary
Change URLRequest ("XMLFile.xml") to URLRequest ("' http://www.google.com" "), disable your network connection, run your Flex application with Firefox and explore and see the difference.
Thank youIn my view, using a timer is the best solution. Please this file as a bug in our new public bugbase for Flex at http://bugs.adobe.com/flex and mention that it's really a problem of browser/player. The team of the player is not currently a public bugbase.
-
Hello
I have a use case in which I'll call synchronous external Web Service and the form of this service, I get the answer after 80 seconds.
I know that this console form EM soa-infra-> SOA Administration-> BPEL proprieties-> under 'more BPEL Configuration Properties..' in SyncMaxWaitTime can I change the default 45 second in 80 seconds, but it will apply to all synchronous services in this area, and I want only the value appeal of Web Service of particular external reference (link partner).
For the limit of timeout for the particular web service (partner of external reference link):
I saw a post at < http://www.mandsconsulting.com/asynchronous-vs-synchronous-bpel-processes > in which there is an option in 'Link partner Edit' form property tab dialog box, we can add "timeout" property but in SOA Suite11.1.1.7 I am not able to find this property form the list.
on this post < http://abhishek-soablog.blogspot.in/2010/06/timeout-for-partnerlink.html > is also described the same way, but it's just the source code of the highest way of GUI to set the timeout property and it does not work with a new version.
Can someone please tell me in a new version (11.1.1.7) of SOA suite, which is how to set the timeout for the particular web service (partner of external reference link).
Thank you
Can someone please tell me in a new version (11.1.1.7) of SOA suite, which is how to set the timeout for the particular web service (partner of external reference link).
VR;
Click em-> composite-> Services and references-> select need to reference and click on-> properties: 'HTTP Timeout of read' and 'HTTP timeout.
developing composites:
Click on a reference-> property inspector-> link properties-> plu green and add oracle.webservices.httpConnTimeout with the necessary value and oracle.webservices.httpReadTimeout with the necessary value
for the same domain defined: oracle.webservices.local.optimization = false
You can watch
Administration of Web Services - 11g Release 1 (11.1.1.7)
How to set a timeout for a Web Service in SOA 11 g (Doc ID 979683.1)
SOA 11 g: political malpractice not to intercept 'service Endpoint unreachable' error (Doc ID 1503989.1)
-
Transport http - problem with timeout
Hello
I have a Bussines services that uses the Http transport and its configured with the ending "http://90.56.154.45:989 / offline1".
It's the rest of the config:
/************/
General configuration
Type of service no matter what XML Service
Transport configuration
Http protocol
Load balancing algorithm no
Endpoint URI
http://90.56.154.45:989 / offline1
Retry Count 0
Retry interval iteration 0
Start Application Yes errors
Configuration of HTTP Transport
Timeout 5
Query HTTP POST method
Authentication no
Proxy server
Follow redirects HTTP DISABLED
Use segmented Mode streaming
Content of message, Configuration management
MTOM/XOP support disabled
Page attachments to disk no.
/*************/
When I try to sbconsole, the connection lasts about 3 minutes. Why not meet the deadline set to 5 seconds?
Thank you very much, greetings.But the setting of timeout (timeout = 5 sg) still not come into force. It may be a possible bug?
Only the timeout setting is actually to READ timeout. So if the target server takes longer than the number of seconds that you have configured in the timeout parameter, then only this setting will take effect. Like currently, you are not able to even connect (connect timeout came into picture), that's why READ timeout isn't triggering because READ has not even started.
It works as expected and there is no problem with the setting.
Kind regards
Anuj -
How to set the timeout of read when using channelReader.ReadWaveform?
I'm using a USB-6210/a. data acquisition, and it works fine until I have to take a longer than 10 s waveform.
When I take a longer than wave form, I get the error 200284, "some or all of the requested samples are not yet acquired. To wait for the samples become available use longer read timeout... »
No problem, I thought, I'll just put a longer period. I searched through the documentation, and the timeout only I found was the watchdog timeout. When I wanted a longer value, I get code 200452 State - specific property is not supported by the device or is not applicable to the task.
I use the code in the example AcqVoltageSamples_IntClk.2008 .net with c# in Visual Studio 2008, .net 3.5 sp1.
How to set the timeout so that ReadWaveform() is not the time?
Here is the code:
privateAnalogMultiChannelReaderchannelReader;
privateAnalogWaveform
awf; publicList
GetWaveForm() {
Try
{
Task getWaveform = newTask();
getWaveform.AIChannels.CreateVoltageChannel (Channel,"", TerminalConfiguration, RangeMinimum,
RangeMaximum, AIVoltageUnits.Volts);
getWaveform.Timing.ConfigureSampleClock ("", SampleRate, SampleClockActiveEdge.Rising,)
SampleQuantityMode.FiniteSamples, NumSamples);
getWaveform.Control (TaskAction.Verify);
channelReader = new AnalogMultiChannelReader (getWaveform.Stream);
AnalogWaveform
data = channelReader.ReadWaveform (NumSamples); AWF = data [0];
samples As new List
(); for (inti = 0; i)
returnsamples;
}
catch (DaqExceptionexception)
{
MessageBox.Show (exception. (Message);
}
List of
l = newList (); return l;
}
Thank you
Curt
Hi Curt,.
Here is a Knowledge Base that can help you to set the timeout setting in your code:
-
imgSessionSerialReadBytes causes timeout (re-post in appropriate thread)
Hello
I'm trying to control a device called "Cedip Titanium", it is an older version of the http://www.flir.com/thermography/eurasia/en/content/?id=11354. The following code generates a timeout error:
IMAQSession* session = 0; int result = InitializeAquisition((void**)&session); char* buffer = new char[8192]; buffer[0] = 0x02; // start byte buffer[1] = 0x04; // command name size buffer[2] = 0x00; // command name size (2x bytes) buffer[3] = 0x43; // command name (C) buffer[4] = 0x43; // command name (C) buffer[5] = 0x4D; // command name (M) buffer[6] = 0x2C; // command name (,) (CCM, = check communication) buffer[7] = 0xFF; // control bit buffer[8] = 0x03; // end byte uInt32 bufferSize = 9; result = imgSessionSerialFlush(session->Sid); result = imgSessionSerialWrite(session->Sid,buffer,&bufferSize,2500); bufferSize = 11; result = imgSessionSerialReadBytes(session->Sid,buffer,&bufferSize,2500);The last line (imgSessionSerialReadBytes) freezes during the time specified in the timeout (a really high timeout setting does not help) and then he returned the error code:-1074397037 (IMG_ERR_SERIAL_READ_TIMEOUT). Passage to imgSessionSerialRead results in the same error as imgSessionSerialReadBytes.
Manufacturing did not any file from camera to load in the measurement and automation, so I had to create my own following standards from the manufacturing:
"The speed of transmission of communication camera can be defined by orders. Cirrus tries to establish communication to the highest possible baud rate. There are 57000 or 115000 according to the length of the cable.
The camera is initiated to the power upward with 9600bds, 8 bits, 1 bit of high, no HW or SW control bit. »
I also tried to change some of the settings (ect buad rate) with no luck. Try to send a command using the test-thing under the series settings in the tool OR Camera File generator always returns a table (8192 bytes) containing \x00\x00\x00... (so basically, an empty array is returned). I read a few other posts on this forum, most of them indicate you should add an endpoint-char. The Protocol specifies a stop bit 0 x 03 who should be added at the end of each packet. I tried to add, but it didn't matter, and what I've read, imgSessionSerialReadBytes ignores the chariot of retirement anyway.
I use the 1427 grabber (PCI-express) card which runs under 64-bit Win2k8.
I tried to solve it by myself for a few days, but I'm out of ideas. Any help would be greatly appreciated!
Best regards, Olof
Problem solved. The baud rate should have been instead of 9600-115200.
-
Automatic logout after inactivity of 180 seconds (http and https)
All of my N4032 and N3024 switches with 6.2.7.2 firmware automaticlly break http and https session after ~ 180 seconds of inactivity. Controls:
line telnet
exec-timeout xdo not work
Does anyone have a similar experience?
Is this a known issue?Looking through the firmware release notes, it looks like it was a known, only http/https problem did not follow the exec-timeout parameter. # Ip http timeout-political order, has been added to 6.2.6.6. I would test change the time-out setting by using the command # ip http timeout policy.
Example of release notes:
Console (config) #ip http idle timeout-political 3600 life 86400
Let us know if it works.
-
Configure the keyboard backlight Timeout
Hello, I want to configure the keyboard backlight Timeout on Dell Latitude E6440. I use pre-installed Linux OS Ubuntu 12.04.2 Dell.
I found this post http://en.community.dell.com/techcenter/enterprise-client/f/4448/p/19415396/19975858.aspx#19975858 of Warren Byle.
He wrote how to change the keyboard backlight with tool CCTK lighting level. I downloaded CCTK for Red Hat Linux and looks like it works fine on Ubuntu too. With that - token orders that I am able to change the level of backlight on the keyboard which is good.
But I still don't know how to change the keyboard backlight Timeout. Backlight is still off after 10 seconds. Is there some special - token for this timeout setting?
According to other messages, looks like configring timeout to 5 minutes could be possible, as there are Windows applications that could do that (for example Dell System Manager Application checkpoint)
http://en.community.Dell.com/support-forums/laptop/f/3518/t/19524424.aspx
http://www.shadowsplace.NET/376/hardware/Dell-laptop-keyboard-backlighting-timeout/
http://Forum.NotebookReview.com/Dell-Latitude-Vostro-precision/739154-e6440-owners-thread-5.html#post9698302Hello
Dell has now released tool called smbios-keyboard-ctl [1] for configurting keyboard backlighting (timeout and trigger). It is in repository libsmbios [2]. I tried and it works very well.
If this problem is now resolved. Thank you!
[1] - http://linux.dell.com/cgi-bin/cgit.cgi/libsmbios.git/tree/src/bin/smbios-keyboard-ctl
[2] - http://linux.dell.com/cgi-bin/cgit.cgi/libsmbios.git/
-
I was told it is advisable to ISE to configure the session timeout something > s 7200 (2 hours).
What happens if we do not enable session timeout at all? (WLAN/advanced, "Enable Session Timeout")
What would be the implication/security operation, if any?
It means customer would authenticate only once, and can stay on, without having to go through the authentication of 802. 1 x all day?
Is there a default session timeout value?
Here's a post on the time-out settings
https://rscciew.WordPress.com/2014/05/07/timeout-setting-on-wireless-LAN-Controller/
As far as I understand it, more big session timeout values can train your oblique stats Cordless drill. Otherwise there is no adverse impact to increase it.
HTH
Rasika
Pls note all useful responses *.
-
Configure the timeout and session timeout in a group policy.
I want a L2L tunnel to establish a period of time, this tunnel is established in a PIX 515E.
Then I had seen that we must configure the idle time in group policy, but I have no ' t know the difference between the idle timeout setting and the session timeout.
Anyone know what is the difference between this two command line.
Thank you
Hello
Session-Timeout: at the end of this time, the security apparatus terminates the connection.
Idle-timeout: If there is no communication on the connection activity in this period, the security apparatus terminates the connection.
Please see the below URL for more details.
http://www.Cisco.com/en/us/docs/security/ASA/asa70/command/reference/TZ.html#wp1281883
http://www.Cisco.com/en/us/docs/security/ASA/asa70/configuration/guide/vpngrp.html
Kind regards
Arul
* Rate pls if it helps *.
Maybe you are looking for
-
My ATT SIM card transfer active
Can I transfer my assets to THE & T SIM from my iPhone to my iPhone 5 SE?
-
Since I've updated, Mozilla guard is no longer me connected to my favorite sites.
-
Mosaic Georaster does not return the same values as sources
I have created a mosaic using the plsql block... and when you query the source and the mosaic I get different results...Any suggestions...Best regardsTagle Hugo-PLSQLDECLAREGR sdo_georaster;BEGININSERT INTO NED_MOSAIC (id, rast)VALUES (1, sdo_geor.in
-
Hello I would like to make a matching color between 2 photos with lightroom?
-
HelloI wrote a few lines of javascript in acrobat performing an action with a button click, the code works well but when I run the same PDF on another PC, it nothing happens when I click on the button.Why do I have this problem?Thanks in advance, and