| Author |
Message
|
| SilentWind |
 Posted: Sun Jul 29, 2007 11:36 pm Post subject: MQ and Weblogic |
 |
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
I am using MQSeries 6.0.2.1 with Weblogic 8.1.
I have configured the MQSeries to be the JMS provider for Weblogic, and have set up the neccessary queues and channels for communication. Everything seem to work except there are 2 symptoms which I am unable to resolve:
1. Number of CLOSE_WAIT TCP connections increase exponentially. I have already tuned by Windows 2000 OS performance by setting TcpTimedWaitDelay to 30 seconds. But still the connection remains. (Approximately 8000 connections and increasing)
2. There are 3 stuck threads in Weblogic, in which those threads happen to be MDB listeners for topics in MQSeries. They continue to exist after the default expiration time of 600 seconds.
The 2 problems may be related, but I have searched for various articles but to no avail. Can these be resolved? |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Mon Jul 30, 2007 2:49 am Post subject: Re: MQ and Weblogic |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| SilentWind wrote: |
I am using MQSeries 6.0.2.1 with Weblogic 8.1.
I have configured the MQSeries to be the JMS provider for Weblogic, and have set up the neccessary queues and channels for communication. Everything seem to work except there are 2 symptoms which I am unable to resolve:
1. Number of CLOSE_WAIT TCP connections increase exponentially. I have already tuned by Windows 2000 OS performance by setting TcpTimedWaitDelay to 30 seconds. But still the connection remains. (Approximately 8000 connections and increasing)
2. There are 3 stuck threads in Weblogic, in which those threads happen to be MDB listeners for topics in MQSeries. They continue to exist after the default expiration time of 600 seconds.
The 2 problems may be related, but I have searched for various articles but to no avail. Can these be resolved? |
1) Make sure your programs close the connection when they are done.
For each .createConnection your need a corresponding connection.close().
2) Make sure the TCF/QCF is setup with FAIL_IF_QUIESCING.
And yes they will stay open for the duration of the JVM or MQServer whichever shuts down first... Read the red book on JMS Topology...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SilentWind |
| Posted: Mon Jul 30, 2007 3:20 am Post subject: Re: MQ and Weblogic |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
[quote="fjb_saper]
1) Make sure your programs close the connection when they are done.
For each .createConnection your need a corresponding connection.close().
2) Make sure the TCF/QCF is setup with FAIL_IF_QUIESCING.
And yes they will stay open for the duration of the JVM or MQServer whichever shuts down first... Read the red book on JMS Topology...
[quote]
1) I don't actually have a program in this case. Because I use Weblogic console to configure a foreign JMS connection factory which matches to the JNDI name of the MQ factory.
2) My TCF has FAIL_IF_QUIESCING set as default. My QCF does not have that option to set. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jul 30, 2007 1:32 pm Post subject: Re: MQ and Weblogic |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20768
Location: LI,NY
|
| SilentWind wrote: |
2) My TCF has FAIL_IF_QUIESCING set as default. My QCF does not have that option to set. |
It should.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| SilentWind |
| Posted: Mon Jul 30, 2007 5:50 pm Post subject: Re: MQ and Weblogic |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
[quote="fjb_saper"][quote="SilentWind"]
2) My TCF has FAIL_IF_QUIESCING set as default. My QCF does not have that option to set.[/quote]
It should. :oops:[/quote]
Is there some other way to reduce the number of CLOSE_WAIT? Because it is taking up all my TCP connections and eventually I get the error.
"Socket connection attempt refused."
When I get the error, I do a netstat and I find all my TCP connnections to the MQ server with the state CLOSE_WAIT.
Or can this be caused by a Weblogic problem as it is actually Weblogic which tries to publish to the MQ server? |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Tue Jul 31, 2007 6:04 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
We had the exact same issue with WL apps connecting to Solaris. I opened a PMR with IBM, BEA and Sun - and was advised that all was functioning properly and to tune the tcp_close_wait_interval on Solaris from the default of 240000 (4 min) to 60000 (1 min).
Not sure what the equivalent setting is in Windows.
Steve |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Tue Jul 31, 2007 6:26 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I seem to recall, although probably incorrectly, a previous mention of an issue with WebLogic that looked similar, and was fixed by a fix from WebLogic.
Probably worth searching for, although probably also I am remembering wrong.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Tue Jul 31, 2007 6:36 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
I've seen the problem mentioned in threads, but have never seen a particular fix for it. If there is one out there, I would love to have it.
That and a fix for every other problem WebLogic causes me in MQ.
Steve |
|
| Back to top |
|
|
| SilentWind |
| Posted: Tue Jul 31, 2007 5:52 pm Post subject: |
|
|
Acolyte
Joined: 11 Jan 2006
Posts: 58
|
| Toronto_MQ wrote: |
I've seen the problem mentioned in threads, but have never seen a particular fix for it. If there is one out there, I would love to have it.
That and a fix for every other problem WebLogic causes me in MQ.
Steve |
Alright, at least I can focus my search on Weblogic instead of MQ, since it is possible that the fix is on Weblogic.
Many thanks for the info. |
|
| Back to top |
|
|
|
|
