DB2Connect issue

We are having an issue with DB2Connect 8 where the "DB2 JDBC Applet Server" service hangs when a JDBC Connection attempts a call to the server. Does anyone know what type of issues we can look for as to the source of the problem? Also, is there a possibility that this is a load issue with the DB2 Connect Services? I have heard that there is a limit to the traffic that DB2 Connect traffic can handle, but have not been able to track down what that limit is.

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.

IBM has a great knowledgebase on DB2 Connect at  http://www-306.ibm.com/software/data/support/

RevelationCSAuthor Commented:

I am aware of the knowledgebase, however, I have been unable to locate anything that appears to be related to our specific issue... this would be why I brought the questions here....
RevelationCSAuthor Commented:
also, to note, I have discovered that a large number of the following errors are being thrown in the jdbcerr.log file:

(Mon Nov 29 12:11:55 2004) pid= 2284 jdbcServiceConnection(): Invalid Request Received., einfo= 0 (client IP = x.x.x.x)

Based on the information that we have, the versions should be correct for the db2java.zip and the version of DB2Connect that is installed on the server.
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

RevelationCSAuthor Commented:
this issue is still ongoing, I will post back if I resolve the issue... anyother recommendations?
RevelationCSAuthor Commented:
We have since been able to resolve the issue... We were able to track the problem down to having two different versions of the drivers out there. Even though the sites were pointed at the correct JDBC URL and using the appropriate set of drivers based on the DB2 Connect server it was pointed at, the issue appeared to occur whenever there was a simultaneous execution of the different drivers. Once we had everyone moved to the new DB2 Connect server with the appropriate set of drivers for that server, our issues stopped.
Closed, 500 points refunded.

Community Support Moderator
Experts Exchange

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
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.