ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexWebSphere Message Broker SupportIIB Database Connection Manager Doesnt Purge Idle Connection

Post new topicReply to topic
IIB Database Connection Manager Doesnt Purge Idle Connection View previous topic :: View next topic
Author Message
eammnsh
PostPosted: Thu Dec 29, 2016 5:04 am Post subject: IIB Database Connection Manager Doesnt Purge Idle Connection Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

HI Everyone,
we Have IIB V9.0.0.2 on Linux x86-46, we have configured an ODBC connection to Oracle 11g server, and currently we are facing a weird behavior.

We have set the Max Connection Age to 60 seconds (default), but we can see that the IIB doesnt purge/close those idle connections, and they stay there for hours.

Shouldnt the IIB kill the idle connections, which stay idle for more than 60 seconds? Or my understanding is wrong?
I was searching for V9 fixes but couldn't find any fix related to this issue!

Did anyone face this issue before?
The easy way is to ask the DBA to create a profile for the IIB and to purge the idle connections, but I dont think this is smart.

Thanks,
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Dec 29, 2016 5:22 am Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6077
Location: Somewhere over the Rainbow this side of Never-never land.

Why do you want the connections to close?
Is it causing you a problem somewhere?

AFAIK, IIB keeps the connections to the DB open so that when the time comes to access the DB it can resuse those connections rather than going through the whole connect/authenticate process which slows things down.

There might be some internal to IBM reason for keeping them open and as such, even a PMR won't give you that information.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
eammnsh
PostPosted: Thu Dec 29, 2016 5:25 am Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

Because we are getting the below error:
Child SQL exception
08001
-1
[unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack [unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack

And when I spoke to the DBA, he shows me that the IIB has more than 300 idle/inactive session not terminated.
Back to top
View user's profile Send private message
eammnsh
PostPosted: Thu Dec 29, 2016 5:47 am Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

Also, We have found that even when there are inactive connections, the iib initiate new connections instead of reusing the inactive sessions.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Thu Dec 29, 2016 6:16 am Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6077
Location: Somewhere over the Rainbow this side of Never-never land.

eammnsh wrote:
Because we are getting the below error:
Child SQL exception
08001
-1
[unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack [unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]TNS-12516: TNS:listener could not find available handler with matching protocol stack

And when I spoke to the DBA, he shows me that the IIB has more than 300 idle/inactive session not terminated.


It would have been nice to have included that bit of information in the original post.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
eammnsh
PostPosted: Fri Dec 30, 2016 8:32 am Post subject: Reply with quote

Apprentice

Joined: 22 Aug 2016
Posts: 29

We have opened a PMR with IBM to check this issue, another piece of information that might be useful, when I asked the DBA to kill the inactive sessions, which had been inactive for 5 minutes, this error started to appear in our logs:
Child SQL exception
HY000
1012
[unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01012: not logged on [unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01012: not logged on
Back to top
View user's profile Send private message
jmduran
PostPosted: Wed Feb 14, 2018 6:57 am Post subject: Reply with quote

Newbie

Joined: 14 Feb 2018
Posts: 1

eammnsh wrote:
We have opened a PMR with IBM to check this issue, another piece of information that might be useful, when I asked the DBA to kill the inactive sessions, which had been inactive for 5 minutes, this error started to appear in our logs:
Child SQL exception
HY000
1012
[unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01012: not logged on [unixODBC][IBM][ODBC Oracle Wire Protocol driver][Oracle]ORA-01012: not logged on


Hi eammnsh

We are facing the same problem, do you have any update of your PMR from IBM?

Thank you
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Feb 14, 2018 7:03 am Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 24972
Location: Ohio, USA

jmduran wrote:


Hi eammnsh

We are facing the same problem, do you have any update of your PMR from IBM?

Thank you


After all this time, I would imagine so. IBM's not that slow at responding, even to non-priority PMRs. I should point out the OP's not posted in over a year.

I would also put it to you that you don't have the same problem, because you're not on the same level of IIB as the OP. If you are, I've solved your problem - any fix supplied as part of this PMR would have been rolled into the product by now so update to the latest maintenance and see if the problem persists.

If so, open a new thread here (referencing this if you're so inclined) and a new PMR.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Feb 14, 2018 8:23 am Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5645
Location: UK

Apply the latest fixpack to that version and see if it still happens.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error.
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexWebSphere Message Broker SupportIIB Database Connection Manager Doesnt Purge Idle Connection
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.