Hi Alexei,
Thanks for the information. Are you both building <and> running tests with JRockit? Or are you building w/ Sun and only running tests under JRockit? Would be good to isolate the two. Good chance, however, that it won't make any difference... 

Geronimo currently has direct ties to the Sun 1.4 corba implementation. That's the only JRE restriction that I'm aware of. People have run Geronimo on Sun 1.5 and also on IBM's 1.4 JRE. 

It seems that the tests you describe <ought> to work. There's a reasonable chance that these are Geronimo bugs that are masked by our current runtime. So, it would be great if you could help us uncover the causes of these failures.

I don't know why JRockit 1.5 would be worse. 

--kevan 

On Mar 17, 2006, at 12:21 PM, Alexei Zakharov wrote:

Hi, community!

I experiment with running Geronimo on various JVM's. The interesting thing I've encountered is that some of unit tests fail on BEA Jrockit VM. I've got at least three failures unique to BEA Jrockit 1.4.2_04 VM:

Module: modules/directory
Test: org.apache.geronimo.directory.RunningTest
Result: VM hangs

Module: modules/timer
Test: org.apache.geronimo.timer.NontransactionalThreadPooledTimerTest.testTasksInUnspecifiedTxContext
Output: expected:<20> but was:<19>

Module: modules/tomcat
Test: org.apache.geronimo.tomcat.JAASSecurityTest.testNotAuthorized
Output: expected:<<!-- Login Page -->> but was:<null>

These tests pass on all Sun VMs. Situation with Jrockit 1.5 is much worse - more than 60 failures. It may result in overall instability while running Geronimo on BEA.
Any comments & suggestions?

Alexei Zakharov,
Intel Middleware Product Division


Reply via email to