WRT54G v 7.0 -- Setting "Keep Alive: Redial Period" not correct (radio button)

Hi,
I own a Linksys-Router WRT54G v7.0 with firmware v7.00.8 build 008, Jul. 9, 2009.
On the web GUI (Setup/Basic Setup) there's a setting "Keep Alive: Redial Period XX Sec.". As I'd like to stay connected with my provider permanently, I've set the radio button to "Keep Alive: Redial Period" and the according text field to "30" seconds. Then, I've clicked "Save Settings" and got a confirmation message that the settings got saved.
Anyway, even after saving the settings the according radio button is still set to "Connect on Demand...". But that is only true for newer browsers, like e.g. IE8, IE7 or Firefox 8. If you use an older browser, like e.g. IE6, then the radio button is correctly set to "Keep Alive: Redial Period" with a value of "30" seconds.
Conclusion: The settings get correctly saved by the router (I can confirm that), but they don't get correctly shown in the web GUI. Looks like a HTML/Javascript bug in the router's admin web GUI. That's really annoying as you never exactly know the effective settings...
Can someone confirm that bug? Is there a newer firmware than version 7.00.8?
Regards,
Patrick

Try to clear the browser's cache as well.
"Don't fix it if it ain't broken."

Similar Messages

Accounts Setting page at Facebook is not correctly displayed

Facebook accounts settings not correctly displayed. My OS is Windows XP & Internet security is Kaspersky

Can you attach a screenshot?
*http://en.wikipedia.org/wiki/Screenshot
Use a compressed image type like PNG or JPG to save the screenshot and make sure that you do not exceed the maximum file size (1 MB).
Reload web page(s) and bypass the cache.
* Press and hold Shift and left-click the Reload button.
* Press "Ctrl + F5" or press "Ctrl + Shift + R" (Windows,Linux)
* Press "Cmd + Shift + R" (MAC)
Reset the page zoom on pages that cause problems: <b>View > Zoom > Reset</b> (Ctrl+0 (zero); Cmd+0 on Mac)
*http://kb.mozillazine.org/Zoom_text_of_web_pages
Start Firefox in <u>[[Safe Mode]]</u> to check if one of the extensions is causing the problem (switch to the DEFAULT theme: Firefox (Tools) > Add-ons > Appearance/Themes).
*Don't make any changes on the Safe mode start window.
*https://support.mozilla.com/kb/Safe+Mode

Keep alive TCP setting for port 3998 to avoid fw timeout?

Hello,
in our new DS6.1 env, replication between the master DS is using port 3998 through several firewalls. If there are no changes to the DB (we are still testing), the connection seems to time out on the firewall and the status of the remote masters in the SMC drops to "stopped" even though they are still running. If one clicks on the DS entry in the SMC, it seems to set up a fresh TCP connection and the status is ok again.
Is there a way to define a keep-alive setting for these connections ?
TIA,
heinz

DS 6.3 has bug 5087249 against it for the missing SO_KEEPALIVE socket option.
This bug was fixed a long time ago in the DS 5.x series which got "unfortunately lost" on the way
to the 6.x release :-(
If you have a valid Sun Support contract you can request a hotfix for this bug 5087249 in
DS 6.3 (or the soon to be released 6.3.1), by raising a support service request.
A similar missing SO_KEEPALIVE socket option bug exists in the DPS 6.3 server,
bug 6782659 is open against this and if you have a valid Sun Support contract you can
request a hotfix for this bug 6782659 in DPS 6.3 (or the soon to be released 6.3.1).
Without a valid support contract, I'm afraid you'll have to wait until the next official patch
release of both these servers (DPS & DS) after the 6.3.1 which does not contain these 2 fixes.
This will most probably be at least one year into the future from present.
The problem with CLOSE_WAITs DPS issue is fixed in the same hotfix for bug 6782659 (which
contains many connection handling bug fixes/enhancement in addition).
Hope this helps.

How to keep alive a session in Web Services?

I have to do my project, that will be including some following features:
1. Login to Application through Web Services method. For example:
http://mydomain.com/web-services/Login?WSDL
2. After logging in, use mySms method to send message to Cellphone through Web Services! For example:
http://mydomain.com/web-services/mySms?WSDL
My questions are:
1. How can I keep alive the session after logging in the application in Web Services? In Web, I can use "Session".
2. If someone has not logged in the Application, he/she could not use mySms method for sending Sms. How can I do that?
3. I know, when I invoke a Web Services, one JavaBean has been called, and this bean is persistence with his own states. It means, if I set value to parameters of this bean, these values are persistence for invoked methods by other persons.
For example:
mySms bean has a private field "jid" inited with NULL value.
Person A invoked mySms.
Then, A set jid of mySms to value "A".
Person B invoked mySms. B got jid value. He receive the result value is "A".
The question is, how can I set mySms bean so that mySms bean is not persistence?
Thanks many!

Hi,
I can right away answer your FIRST Question.
Since WebServices are PURELY Based on SOAP which is in tern based on HTTP, they rely on a Stateless protocol.
I am sure you know that the HTTP is the STATELESS Protocol and so you can not maintain Session and so EACH Http REQUEST is considered as a SEPERATE REQUEST.
Now, still you want to maintain the Session in WebServices,
The simple answer is PASSING PARAMETERS.
Just Maintain your Session on Client (If you are using JSPs or Servlets to CAll WEBSERVICES then maintain Session through your HTTPSession) and each time you Invoke WebService PASS ON REQUIRED Parameters.
This Approach is Exactly like your URL REWriting OR your Parameters Passing through QUERY STRINGS.
I hope you got what I am saying!
Take care,
Himanshu/

Weblogic proxy plugin closes keep-alive connections to clients randomly

In short we have following arhitecture:
clients ---> wl proxy plugin 1 ----> weblogic 1
clients ---> wl proxy plugin 2 ----> weblogic 2
Beacuse of the application/installation specific requirements, we are not using failover, one wl proxy always forwards requests to one weblogic (simple configuration).
Application is TR-069 protocol based (SOAP over HTTP) so it very much relays on persistence TCP connections (Connection: keep-alive). This TCP persistence has to work correctly in order that TR-069 messages are exchanged in required order, otherwise we have a error on application layer.
Here and there we've noticed applications errors which suggest that we have some problems in TCP connection between the client and the weblogic server. After sniffing, we've noticed that weblogic proxy plugin (Apache) randomly, or because of some other reason we do not know, decides to close TCP connection to client, even app on weblogic did not request so ???
As a result, client opens new connection to the server with new TR-069 session and it gets bounced beacuse it allready has one open on weblogic server.
We've sniffed, traced everything we could, we were searching for patterns in time, etc... but we can not find the reason why proxy plugin decides to close the connection to the client (not to the weblogic server).
Trace (replaced sensitive information):
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> URL::parseHeaders: StatusLine set to [200 OK]
Thu Apr 29 15:05:50 2010 <958012725463463784> parsed all headers OK
Thu Apr 29 15:05:50 2010 <958012725463463784> sendResponse() : r->status = '200'
Thu Apr 29 15:05:50 2010 <958012725463463784> canRecycle: conn=1 status=200 isKA=1 clen=545 isCTE=0
Thu Apr 29 15:05:50 2010 <958012725463463784> closeConn: pooling for '$IP$/$PORT$'
Thu Apr 29 15:05:50 2010 <958012725463463784> request [$URL$] processed successfully..................
!!!! Now it closes the TCP connection and inserts "Connection: close" HTTP header !!!
WL proxy plugin conf params are:
WebLogicCluster $IP$:$PORT$
DynamicServerList OFF
KeepAliveTimeout 90
MaxKeepAliveRequests 0
KeepAliveSecs 55
Apache worker configuration is:
<IfModule mpm_worker_module>
PidFile var/run/httpd-worker.pid
LockFile var/run/accept-worker.lock
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 200
ThreadsPerChild 200
MaxClients 2000
MaxRequestsPerChild 0
AcceptMutex pthread
</IfModule>
Why weblogic proxy plugin ignores Keep-alive directive and decides to close connection to the client by itself?
Any help?

If a WebLogic Server instance listed in either the WebLogicCluster parameter or a dynamic cluster list returned from WebLogic Server fails, the failed server is marked as "bad" and the plug-in attempts to connect to the next server in the list.
MaxSkipTime sets the amount of time after which the plug-in will retry the server marked as "bad." The plug-in attempts to connect to a new server in the list each time a unique request is received (that is, a request without a cookie).
Note: The MaxSkips parameter has been deprecated as the MaxSkipTime parameter.
See also here: http://download-llnw.oracle.com/docs/cd/E13222_01/wls/docs81/plugins/plugin_params.html
You said the problem arises under significant load. Maybe, it is wise to tune the number file descriptor's on your operating system. HTTP connections are nothing more than TCP sockets on the operating system. All modern operating systems treat sockets as a specialized form of file access and use data structures called file descriptors to track open sockets and files for an operating system process. To control resource usage for processes on the machine, the operating system restricts the number of open file descriptors per process. You should be aware that all TCP connections that have been gracefully closed by an application will go into what is known as the TIME_WAIT state before being discarded by the operating system.
On most unix systems you can use netstat -a | grep TIME_WAIT | wc -l to detemine the number of socket in time_wait state. You have to check with your system adminstrator how to tune the tcp_time_wait_interval. On solaris you can use: /usr/sbin/ndd -set /dev/tcp tcp_time_wait_interval 60000

Changing Default "Keep Alive" & " Max Processing Time" values in SMICM

Dear Experts
As you aware the default values in SMICM --> Go to --> Services The default values "Keep Alive" & " Max Processing Time" of services like HTTP & HTTPS is 30 sec & 60 seconds respectively.
Every times when we restart application server - we are increasing the time values manually. once we restart they will be reset to original 30 & 60 sec respectively.
I want to make customozed values permanently which should not be lost even after restart of application server.
Please Help
Regards
PR

If you have not set the PROCTIMEOUT parameter, TIMEOUT (or icm/keepalive_timeout) defines both the processing timeout and the keepalive timeout. Also, as of release 6.40, the keepalive timeout is limited to a maximum of 30 seconds.
In a system where the default timeout settings of 30 seconds for the keepalive timeout and the processing timeout are not sufficient because of long-running applications, we recommend that you set the TIMEOUT and PROCTIMEOUT parameters for the relevant services so that you can configure them independently of each other. In addition, we recommend that you do not set the TIMEOUT value higher than necessary, for example, to the usual default value of 30 seconds.
We recommend, for example, the following settings:
icm/server_port_0 = PROT=HTTP,PORT=1080,TIMEOUT=30,PROCTIMEOUT=600
to allow a maximum processing time of 10 minutes.
Thanks,
Tanuj

How to Keep Alive a specific HFM application

My PRD landscape has 2-3 applications. Whenever any application loads for the first time in the memory, it takes quite some time before it is loaded. Once the application is loaded, the response times are pretty quick and acceptable.
During specific parts of the day / month, a specific application becomes active. During this time, other applications may or may not be used, but one specific application is definitely used. I want to keep this application's cubes loaded in the RAM, so that response times are quick, whenever the user needs it - whether for the first time or otherwise.
How to keep alive a specific application's cubes alive and loaded in RAM? I am not looking for general solution like setting the "FM Service" to Automatic (currently it is set Manual) - setting this to Automatic, will affect all applications. However, I am looking for a specific application at a specific period of time.
I am ok with a custom solution if required. Let me know, what are my options.

I think you are looking for an inappropriate solution to your problem. Most HFM applications take a few seconds to start up. If your application takes such a long time to start up you really need to examine the root cause. Start by removing the Sub NoInput and Sub Input routines in your rules to see if this is the reason the application takes so long to start.
If the removal of those routines does not significantly change the startup time, look through the event logs for possible causes. It is possible you have a connection problem with the Oracle database for example, or you have an environment configuration problem where the HFM application servers have a very slow connection to the database server, or possibly the database server performs poorly.
I strongly suggest you investigate these root casues first before trying to make HFM behave in a non-standard way. Certainly you can start the HFM Management Service, which will start all of your HFM applications and keep them all up and running. This approach does not allow the applications to shut down on their own though. Only use this if you have exchausted your investigations (as I suggsted above).
--Chris

Http keep-alive with SOAP webservices

Just had an interesting experience with a web service setup behind UAG...under low load conditions all SOAP responses were coming across with no issue...once a high load was introduced by the client app the behavior changed where an initial request was
processed and subsequent requests were rejected by UAG with a Bad Parameter : Length message...but high load (relatively) on a web browser ran without issue...the client app had to wait ~100 seconds before the next request would process correctly...browser
works - app has problems...turns out it was the keep-alive "default" settings on both the client app server, as well as my web service in IIS...so -apparently UAG thought the 2nd (and subsequent < 100 seconds) were a parameter of the first request...and
was way too long and got rejected...I unchecked the keep-alive enabled box on the http response header (set common headers) and all is fine now! Apparently the browsers were closing the connection with each page load and the service responded appropriately
- so it looked like all was well. Using SOAP UI revealed the error...but it also had it's connection set to keep-alive...once that was disabled in SOAP UI all requests ran correctly...that's when I poked around and found that response header setting.

ejp wrote:
and also an incorrect implementation of the timeout period. This code will still wait forever if no data arrives.You're right... actually I didn't mean to put that while loop there! What I meant was simply
if (!reader.ready())
wait(keepAliveTimeout);
if (!reader.ready())
break mainLoop;
// If we get here there is a new request to read...and I agree that it's ugly, that's why I'm asking you guys for help!
setSoTimeout() is of course a way to go... didn't think of that although I have kind of already added it to my code but with a different timeout. Thanks!
Last question then is:
does reader.readLine() block like reader.read(), or do I have to use the latter?
I would test for myself I could, but at the moment I can't...

Question about Keep Alive feature in Forte 3.

Does anyone use Keep Alive feature under Forte 3.0F.2 environment.
I got trouble and encounters the following problem in the service objects
daily:
INFORMATION: An abnormal disconnect from partition
(CFFE2500-85B0-11D1-B37F-E2F7F3F1AA77:0xec254) was received. Since there
are
no method invocations outstanding to this partition, no notification could
be
given of this disconnect (by indicating a method invocation failed).
Therefore, the information associated with this disconnect is being
reported
to the log.
Class: qqsp_DistAccessException
Error #: [601, 119]
INFORMATION: The connection to the partner was terminated by the
Communication Manager for the reasons below.
Class: qqsp_DistAccessException
Detected at: qqdo_PartitionMgr::StopLocation at 1
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: Failed to establish connection: OS Error 61: Connection
refused
Class: qqsp_DistAccessException
Detected at: qqcm_HoseFSM::SetError at 5
Error Time: Fri Nov 26 17:45:39
SYSTEM ERROR: hose 15 STATE_CONNECTING (EXT_RECEIVED) from
qqcm_HoseFSM::IssueConnect (after EstablishConnection)
Class: qqsp_ErrorDescriptor
Detected at: qqcm_HoseFSM::SetError at 1
Error Time: Fri Nov 26 17:45:39
It seems that Keep Alive sometimes disconnects the connection between the
service objects and the environmental manager.
So that any further connection request from the client encounters the
abnormal exception.
Forte seems not to recommend to use this feature in the Forte Relase note
3.0J1.
She states that "Sites that chooses to test KeepAlives should report all
problems to Technical Support ( and let
Technical Support know that you have enabled this capability)"
Should I disable Keep Alive feature under Forte 3.0F2 environment?
Rgds
Tom

Hey Marco,
I can`t find a view that is named like "APEX_APPLICATION_PAGE_IR%". Is it not available on the evaluation instance.
I don`t want to use the build-in CSV download, becaus I want to export thousands of data sets. I got this already to work with APEX 3.0 and I get the sql from the application views. The procedure which creates the file runs a few hours and after that it is inserted into a table from which the user can download the file. In the procedure there happens a few other things, which are very import, so I have to create my custom solution.
And for that I thought it would be very very very cool if I can get the sql behind the interactive report with the filters ant those things.
Don`t you think that would be possible? I guess the APEX create a SQL although, or am I wrong?
Thank you,
Tim

URLConnection POST to external server requiring keep-alive fails because request is HTTP/1.0

          I have a class that when run as a "main" transmits a HTTP/1.1 post successfully
          to an external server. This external server requires keep-alive connections.
          However when instantiated inside a weblogic servlet container, the post fails
          because the HTTP protocol is set to HTTP/1.0. I have tried this with V5.1 SP11
          and then with V6.1 SP2 with the same result. The code works under Tomcat.
          I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?


Great. I have a question to BEA folks, if they ever read this newsgroup:
          what is the reason for installing WLS protocol handlers, and, if there is
          one, why the implementation is still buggy? I saw many, many instances when
          code making outgoing connections failed to work in WLS, and the solution is
          always the same - use handler which comes with the JVM.
          Bob Bowman <[email protected]> wrote:
          > <[email protected]> wrote:
          >>If it works as a standalone application and fails inside WebLogic, most
          >>likely this
          >>is caused by WebLogic http handler implementation. You can try to modify
          >>your code
          >>like this:
          >>
          >>URL url = new URL(null, "http://some_url", new sun.net.www.protocol.http.Handler());
          >>HttpURLConnection conn = (HttpURLConnection)url.openConnection();
          >>
          >>(you will need to modify weblogic.policy to allow your code to specify
          >>protocol
          >>handler).
          >>
          >>Bob Bowman <[email protected]> wrote:
          >>
          >>> I have a class that when run as a "main" transmits a HTTP/1.1 post
          >>successfully
          >>> to an external server. This external server requires keep-alive connections.
          >>> However when instantiated inside a weblogic servlet container, the
          >>post fails
          >>> because the HTTP protocol is set to HTTP/1.0. I have tried this with
          >>V5.1 SP11
          >>> and then with V6.1 SP2 with the same result. The code works under
          >>Tomcat.
          >>
          >>> I can find no way to force HTTP/1.1 in the URLConnection. Any suggestions?
          >>
          >>--
          >>Dimitri
          > Worked like a champ! Thanks.
          Dimitri

Workstation keep-alive and connectivity failure detection

Dear all,
I intend to automatically detect network failures from my workstation client and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive option. If I understood correctly you can have the workstation generate periodic keep-alive messages to the server and if these are not acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for a disconnection? Otherwise network failures might go by unnoticed if there are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically discriminate if the cause is a network disconnection? It is a pretty generic error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a network failure, can the system recover on its own? or must I reconnect to the server? What I mean is, maybe some keep alive messages where lost, the system passes to the 'disconnected' state, but then the K.A. messages keep being generated and upon correct acknowledgement of these, subsequent ATMI calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep alive message? or is there some sort of tolerance like, say, 'If N messages in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Cacho,
1. I assume that you're talking about the WSL CLOPT option "-K
{client|handler|both|none}", which causes periodic keepalive messages to be
sent. When this option is used, there is no need for the WSC to perform any
periodic operations to keep the network connection alive.
However, if you are worried that the network might suffer a transient
failure and you want to perform your first ATMI call after an extended
period of inactivity as quickly as possible without waiting for another
tpinit(), you may want to perform periodic dummy operations so that you can
reissue the tpinit() if needed as soon as the network connection is
restored.
One option is to make a tpcall() to the ".TMIB" service with an FML32 buffer
where TA_OPERATION is set to "GET" and the other fields are set to retrieve
some system attribute. There is an example of how to call .TMIB at the end
of the TM_MIB(5) manual page. You would want to perform a GET operation
rather than the SET operation shown in that example.
Another option is to write a null service in one of your application servers
which just calls tpreturn() and have your client make periodic cals to that
service.
Calling a verb such as tpalloc() or tpconvert() would not be sufficient,
since these calls do not result in any network traffic.
2. The tperrordetail() function is available in newer releases of Tuxedo to
provide additional information about certain Tuxedo errors. When a
workstation client is disconnected, tperrordetail(0) will return TPED_TERM.
3. If there is a network failure, workstation clients must call tpinit() to
reauthenticate to the system. This is necessary for security reasons.
4. The keepalive option is passed down to the underlying network provider
and Tuxedo has no further involvement with keepalive once it informs the
network of this option. For Sockets the option passed is SO_KEEPALIVE; you
can do a web search on SO_KEEPALIVE to see exactly how the network treats
keepalive messages on your particular platform.
Ed
<Cacho Nakamura> wrote in message news:[email protected]...
Dear all,
I intend to automatically detect network failures from my workstation client
and have it attempt to reconnect to the server on its own.
Browsing the documentation for related information I saw the keep-alive
option. If I understood correctly you can have the workstation generate
periodic keep-alive messages to the server and if these are not
acknowledged, all subsequent ATMI calls will fail with TPESYSTEM.
My doubts regarding this are the following:
1) Is there some dummy ATMI function I can invoke periodically to check for
a disconnection? Otherwise network failures might go by unnoticed if there
are periods where my WSC doesn't require to communicate with the server.
2) Once I get a TPESYSTEM failure, is there some way to programatically
discriminate if the cause is a network disconnection? It is a pretty generic
error after all.
3) Once all ATMI functions start failing due to keep-alive detecting a
network failure, can the system recover on its own? or must I reconnect to
the server? What I mean is, maybe some keep alive messages where lost, the
system passes to the 'disconnected' state, but then the K.A. messages keep
being generated and upon correct acknowledgement of these, subsequent ATMI
calls will stop failing.
4) Does the WSC go to 'disconnected' state after the first unanswered keep
alive message? or is there some sort of tolerance like, say, 'If N messages
in a row are not answered then assume the connection to be dead'.
I'm sorry if it was too long a post, but neither searching the documentation
nor this forum clarified any of these issues for me.
Many thanks for your attention.
Regards.

Keep Alive burst configuration ATA 122

Hi Guys,
Sorry if this is not posted in the correct place, if it is not please advise me and i will move it. I am hoping this is very quick question but basically i have got some ATAs that when plugging in a sounder (bell) or a Cordless analogue phone every 60 seconds or so the osunder makes a noise and the the phone basically thinks it is making a call. done a bit of research and i think this is due to the keep alive burst. Wondered if anybody knew how i can turn this off or extend it to maximum length. I have logged into the cisco and i dont seem to have many options so not sure if this is due to me lookinhg in wrong place or the fact it hasnt a different configuration file.
The ATA are being used on the BT IPVS system.
if somebody could please reply would appreciate it.
thank you

Hi Mateus,
As you can see in the output:-
Aug 01 20:35:02 [IKEv1]Group = DefaultRAGroup, IP = 197.217.68.99, PHASE 1 COMPLETED
Phase 1 is getting completed and QM FSM error indicates the issue with transform-set and/or crypto access-list .
Please try using ESP-3DES and ESP-SHA-HMAC for transform set and let us know how it fares.
You might as well try using PAP as authentication.
Regards,
Dinesh Moudgil
P.S. Please rate helpful posts.

Keep alive using plain DHCP

Hi. My ISP assigns IPs using DHCP and then requires a manual login via an HTML form. After that you will be automatically logged out after some time of inactivity.
I'm looking into buying the WRV200 and wonder if I can set it up to remain connected despite user inactivity. I see it has keep alive for PPPoE etc, but I can't use PPPoE.
Is there any other way to keep the connection alive? By creating a VPN tunnel and set a key lifetime lower than my ISPs timeout??? Or does the VPN disconnect after some inactivity too...?
Thanks in advance.

I keep the same IP for months at a time, so that is not the problem.
The problem is that after 1 hour (or so) with no traffic sent from my IP, all the traffic from my endpoint is blocked until I manually log in again via a web form that, I am redirected to whatever URL I enter in the browser.
So if there is any way to make the router send a package every x minutes, I would stay logged on.
(IPSec key exchange would be such a package, if those are sent even when the tunnel is not in use from any computer on my LAN.)
There is software avalable for the PC that sends these keep alive packages, but I want the router to send them so that I can check my e-mail using my WLAN enabled cell phone even though I have had the PC turned off for hours.

Keep-alive message bridge connection

Hi,
I have setup messaging bridge between WLS 10.3.0.0 and a JBoss Messaging queque, after about 4 hours of inactivity in a queue bridge was disconneted, is there any way to configure keep-alive connection in WLS bridge ?
Thanks,
Lukasz

You can try to set the IdleTimeMaximum setting on your bridge configuration to a very large number. It specifies the maximum amount of time, in seconds, that a messaging bridge instance remains idle.
In “asynchronous” mode, this is the longest amount of time a messaging bridge instance stays idle before it checks the sanity of its connection to the source. In “synchronous” mode, this is the amount of time the messaging bridge can block on a receive call if no transaction is involved.
-Dongbo

LDAP keep-alive connection ? (use of ldap_io_fns)

Hi there,
I am facing a new req. from network security guys that want to close 'idle' connections that crosses firewalls. But as I do use persistent search connection which are not very 'busy' => i.e. not enough traffic to be kept open by FireWall rule.
Consequence my client could not 'detect' this cut of connection and do not receive any more the 'updates' through persistent search.
I am now trying to init my connection setting optional io_fns structure changing the socket func by my socket func that do create a keep-alive socket.
But it does not bind properly ... Init seem ok but bind never get out. LDAP receives bind and do log it but seem not able to respond properly ...
Any idea on how to use this io_fns struct ?
Many thanks.
Hedi.
.

the problem is not that process is in foreground or background: the problem is the timeout: I need to avoid timeout, because the idea is to launch the report and then go out for lunch So I need to find a way in the code to advise the system that user has not to be logged out.
Thanks
Gabriele

WRT54G v 7.0 -- Setting "Keep Alive: Redial Period" not correct (radio button)

Similar Messages

Maybe you are looking for