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

Similar Messages

I.tunes keep getting message not connected to the internet when I am

I keep getting message I am not connected to the internet when I try to access itunes store when I am connected

Hey confused joseph,
Thanks for the question. I understand you are experiencing issues connecting to the iTunes Store. The following resource should help you troubleshoot these issues.
Can't connect to the iTunes Store
http://support.apple.com/kb/TS1368
Thanks,
Matt M.

Message bridge connecting to MQ shows active/forwarding messages but fails to deliver

Created a message bridge between active MQ and weblogic.
Status shows active >>forwarding messages
when i put a message in the queue i see the following error in the logs
<Aug 21, 2013 5:13:29 PM PDT> <Warning> <MessagingBridge> <BEA-200026> <Bridge "
Bridge-1" encountered some problems in one of its adapters or underlying systems
. It stopped transferring messages and will try to reconnect to the adapters sho
(The exception caught was javax.resource.ResourceException: Error sending
message.)>
Weblogic10.3

We resolved this issue by using the latest Active MQ jar.Earlier we were using 5.4.3 now when using the latest version this issue got resolved

HT4623 trying to update to 6.1.3 but keep getting message not connected to the internet when it is

I am trying to update my ipad to 6.1.3 and even though it is connected to the internet, i keep getting the message: unable to update not connected to the interent.
Any suggestions?

Try using this extension to force compatibility.
* https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/
Check and tell if its working.

Keep alive sybase database connection

Hi,
How we can keep connections alive. In our application we are using java as frond-end and making connection to sybase database server using jconnect. We are firing big queries which took generally more than two hours to run. But firewall drops the connection which are ideal for more than 1 hour.
So, is there any way out to keep those connections alive.
Thanks in advance.

Anup_Agr wrote:
Hi,
How we can keep connections alive. In our application we are using java as frond-end and making connection to sybase database server using jconnect. We are firing big queries which took generally more than two hours to run. But firewall drops the connection which are ideal for more than 1 hour.
So, is there any way out to keep those connections alive.Yes but that would be a poor solution.
You shouldn't be attempting to run a job that takes that long. Googling certainly suggests that Sybase supports scheduled jobs.
That suggests the following
1. Create a job queue (table)
2. Create a scheduled task to process tasks in the job queue.
3. Modify your app to put a task in the job queue.
4. Modify your app to query for a complete job at some reasonable interval (like minutes.)
And you might look further at the design and requirements for that matter. For example there is no point in running a 2 hour job 15 times a day that returns the same results because 15 people want the same results. Instead run the job once at midnight and keep the results and return those each time for the 15 requests.
Even if the jobs are different sometimes the data can be munged in a nightly process to make it more efficient. For example create a summary for each account. Then a sales report for a specific sale rep just collects the existing summaries rather than summerizing it each time.

Keep getting message not connected to Internet when settings say I am

our Internet provider is talk talk. Our modem is in the lounge. Whe upstairs the ipad keeps saying we are not connected to the Internet. Settings say that we are. Any thoughts?

Hello, Wy507sa.
Thank you for visiting Apple Support Communities.
This sounds like you may be experiencing a self-assigned IP address. Try power cycling your router and testing the results. If the issue persists, I would recommend going through all of the steps in the article below.
iOS: Troubleshooting Wi-Fi networks and connections
http://support.apple.com/kb/ts1398
Cheers,
Jason H.

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 SMTP connection

Hi,
Is there any way to keep alive a SMTP connection forever using JavaMail? I know being a TCP connection, the connection will be broken if no data is exchanged for specific time. What if NOOP command is send to SMTP server as a heart beat. Can anybody suggest how this can be accomplished using JavaMail?
Thanks,
Atul

You can call the isConnected method, but your server isn't going to like you if you
keep a connection open even though you're not using it.

CM1312 NFP: WIndows 7: USB Error message ~"Lost Connection"

With the 1312 connected to my Windwos 7 desktop, periodically Windows gives an error message that indicates that it has lost connection to the printer. Unplugging and replugging the USB cable fixes the problem. Otherwise the print & scan functions work perfectly. Symptomatically it appears as if the printer goes to sleep and stops responding to whatever "keep alive" messages Windows might be sending. Is there a setting in the printer, in Windows or in the printer driver software that can prevent this message?
BTW, the other way to work around this problem is to just access the printer via the Ethernet but the scan funciton is not accessible via the network (an unfortunate limitation).

aluniewski,
I am sorry, but to get your issue more exposure I would suggest posting it in the commercial forums since this is a commercial printer. You can do this at http://h30499.www3.hp.com/hpeb/ .
I hope this helps.
↙-----------How do I give Kudos?| How do I mark a post as Solved? ----------------↓

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

Messaging Bridge keeps dying

I am using weblogic 10.3 on sunos and i am seeing this issue where the messaging bridges keep dying ever so often(once or twice a week). I have over 15 servers in the weblogic domain but out of them only 2-3 messaging bridges die at random. The issue is compounded by the fact that the weblogic logs say unable to connect to source destination will retry later but weblogic never retries. I can't see any configuration where i can configure duration and number of retries for messaging bridges. Does anyone know how to fix this problem?

Ok is there a way anyone knows of by which we can reset the messaging bridge from the admin console without having to restart the managed server?

HTTP persistent connection (keep Alive) problem

Hi,
I'm trying to deploy a RPC web service and I would like to use the HTTP 1.1 keep alive feature (which should be the default).
I generated the server side and client side code using jdev 903. The AS is OC4j 903.
The problem is that the server is sending a âConnection: close:â header in the SOAP response, despite the client sending a âConnection: keep-aliveâ header in the request. This is obviously causing the client to close the connection and open another for the next message.
The documentation implies that the server will always try to use persistent connections, even so, in the file:
<OC4J_HOME>/j2ee/home/config/http-web-site.xml
there is a config option âuse-keep-alivesâ. Setting this to true has no effect.
Iâm guessing there must be another option somewhere to turn on connection persistence.
Can anyone please help ?

Does anyone know whether Oracle Supports persistent connections ?
I tested this on JBOSS and I seems to get better performance.
cheers.

I keep trying to update but Keep getting message that network connection timed out. What shall I do, I do not know how to disconect my firewall

Trying to update ipad2 software. Keep getting message that network connection timed out. Don't know how to cancel the firewall

Im getting the same thing...

My iPod touch 4th gen. Keeps giving me the error message "cannot connect to the app store when I sign in. I can open the app store and browse it but I can't download anything. I have full signal strength with my wi-fi and safari is working perfect.

My iPod touch 4th gen. Keeps giving me the error message "cannot connect to the app store when I sign in. I can open the app store and browse it but I can't download anything. I have full signal strength with my wi-fi and safari is working perfect. I turned it off and restarted it 3 times now. I have an iPad 2 and the app store works flawlessly with it. What is going on?

Same here on my lpad2. Can access the web just fine from browsers but cannot install new apps or updates in appl store. Seeing a few others reporting same issue tonight so likely an apple server issue and staff will notice it in network monitors and fix it...sometime this weekend.
Rob

HT202667 I switched from att to charter internet and change e-mail address. I keep getting messages telling me my at&t iCloud account is not connected. How do I get rid of the at&t iCloud message?

I switched from att to charter internet and change e-mail address. I keep getting messages telling me my at&t iCloud account is not connected. How do I get rid of the at&t iCloud message?

Hi adamsfly,
Thanks for using Apple Support Communities. Based on what you stated, it sounds like you changed your email address and iCloud is looking to sign in with the old Apple ID email. I would recommend that you read this article, it may be able to help the issue.
What to do after you change your Apple ID email address or password - Apple Support
Cheers,
Mario

Keep-alive message bridge connection

Similar Messages

Maybe you are looking for