• 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: Oracle connection
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Oracle connection


  • Subject: Re: Oracle connection
  • From: Don Lindsay <email@hidden>
  • Date: Tue, 23 Feb 2010 15:44:11 -0500

I have seen this before. it is not an issue with the oracle plugin. What the ER is trying to do is re-fault all your objects for webobjects. This results in an out of memory error.


I would say, just guessing because I cannot see your EO Model.

You have too many bidirectional relationships. To one in one direction and to many back to the parent. In my experience if you have too many of these types of relationships (the toMany back to a parent table with many records associated), you can get out of heap space errors when WO attempts to re-fault your objects.

Try removing some of your toMany relationships from your model or making these relationships so they do not get cached and are only faulted when needed. See if that does not stop the error.

WebObjects is seeing a change (commit) from your forms application which then forces a re-fault.

Don


On Feb 23, 2010, at 2:16 PM, Fabián Montealegre Carvajal wrote:

Sorry for not giving all the details.

We have a WO 5.3 Wonder app. It's connected to a Oracle 10G db. It is allowing concurrent request handling (setAllowsConcurrentRequestHandling(true)).

This is the DB connection:

model.URL=jdbc:oracle:thin:@xxx.xxx.xxx.xxx:1521:bdtouse
model.DBUser=user
model.DBPassword=password
model.DBDriver=oracle.jdbc.driver.OracleDriver (version: 9.0.2.0.0)
model.DBPlugin=com.webobjects.jdbcadaptor.OraclePlugIn


The production environment is tomcat 5.5, java jdk 1.5, Windows Server 2003 standard revision SP 2.

The app is actually working properly. Nevertheless, we have detected that when a process from another app (oracle forms) is executed, said process hogs all the resources from the DB. It appears that the oracle service relegates the WO requests. After that, Tomcat starts eating memory until it dies with a out of memory error. We have to restart the service all over again.

Any ideas how to solve this? Maybe a Tomcat tweak?

Thank you very much for your time.

--
Fabián Montealegre Carvajal

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


This email sent to email@hidden

_______________________________________________ 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: Oracle connection
      • From: Fabián Montealegre Carvajal <email@hidden>
References: 
 >Oracle connection (From: Fabián Montealegre Carvajal <email@hidden>)
 >Re: Oracle connection (From: Don Lindsay <email@hidden>)
 >Re: Oracle connection (From: Fabián Montealegre Carvajal <email@hidden>)

  • Prev by Date: Re: Error on deployment - Can't connect to window server
  • Next by Date: Re: Error on deployment - Can't connect to window server
  • Previous by thread: Re: Oracle connection
  • Next by thread: Re: Oracle connection
  • Index(es):
    • Date
    • Thread