Maik,

It is not really a global static dictionary, it is stored in thread storage so 
no concurrency problem...

This does not help you much though.

I would try to catch the exception to add log context information like the 
current request of page being rendered.

Samuel

> Le 30 mars 2016 à 07:56, Maik Musall <[email protected]> a écrit :
> 
> Hi all,
> 
> I’ve been getting these a lot lately:
> 
> java.lang.IllegalStateException: You attempted to use an ERXElse without a 
> preceding conditional.
>        at 
> er.extensions.components.conditionals.ERXElse.lastConditionChecked(ERXElse.java:29)
>        at 
> er.extensions.components.conditionals.ERXElse.appendToResponse(ERXElse.java:54)
>        at 
> com.webobjects.appserver._private.WODynamicGroup.appendChildrenToResponse(WODynamicGroup.java:126)
>        at 
> com.webobjects.appserver._private.WODynamicGroup.appendToResponse(WODynamicGroup.java:136)
>        at 
> com.webobjects.appserver.WOComponent.appendToResponse(WOComponent.java:1122)
> 
> Of course the wo:if-wo:else tags are correct. Turns out ERXElse holds the 
> lastCondition state in a static (!) dictionary. How is this even supposed to 
> work with high concurrency?
> 
> In my case, I’m rendering HTML in background threads to be delivered on the 
> next Ajax poll, which seems to interfere with foreground worker threads.
> 
> Any thoughts on this?
> 
> Thanks
> Maik
> 
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> https://lists.apple.com/mailman/options/webobjects-dev/samuel%40samkar.com
> 
> This email sent to [email protected]


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to