Addional libraries with JavaPlugin 1.2.2
Hello, I copied addional libraries (jndi.jar, rmiregistry.jar, providerutil.jar) to the $HOME/.netscape/java/lib/ext directory, but the plugin doesn't find them. What goes wrong? Thanks, Lars. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anyone using blackdown jdk on SMP linux?
> "Scott" == Scott Murray <[EMAIL PROTECTED]> writes: > Scott Murray wrote: >> >> Michael Thome wrote: >> > >> > > "Scott" == Scott Murray <[EMAIL PROTECTED]> writes: >> > >> > > Michael Thome wrote: >> > >> >> > >> > "Calvin" == Calvin Austin <[EMAIL PROTECTED]> writes: >> > >> >> > >> > Submit it as a bug and/or send us the short example, it could very well be >> > >> > another linuxthreads bug that we will have to work around or someone has >> > >> > already discovered. >> > >> >> > >> Ok - I've submitted it as a bug both to the bug parade and to >> > >> blackdown's jitterbug. >> > >> >> > >> For your reading pleasure, enclosed below is the current version of my >> > >> test case. It is pretty easy to cut it down to smaller examples, >> > >> especially if you are just looking for the Exception cases. All that >> > >> appears to be required is tight-loop lock contention with wait/notify >> > >> involved running on a native-threaded VM on an SMP machine (phew!). >> > >> > > Actually, I don't see any problems running the "Bang" example under >> > > either 1.2.2-RC4 or Sun's beta 1.3 on my dual PIII-450 with RedHat 6.2. >> > > It just keeps running until I kill it. >> > >> > Cool. What kernel+glibc are you running with? standard RedHat 6.2? >> > Must be my kernel... >> >> Just the standard 2.2.12-20 kernel from RH 6.2. I may give it a whirl on >> a 2.4.0-test2-preX kernel at home on the weekend. > Oops. I'm also using the stock RH 6.2 glibc-2.1.3-15 package. Just wanted to follow up on this... The scientific method led me to discover that the culprit was the rawhide glibc-2.1.3-16 I'd installed - going back to the stock RH 6.2 glibc seems to be working just fine. Next step, back to the 2.3/2.4-test kernels... Thanks much, -mik -- Michael Thome ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anyone using blackdown jdk on SMP linux?
Avi Cherry wrote: > > > > We're considering buying a dual processor machine to run our java > > > > programs but if we can't get something running with a jdk on an smp > > > > kernel there probably won't be much point. > > I've actually been running the Blackdown JDK 1.2.2RC4, with the JIT > on a 2.2.14 SMP 2-CPU box for several months now without having any > of these sorts of problems. I suggest that it's probably a issue > with your configuration, rather than a bug in the JVM(s). > > You mentioned you were running 2.2.12? Try updating to 2.2.14. Also > try updating to the latest glibc, since that has the pthreads code in > it. That was me that mentioned jitc problems on a 2.2.12 configuration (using Blackdown JDK 1.2.2 RC4). Based on the following I don't think it's a kernel / library configuration problem: I'm actually running a stock Redhat 6.1 kernel on a dual PIII 600 server (2.2.12-20smp). I did weeks of serious testing earlier in the year and had intermittent problems with the sunwjit jitc. At another list member's suggestion I tried running tests on the TYA jitc over the weekend (with good results). My test app does heavy i/o (JMS) and heavy XML parsing and generation, so it's a good mix of CPU and i/o. There are around 20 threads and a few heavily contended locks (so it has 'Bang'-like characteristics, but with a server-app-like profile). I ran for 42 hours continously at heavy loads using the TYA jit without any problems (the test was manually terminated). I then ran the identical configuration with sunwjit and got @ 5 hours at the same load before the server JVM terminated abruptly. On a retry it terminated within seconds. This is consistent with behavior from many previous test runs. I switched the jitc back to TYA and it's still running without a hitch. (On my tests TYA is marginally faster than sunwjit as well). In the past I've tested Borland's javacomp, but was unable to get it run on a native threads SMP configuration for more than a few seconds (though, being fair to Borland, that is not a supported / designed for configuration). I'm delighted with what I've seen of TYA so far. I've got a serious internal testing cycle coming up later next month and will add TYA to the tested configurations. I have not done any JDK 1.3 / Hotspot testing, but am nervous about the beta readme statement: "Sun does support or recommend running the Java 2 SDK on SMP kernels." Should that be "does support _and_ recommend" or "does _not_ support or recommend"? Has anyone got results from 1.3 testing on SMP yet? -- David Marshall mailto:[EMAIL PROTECTED] VM Systems, Inc. http://www.vmguys.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Addional libraries with JavaPlugin 1.2.2
> "Lars" == Lars Lathan <[EMAIL PROTECTED]> writes: Lars> I copied addional libraries (jndi.jar, rmiregistry.jar, Lars> providerutil.jar) to the $HOME/.netscape/java/lib/ext Lars> directory, but the plugin doesn't find them. What goes Lars> wrong? That's a bug in 1.2.2 version of the plugin on Linux and Solaris: It doesn't find jars in the java/lib/ext directory. The work-around is to put the files into java/lib. Juergen -- Juergen Kreileder, Blackdown Java-Linux Team http://www.blackdown.org/java-linux.html JVM'01: http://www.usenix.org/events/jvm01/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Anyone using blackdown jdk on SMP linux?
We've experienced the `java.lang.IllegalMonitorStateException: current thread not owner' exception after we run some of our test programs through Soot, our Java bytecode analysis framework. Strangely enough, the exception does not occur on the original copies of the programs, only after we Sootify. At first, I thought this was a problem with Soot, but the error seems to be the same one people are encountering without Sootifying their files. We are running Debian potato on 2.2.8 kernels, Blackdown's JDK1.2.2, with native threads, on dual-processor PII systems. pat -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
JSlider
I have writen a gui which uses JSlider. The code works fine on windows 98/NT and Solaris but not on Linux. When JSlider is moved, its supposed to do a repaint, but on Linux that does'nt happen. Is there a bug in JDK1.2RC4? Thanks, Nash'at -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: jdk1.2.2 on SMP
After about two years of turmoil in the Java, kernel, and glibc worlds, we *finally* appear to have our stuff working with native threads on SMP. The winning combination is blackdown 1.2.2RC4 redhat 6.2 glibc-2.1.3 <--- **VERY** important It absolutely doesn't work on redhat 6.1. We're talking seg faults. I don't know what it is that makes our use of Java special, but I am more than a little suspicious of anyone who says SMP and native threads work fine on their RH6.1 system. Mandrake 7.1 is also glibc-2.1.3, will be trying that soon. I've never tried the SUN jdk1.2 for linux. Principles and versioning aside, they explicitly do not support native threads on SMP. Many thanks to the Blackdown team for persevering in such a tumultuous climate with such a complex system. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
C# -- the Java killer?
Microsoft has released a preliminary version of the C# ("C Sharp") language
reference. It's at:
http://msdn.microsoft.com/vstudio/nextgen/technology/csharpintro.asp
The language reference is a .exe file but can be unpacked using 'unzip'
under Linux. The MS Word .doc file inside can be read by StarOffice - no
Microsoft products required :-)
C# is VERY similar to Java. Here's my summary of some of its interesting
features (as they differ from Java):
* The language is definitely targeted at static compilation and invoking
dynamically loaded classes must be done through a DLL mechanism --
there's no dynamic class loading as in Java.
* Cross-platform portability does not appear to be a goal.
* Interestingly, C# does *not* have its own runtime library - instead
they intend to bind everything to Win32 and COM libraries it seems
(or perhaps to the ".NET" runtime we have heard a bit about).
* Memory is garbage collected, but some code segments can "fix" memory
so it can't be moved by the GC, allowing you to use pointers on it.
Such code must be tagged with the "unsafe" keyword.
* Events are built into the language -- although this appears mainly to
be syntactic sugar. A class can declare fields with the keyword "event"
which means they represent event handlers. Using the "+=" and "-="
operators you can add or remove function pointers from the list of
event handlers associated with that class instance. It's not clear what
happens when an event handler is invoked.
* Versioning is part of the language - albeit in a primitive form. If
a new version of a base class declares a method which conflicts with
an old version of a subclass's method, then when the subclass is
recompiled the author must explicitly state whether the method
overrides or hides the base method.
* It uses 'cpp' style preprocessing
* Multidimensional arrays are supported
* Type-checking can be disabled for code blocks by labelling that block
with the 'unchecked' keyword
* Operator overloading is supported
* Supports Java-style exceptions with try ... catch ... finally
* Thread synchronization is supported with the 'lock' keyword (similar
to Java's 'synchronized')
* Supports single-inheritance and interfaces (just like Java)
* Virtual methods are supported but you have to use the 'virtual' and
'override' keywords - a bit ugly. Otherwise methods are treated as
non-virtual. My guess is that they are trying to avoid the problem
that Java has with nearly everything being a virtual method, and the
resulting performance issues. However, a static C# compiler should be
able to devirtualize everything since there's no dynamic class loading.
* 'struct' and 'enum' are supported (they seem unnecessary since 'class'
and 'interface' can be used)
* Special keywords allowing direct bindings to COM are supplied
Overall it's a nice language -- some of the syntax might be a bit
superfluous but otherwise no major problems with it. The language spec
is very preliminary and leaves out a lot of details, such as what threads
and locks actually do, what the memory model is, etc. As we all learned
from Java, these seemingly minor details end up being very important down
the line...
Matt Welsh, [EMAIL PROTECTED]
http://www.cs.berkeley.edu/~mdw
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
JavaPlugin and https
Hi, I'm new in this mailing list and don't know much about Java. My problem is that I need to access to a secure web page wich needs the JavaPlugin. But when I try to acces it, the hole Netscape crashes!!! The plugin_stack.trace file says https is not supported. I'm using the JavaPlugin1.2.2, Redhat 6.2, and Netscape 4.72. Is the https protocol really not supported by the JavaPlugin? Or do I have to do something special?? If it's not supported,... when will it be supported?? Thank you very much,... -- ... y recuerda: "TITO JAIME SIEMPRE TIENE LA RAZON"
