• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
WebSphere connection pool and deadlock - HELP!
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WebSphere connection pool and deadlock - HELP!


  • Subject: WebSphere connection pool and deadlock - HELP!
  • From: David Aspinall <email@hidden>
  • Date: Tue, 2 May 2006 16:30:48 -0400

We have a client who insists on using WebSphere 5.0. At first everything was fine, but all our database connections were created using JDBC connection logic. The client insists we use the JNDI naming context for finding and using the websphere connection pool and we began to encounter problems.

The first problem was that sub-threads are not permitted under the servlet spec and so the behaviour if "undefined". This shows up initially as the subthreads are not able to find the JNDI named context so nothing connects. My fix for this is to perform all actions in the current request response loop (no backgrounding).

Now that I have everything connecting correctly I am creating a database deadlock constantly. Basically is seems that fetches are locking database rows, but the insert/updates are going to the database in a different connection and so are deadlocking on the same objects. No deadlock occurs until an INSERT is sent for an object related to a previous fetch. For example I can insert ActivityLogs all day since they have no relationships, but if I insert a new ContactLog for a Household .. dead.

I have tried:
- turning on concurrent request handling (thought it might change the fetch lock logic)
- put in a custom SQLServerPlugin and overrode lockClause() to return an empty string.
- did all editing in the session editing context
- did initial fetches in the session EC, then all edits in a new EC
- did initial fetches in the session EC, then all edits in a new EC with a new ObjectStoreCoordinator
- reverting to straight JDBC, no pool works fine.


I'm not sure where to go next.

Other notes:

- WebSphere 5.0.x deployed on SUSE
- MS SQLServer 2000
- WebObjects 5.2.4

- Fastest way to reproduce is to submit a delta XML document via DirectAction POST.


Thanks, David --- email@hidden (416) 513-9524 x263

Ticoon Technology Inc.
56 The Esplanade, Suite 404, Toronto, ON, M5E 1A7



_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Prev by Date: Re: simple encoding question :-)
  • Next by Date: Re: Bug in WOContext.directActionURLForActionNamed() when using query dictionary
  • Previous by thread: Re: simple encoding question :-)
  • Next by thread: Re: WebSphere connection pool and deadlock - HELP!
  • Index(es):
    • Date
    • Thread