Unable to connect to DB -- DB2 LUW 10.5

Hi All

I am facing the below Error message in my Application logs.

 Invalid operation: Connection is closed. ERRORCODE=-4470, SQLSTATE=08003

Can any one give inputs to solve this.

Does increasing LOGFILSZ help to solve this.

Application is not able to connect to DB.
Prardhan NAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kent OlsenDBACommented:
Hi sridhar,

Is there anything else in the error log?  (Check the system logs and db2diag.log)

In generic terms, the message you're seeing means "an error occurred so the connection is being closed".  We'll need to find out what the error is to know why the connection is closing.
Prardhan NAuthor Commented:
Hi Kent

There are no Error Messages in Diag Logs or notify logs.
Tomas Helgi JohannssonCommented:

What about warnings ?
What db2 driver (version) are you using to connect to the database ?

    Tomas Helgi
Become a CompTIA Certified Healthcare IT Tech

This course will help prep you to earn the CompTIA Healthcare IT Technician certification showing that you have the knowledge and skills needed to succeed in installing, managing, and troubleshooting IT systems in medical and clinical settings.

Kent OlsenDBACommented:
There should be a stack trace associated with the error.  It is probably showing on the application side even though it appears that it's not being written to the log file(s).  

As noted, the message is a result of a previous error and any of several errors can result in the message that you're seeing.  It can be a logging issue, connection issue, connection pooling, or driver issue.  Are you using Tomcat or other middleware?

I'm hesitant to suggest a fix without knowing the cause,
Tomas Helgi JohannssonCommented:

If this warning (similar to this one)
ADM1541W Application "db2jcc_application" with application handle
"0-9663" and application id ""
executing under authentication id "DB2INST1" has been forced off of
the database for violating database configuration parameter
NUM_LOG_SPAN (current value "8"). The unit of work will be rolled

is in your db2diag.log then your LOGFILSIZ and LOGPRIMARY/LOGSECONDARY config parameters are to low for your biggest UOW.
Connections can suffer from connection closed if that is the case.
Post the output of
db2 get db cfg for <yourdb> | grep LOG

Open in new window

    Tomas Helgi

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Prardhan NAuthor Commented:
No, This Warning is not seen in Diag log and notify logs.
Prardhan NAuthor Commented:
Thanks for your timely inputs.
Kent OlsenDBACommented:
What did the issue turn out to be?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.