On Mon, Aug 06, 2001 at 11:59:04AM -0700, Wilhelm Fitzpatrick wrote:
> This message indicates java cannot grow its heap any larger. This may be
> do to an actual inability to allocate memory, or more likely, the heap has
> grown to the maximum allowed size, which, with the 1.3.0 blackdown VM is
> 64MB. You can add override this using the -Xmx parameter to java by doing
> something like the following:
>
> java -Xmx128mb com.my.class.Main
ok, but now I have the following problem (I use the jdk 1.3.0 from
blackdown and woody with kernel 2.2.18pre21):
SIGSEGV 11* segmentation violation
si_signo [11]: SIGSEGV 11* segmentation violation
si_errno [0]: Erfolg
si_code [0]: SI_USER [pid: 0, uid: 0]
stackpointer=0x7fffc2bc
Full thread dump Classic VM (Blackdown-1.3.0-FCS, native threads):
"Log time updater" (TID:0x319941a8, sys_thread_t:0x101e4a80, state:CW,
native ID:0x1005) prio=5
at java.lang.Thread.sleep(Native Method)
at org.jboss.logging.Logger.run(Logger.java:139)
at java.lang.Thread.run(Thread.java:484)
"Finalizer" (TID:0x3198e528, sys_thread_t:0x1005f9d8, state:CW, native
ID:0xc04) prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:108)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:123)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:162)
"Reference Handler" (TID:0x3198e300, sys_thread_t:0x100598c8, state:CW,
native ID:0x803) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:420)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:110)
"Signal Dispatcher" (TID:0x3198e330, sys_thread_t:0x10055ed8, state:CW,
native ID:0x402) prio=5
"main" (TID:0x3198e1a0, sys_thread_t:0x1001b420, state:R, native ID:0x400)
prio=5
at java.lang.reflect.Method.copy(Method.java:280)
at java.lang.reflect.Method.getParameterTypes(Method.java:90)
at com.sun.management.jmx.MetaData.findMethod(MetaData.java:277)
at com.sun.management.jmx.MetaData.findSetter(MetaData.java:229)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1375)
at
com.sun.management.jmx.MBeanServerImpl.setAttribute(MBeanServerImpl.java:1331)
at
org.jboss.configuration.ConfigurationService.load(ConfigurationService.java:132)
at
org.jboss.configuration.ConfigurationService.loadConfiguration(ConfigurationService.java:295)
at java.lang.reflect.Method.invoke(Native Method)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1628)
at
com.sun.management.jmx.MBeanServerImpl.invoke(MBeanServerImpl.java:1523)
at org.jboss.Main.<init>(Main.java:209)
at org.jboss.Main$1.run(Main.java:121)
at java.security.AccessController.doPrivileged(Native Method)
at org.jboss.Main.main(Main.java:117)
Monitor Cache Dump:
[EMAIL PROTECTED]/319C3F10: <unowned>
Waiting to be notified:
"Reference Handler" (0x100598c8)
[EMAIL PROTECTED]/319C4320: <unowned>
Waiting to be notified:
"Finalizer" (0x1005f9d8)
Registered Monitor Dump:
utf8 hash table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class linking lock: <unowned>
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Monitor cache lock: owner "main" (0x1001b420) 1 entry
Thread queue lock: owner "main" (0x1001b420) 1 entry
Monitor registry: owner "main" (0x1001b420) 1 entry
How can I solve this problem? I don't want to use
kernel 2.4.x because I get some problems with my cdrom and my network
adapter (on a powerbook g3 pismo).
thank you Stefan
