• 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
Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context


  • Subject: Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
  • From: Chuck Hill <email@hidden>
  • Date: Thu, 22 Apr 2010 15:09:24 -0700


On Apr 22, 2010, at 2:17 PM, Farrukh Ijaz wrote:

Hi WOGurus,

1. We've few applications based on same database structure. What happens, one of the application after approximately 500 hits gets down. What can be the reason for that? (I know the question is too broad but would appreciate for any clues).

What does "gets down" mean? Runs out of memory? The JVM process crashes? Deadlocks?



2. Sometimes the logs show message with Runtime Exception "Statement running too long" what can be the reason.

The statement running too long? Un-optimized or sub-optimal SQL can cause this. Which database? Using Wonder?



Does the database backup running on the same database can cause this problem? If yes, how to fix that?

It could by making the machine slower. The fix is database dependent. You could replicated it on a different machine and backup that machine.



3. I've read in the documentation that we can have multiple editing context but all of them by default share 1 database context.

More importantly one database connection.


What I understand from this is if we configure pooling setting in the properties file it won't have any affect since there is only one channel for database. Is that right?

I guess that depends on which pooling you are referring to. One I am thinking of randomly assigned an EOF stack wtih DB connection to new sessions.



If yes, how can we enable them to utilize connection pooling without creating multiple database contexts per session.




Chuck


-- Chuck Hill Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects








_______________________________________________
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


  • Follow-Ups:
    • Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
      • From: Farrukh Ijaz <email@hidden>
References: 
 >Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context (From: Farrukh Ijaz <email@hidden>)

  • Prev by Date: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
  • Next by Date: Re: DB2
  • Previous by thread: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
  • Next by thread: Re: Instance gets down after approx 500 hits; Database backup; Connection pooling with Single Database Context
  • Index(es):
    • Date
    • Thread