harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Dmitriev (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-5251) [drlvm][kernel] H4965 causes jboss/SPECjAppServer2004 failure
Date Tue, 04 Dec 2007 19:09:43 GMT
[drlvm][kernel] H4965 causes jboss/SPECjAppServer2004 failure
-------------------------------------------------------------

                 Key: HARMONY-5251
                 URL: https://issues.apache.org/jira/browse/HARMONY-5251
             Project: Harmony
          Issue Type: Bug
          Components: DRLVM
         Environment: linux32
win32
            Reporter: Sergey Dmitriev


Recently it's been discovered that
H4965 "[drlvm][kernel] ClassLoader.findLoadedClass() does not cache not owned classes" and
H5218 "[drlvm][kernel] null may be passed to registerInitiatedClass if class loader does not
throw ClassNotFoundException for missing classes"
patches cause the JBoss/SPECjAppServer2004 failure. Meaning the VM crash.

Internal error:/localdisk/harmony.3dec/working_vm/vm/vmcore/include/hashtable.h:269: Element
was inserted second time in MapEx!SIGABRT in $
Stack trace:
  0: ?? (??:-1)
addr2line: '/mnt/huge/vm_heap': No such file
  1: ?? (`F+_F+D=@:-1)
addr2line: '/mnt/huge/vm_heap': No such file
  2: ?? (`F+_F+D=@:-1)
addr2line: '/mnt/huge/vm_heap': No such file
  3: ?? (`F+_F+D=@:-1)
addr2line: '/mnt/huge/vm_heap': No such file
  4: ?? (`F+_F+D=@:-1)
addr2line: '/mnt/huge/vm_heap': No such file
  5: ?? (`F+_F+D=@:-1)
  6: ?? (??:-1)
  7: ?? (??:-1)
  8: java/lang/ClassLoader.registerInitiatedClass(Ljava/lang/Class;)V (ClassLoader.java:-2)
  . . .

Full logs are attached.

This is definetely about these patches: I've tried fresh (3 DEC) Harmony without the patches
- JBoss works just fine.

Please be informed that there is another guilty commit H5090 "OSR" which play a role here.
So when I say "Harmony without H4965 & H5218 works just fine" this means "with rolled
back H5090 as well". I've checked this two cases separately. Just the first thing that causes
JBoss to fail is these patches; later - having these patches rolled back - JBoss fails because
of OSR patch. So please note this: you can just disable the osr_path in server.emconf.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message