Re: Wonderizing an existing app

John Pollard <[email protected]>
Newsgroups gmane.comp.web.webobjects.wonder-disc
Message-ID <[email protected]>
>> I have successfully Wonderized one application and am now trying my second, following instructions http://wiki.wocommunity.org/display/documentation/Integrate+Wonder+Into+an+Existing+Application
>> 
>> Biggest issue, my browser shows "An Internal Server Error Has Occurred."
> 
> Every request?  Just some of them?  That should indicate an exception thrown very early or very late in the RR loop.

Every request but this problem goes away if I set:
er.extensions.ERXEC.safeLocking=false
So the existing manual locking/unlocking in this app is somehow upsetting ERXEC lock management. Would it be reasonable to leave this setting as false and to retain our existing locking/unlocking which has been deployed and working for years?

Another thing I read is that ERXEC sets a default delegate, though our app is itself setting an EC delegate, presumably displacing whatever ERXEC had in mind. I can investigate further, but if anyone has info on what job the ERXEC delegate does and whether I should try to make sure it is used in our app...that would be of interest.

>> which I suspect relates to the last shown log line:
>> 
>> Mar 06 17:27:45 MPMall[9999] WARN  NSLog  - <WOWorkerThread id=15 socket=Socket[addr=/192.168.0.122,port=57316,localport=9999]> Exception occurred while responding to client: java.lang.IllegalMonitorStateException
> 
> That could well be it, but I have no idea why you would be getting that exception.

>> Mar 06 17:58:06 MPMall[9999] ERROR er.extensions.eof.ERXEC  - Should pop, but ec not found in Vector! WorkerThread15, ec: er.extensions.eof.ERXEC@1ee29820, ecs:[]
> 
> I have no advice on that one either.

The above two error messages went away with er.extensions.ERXEC.safeLocking=false

Thanks
John

> 
> Chuck

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.