We've seen JVM lockups during high contention Threading operations with
the jdk15 port. The same code succeeded when running under diablo-jdk.
I have precious little information on the details of the failure we saw
so I'm hesitant to toss the jdk15 port squarely under the bus without
more poking at the issue, but time just isn't on my side lately. :)
Perhaps this will jog the memories of others who can elaborate.
Juergen Nickelsen wrote:
Stefan Walter <[EMAIL PROTECTED]> writes:
It might be easier for you to just use the java/diablo-jdk15 port, which
installs precompiled binaries.
Although I have, with the much appreciated help from people here,
successfully installed the jdk15 port in between, I thought about
diablo-jdk15, too. Would there be any difference between both ports
in terms of compatibility, features, and performance from the
viewpoint of the Java developer and user?
--
Sam Baskinger
Software Engineer
Lumeta - Securing the Network in the Face of Change
www.lumeta.com
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
