Is Java/Tomcat on FBSD practical?

Heath Volmer hvolmer at
Thu Nov 6 05:46:24 PST 2003

Thanks for the replies.  

I ran Tomcat as root (or other users, doesn't matter).  What happens
means absolutely nothing to me.

I get on screen: lefty /kernel: pid 22239 (java), uid 0: exited on
signal 6 (core dumped)

This is what I get in Catalina.out:

SIGABRT   6*   abort (generated by abort(3) routine)

Full thread dump Classic VM (diablo-1.3.1-0, green threads):
    "Finalizer" (TID:0x28e9d528, sys_thread_t:0x80d6080, state:CW)
        at java.lang.Object.wait(Native Method)
        at java.lang.ref.ReferenceQueue.remove(
        at java.lang.ref.ReferenceQueue.remove(
    "Reference Handler" (TID:0x28e9d300, sys_thread_t:0x8096480,
state:CW) prio=10
        at java.lang.Object.wait(Native Method)
        at java.lang.Object.wait(
    "Signal dispatcher" (TID:0x28e9d330, sys_thread_t:0x8096280,
state:CW) prio=5
    "main" (TID:0x28e9d1b0, sys_thread_t:0x8054080, state:R) prio=5
        at java.lang.Long.toString(
        at java.lang.String.valueOf(
        at java.lang.StringBuffer.append(
        at org.apache.catalina.startup.Catalina.load(
        at org.apache.catalina.startup.Catalina.load(
        at java.lang.reflect.Method.invoke(Native Method)
Monitor Cache Dump:
    java.lang.ref.Reference$Lock at 28E9D310/28ED2F98: <unowned>
        Waiting to be notified:
            "Reference Handler" (0x8096480)
    java.lang.ref.ReferenceQueue$Lock at 28E9D540/28ED3478: <unowned>
        Waiting to be notified:
            "Finalizer" (0x80d6080)
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" (0x8054080) 1 entry
    Dynamic loading lock: <unowned>
    Monitor IO lock: <unowned>
    User signal monitor: <unowned>
        Waiting to be notified:
            "Signal dispatcher" (0x8096280)
    Child death monitor: <unowned>
    I/O monitor: <unowned>
    Alarm monitor: <unowned>
        Waiting to be notified:
            <unknown thread> (0x8054280)
    Thread queue lock: owner "main" (0x8054080) 1 entry
    Monitor registry: owner "main" (0x8054080) 1 entry

-----Original Message-----
From: Dirk-Willem van Gulik [mailto:dirkx at] 
Sent: Wednesday, November 05, 2003 2:03 AM
To: Heath Volmer
Cc: freebsd-questions at
Subject: Re: Is Java/Tomcat on FBSD practical?

> My biggest problem has been Java.  I've done the diablo 1.3 package 
> and java seemed to work (java -v), but when I install Tomcat it won't 
> start. I've done the same install on mac and windows with no problem.

> The stack trace is completely alien to me and I can try to get it if 
> it would help.

If the stacktrace looks like it is some VM issue - posting it here may
help - otherwise the tomcat folks may be a better bet.

One quick test - try running it as root and see if that changes anything
- some JDK version had that problem - which since is fixed if I recall

> I'm basically wondering if running Tomcat or any other java on this 
> machine is realistic or not.

We are using it with no great issue (other than that java can be quite
memory hungry :-)


More information about the freebsd-questions mailing list