Very Computer

So I thought I was flying high actually getting this all to work, and
for the most part it does, but for some reason the
linux-jdk13(1.3.0-1.3.1) core dumps every time I run a speficic jsp.  Is
the linux-jdk13 really buggy or is this just me.  I have the problem on
both my servers.  On one where I am just running tomcat I can run it in
classic mode and have no problems.  My personal server though I am
experimenting with JBoss, which seems to have something against the
classic vm.  In classic it only loads up halfway and stops, but that is
for the jboss list.  When I use the hotspot (client and server) in both
int and mixed modes it catches an abort trap and core dumps everytime I
run the tomcat example jsp 'ErrorPage'.  It will core dump on almost all
the others too eventually but the 'ErrorPage' example does it every
time.  I have tried all sorts of combinations with the linux-jdk13 with
no luck.  I am reinstalling my linux-base right now in hopes that that
will fix it.  Are there any known issues with the linux-jdk13?  By they
way I am running FreeBSD-4.3-STABLE (5/20/2001).  My last resort is to
udate to the latest stable.

So on the port front I have started on two for JBoss.  The first on I
have started on is the more complicated one, jboss-current.  Rather than
downloading a release build this checks out the latest source from the
CVS archive.  I added an 'update' target on it that retrieves the latest
changes and clears the '.build_done' and '.install_done' flags.  I am
trying to get it to auto build and install the optional modules and
contrib modules too by defining WITH_X flags.  Right now I have
'WITH_JBOSSCX' for those (me) who need the latest release of the Java
Connector Architecture support.  I am also working on 'WIHT_TOMCAT' to
automate the embeded tomcat support.  I have been trying to use this one
myself to keep up the latest changes and debug it.  The next on I will
work on, and probably finish first, will be a normal port that just
installes the latest release binaries.  So does it sound like I am on
the right track?  Is there anything in particular anyone would like to
see in the ports?  I notice the post about a how-two on JVM dependency,
that would be nice to know how to do.  JBoss needs a Java2 vm so it
would be nice to say something like 'DEPENDS_JAVA=1.2+' to let the ports
engine know that this package depends on Java an more specifically 1.2
or greater.

-Jake

with "unsubscribe freebsd-java" in the body of the message

<SNIP>

Quote:

> Are there any known issues with the linux-jdk13?

Yes; using the HotSpot VM is, in my experience and that of others, a no-no. As I vaguely recall, there are problems with signal
handling in the Linux compatibility layer (don't quote me on that explanation though!). Searching the archive for this list will
give more info. But, as you already know, Classic works fine with Tomcat.

with "unsubscribe freebsd-java" in the body of the message