[Wonder-disc] WOOGNL expression crashes java?

[Timo H. <th...@on...>]

Hi,

I just had a strange experience. We're using WOOGNL in our projects  
and just as a co-worker introduced a new conditional using ognl, the  
jvm on one of our xserves started to crash. We drilled it down to one  
ognl expression. When removed, everything works OK again.

The server is still running Panther server with WO 5.2.3. A different  
xserve running Tiger with wo 5.2.4 doesn't expose this problem.

Here's the expression we were using on a woconditional :

condition = "~component.componentDefinition.isCroppingAllowed && (! 
component.componentDefinition.isCroppingServiceOnly ||  
(session.user.can.service &&  
component.componentDefinition.isCroppingServiceOnly))";

and here's the crash dump of the jvm:

Date/Time:      2007-02-23 17:12:23 +0100
OS Version:     10.3.9 (Build 7W98)
Report Version: 2

Command: java
Path:    /usr/bin/java
Version: ??? (???)
PID:     6268
Thread:  0

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000008

Thread 0 Crashed:
0   <<00000000>>        0xffff8264 __spin_lock + 0x4
1   com.apple.CoreFoundation    0x902312f4  
CFMessagePortCreateRunLoopSource + 0x48
2   com.apple.AppKit            0x983bc8e4 -[NSApplication  
_createWakeupPort] + 0xc0
3   com.apple.AppKit            0x9832cb1c -[NSApplication init] + 0x304
4   libawt.jnilib               0x8108c0b8 -[NSApplicationAWT init] +  
0x38
5   com.apple.AppKit            0x98350424 +[NSApplication  
sharedApplication] + 0xac
6   libawt.jnilib               0x8108bbec +[AWTStarter startAWT:] +  
0x80
7   com.apple.Foundation        0x90a4b0a0 __NSFireMainThreadPerform  
+ 0x108
8   com.apple.CoreFoundation    0x902151b0 __CFRunLoopPerformPerform  
+ 0x88
9   com.apple.CoreFoundation    0x901c4800 __CFRunLoopDoSources0 + 0x1fc
10  com.apple.CoreFoundation    0x901c20b8 __CFRunLoopRun + 0x1b0
11  com.apple.CoreFoundation    0x901c69e4 CFRunLoopRunSpecific + 0x148
12  java                        0x00006698 0x1000 + 0x5698
13  java                        0x00003d10 0x1000 + 0x2d10
14  java                        0x00003b84 0x1000 + 0x2b84
...


java version "1.4.2_09"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_09-233)
Java HotSpot(TM) Client VM (build 1.4.2-56, mixed mode)


We have a workaround now, but it's nevertheless strange. Anyone  
having an idea what's going on here?

And no, we don't use any AWT stuff in the whole project.

Timo