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

RE: ERXObjectStoreCoordinatorPool exception


  • Subject: RE: ERXObjectStoreCoordinatorPool exception
  • From: Michael Gargano <email@hidden>
  • Date: Tue, 13 Dec 2011 23:27:03 -0800
  • Acceptlanguage: en-US
  • Thread-topic: ERXObjectStoreCoordinatorPool exception

Okay, I’ve figured out how to set this up across servers, but I’m still seeing the exception.  Doesn’t seem to cause any problems but I haven’t met a stack trace I like.

 

I’m a little unsure exactly why you need to make the choice between using the remote synchronizer and using setFetchTimestamp(System.getCurrentTimeInMillis()) on EC creation.  Isn’t the end effect really the same?  The DB cache gets the freshest data in both cases, no?

 

Thanks.

-Mike

 

 

From: webobjects-dev-bounces+mgargano=email@hidden [mailto:webobjects-dev-bounces+mgargano=email@hidden] On Behalf Of Michael Gargano
Sent: Monday, December 12, 2011 4:50 PM
To: WebObjects webobjects-dev
Subject: ERXObjectStoreCoordinatorPool exception

 

Hi again,

 

I just configured the ERXObjectStoreCoordinatorPool have 4 coordinators using the ERJGroupSyncronizer.

 

I have 2 application servers running 2 apps each.  The apps on each box talk to each other and both servers share one DB.

 

 

Server A                                                                                  Server B

---------------------------                                      ---------------------------

myApp                                                                                    myApp

taskRunnerApp                                                           taskRunnerApp

                                                            \                       /

                                                            DB Server

                                                           

 

Everything seems to be running okay, but now that I've turned on the coordinator pool I see this strange exception.

 

ERROR er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer  - java.lang.NullPointerException

NullPointerException

  at er.extensions.eof.ERXEOAccessUtilities.databaseContextForEntityNamed(ERXEOAccessUtilities.java:1011)

  at er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer$ProcessChangesQueue._process(ERXObjectStoreCoordinatorSynchronizer.java:490)

  at er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer$ProcessChangesQueue.process(ERXObjectStoreCoordinatorSynchronizer.java:521)

  at er.extensions.eof.ERXObjectStoreCoordinatorSynchronizer$ProcessChangesQueue.run(ERXObjectStoreCoordinatorSynchronizer.java:598)

  ... skipped 1 stack elements

 

Anything to be concerned about?

 

I also set both apps to use the same group name, so I assume that means that it's syncing the EOF stacks across both apps.  Is there a way to do this across servers as well, and is that even a good idea?

 

Thanks.

-Mike

 

 _______________________________________________
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

References: 
 >ERXObjectStoreCoordinatorPool exception (From: Michael Gargano <email@hidden>)

  • Prev by Date: Re: Can someone explain how this ERXKey works?
  • Next by Date: Re: What wonder branch is what?
  • Previous by thread: ERXObjectStoreCoordinatorPool exception
  • Next by thread: How do I get the ERFileAttachment webPath in ERRest?
  • Index(es):
    • Date
    • Thread