Re: JDK 1.1.8 ??
[RE:] Kelly Campbell wrote: I'd like to chime-in that I really appreciate the work done by the Java Blackdown Team, and am anxiously awaiting the release version of 1.2. Specifically the CORBA IDL stuff. Keep up the great work!!! James Caple Riverbed Technologies > Hi, > > I was just wondering if the jdk team is planning to release a 1.1.8 > version of the JDK now that the reference release is out, or is the port > effort mainly going towards 1.2 now? > > JDK 1.2 is just too bloated for us to use in any kind of production > environment. (I'm basing that decision off the Solaris version, not the > 1.2 pre 1 release for linux. Most applications I've test have taken 3x the > memory and the speed increase is not worth that.) We've been seeing a > few minor problems in jdk1.1.6 and 1.1.7 for linux x86 that can hopefully > be corrected in 1.1.8. > > thanks, > Kelly > -- > Kelly A. Campbell Applications Programmer/Analyst > <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Kansas State University > http://www.telecom.ksu.edu/~camk/ Department of Telecommunications > 109 East Stadium, Manhattan KS 66506http://www.telecom.ksu.edu/ > Voice: (785) 532-7067 Fax: (785) 532-7114 > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: JDK 1.2 and CORBA problem on hello example
Dear Daniele, Did you get any answers on your CORBA problem? I too am experiencing the same anomaly. I'm using RedHat 5.2 Linux with JDK117_v1a, with Orbacus 3.1.2. I get your error when I run the Client on a WindowsNT box, with the HelloWorld Server running on my Linux box. When the client and server are swapped, however, everything's cool. James BTW, I'm running the Hello example provided in the Orbacus 3.1.2 documentation, Java example. Daniele Sacchetti Matr.1783 wrote: > I have installed jdk1.2 version pre-v1 for i386 on my Redhat 5.2 linux > distribution. > > The simple hello world example of the java tutorial at the address: > http://www.javasoft.com/docs/books/tutorial/idl/hello/index.html > > gives me an error when i execute the server and the client on two > different machines. > When i execute either server or client on the same machine everything is > ok. > > My two hosts are host1 and host2; when i execute: > on host1: >host1# tnameserv & >host1# java HelloServer > and on host2: >host2# java HelloClient -ORBInitialHost host1 > > on host2 i get the error: > > ERROR : org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: No > org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: No > at com.sun.CORBA.iiop.ConnectionTable.get(Compiled Code) > at com.sun.CORBA.iiop.GIOPImpl.createRequest(GIOPImpl.java:78) > at com.sun.CORBA.iiop.GIOPImpl.createRequest(GIOPImpl.java:62) > at com.sun.CORBA.idl.GenericCORBAClientSC.createRequest > (GenericCORBAClientSC.java:138) > at com.sun.CORBA.idl.RequestImpl.doInvocation(Compiled Code) > at com.sun.CORBA.idl.RequestImpl.invoke(RequestImpl.java:219) > at org.omg.CosNaming._NamingContextStub.resolve > (_NamingContextStub.java:160) > at HelloClient.main(HelloClient.java:23) > > I get the same error if i use the stringified client/server version, using > the IOR string corresponding to the object on the server, that is: > > host1# java HelloStringifiedServer > > after having copied the IOR identifier on host2, i execute: > > host2# java HelloStringifiedClient > > and i get the same error. > > I have tried with the server on a windows machine with jdk1.2 and the > client on a linux machine and in this case everything is ok. > > I would like to know if i must use any options for java interpreter or > compiler (i have read the README.linux file and i have tried the options > suggested for the interpreter and the compiler), or if i must configure > jdk1.2 in a different way. > > Thanks in advance, > Daniele > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Big-Endians
What's up? Can someone help me clarify the following: Java is Big-Endian, correct? Intel Linux is Little-Endian, correct? Thanks, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RMI Activatable Object
Greetings, Was wondering if any other Linux/Java developers have run into problems when developing RMI Objects. I have a Runnable, Activatable Object, which has been subclassed from an Activatable RMI Server Object. When instantiated, the RMI Server Object starts a thread and suspends it until one of it's methods is called from a remote client, at which time the thread is resumed. Under Solaris 7, my code works fine. Under Linux, however, the RMI Server Object's method is never gotten into; It's as if the suspended thread blocks the object from all outside methods call. I've started both client and server using -green and turned off the JIT setting my JAVA_COMPILER=NONE environment variable. RedHat Linux 6.0 glib2.1 jck1.2 rel2 This appears to be a Java-on-linux bug. Thanks, James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RMI Activatable Object (solved)
Appreciate the help. I was able to get things working, for the most part, by setting the following environment variables: THREADS_FLAG=GREEN JAVA_COMPILER=NONE I am, in fact, using native threads under Solaris. Thanks, James Cees de Groot wrote: > [EMAIL PROTECTED] wrote: > >Under Solaris 7, my code works fine. Under Linux, however, the RMI > >Server Object's method is never gotten into; It's as if the suspended > >thread blocks the object from all outside methods call. > > > >I've started both client and server using -green and turned off the JIT > >setting my JAVA_COMPILER=NONE environment variable. > > > Have you been using green threads on Solaris as well? The RMI daemon > doesn't take any explicit arguments so I guess you have to do this with > environment variables. As far as I understood it, the RMI daemon does not > spawn new threads but rather whole new VM processes per activation group > and you want to make absolutely sure that all VM's involved run green > threads in order to eliminate programmer error. > > I have Jini running onder Blackdown pre-v2 via RMI activation so it > seems to be basically working. I did have some problems on my SMP box, > but on my laptop with native threads things seem to be OK (at least, > 'ps' indicates some 107 Java procs polluting process table space ;-)). > > -- > Cees de Groot http://www.cdegroot.com <[EMAIL PROTECTED]> > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which Linux JVM is better?
For what it's worth, my experience has been that the Blackdown RC3 port is much more scaleable and stable than the Inprise Linux port. I'd place my bets on the Blackdown port for server-side performance and scaleability. Although somewhat slow in porting, Blackdown is doing a very thorough job. My comments are based on tests using green threads without a JIT, at the moment. JC Andreas Rueckert wrote: > Hi! > > On Son, 09 Jan 2000 Nathan Meyers wrote: > > > > >Depends what you want to do. If you want to use native threads, you > >need the Blackdown JDK. If you want to use tools that depend on the > >Java Platform Debugging Architecture (like JBuilder and other IDEs), > >you need the Sun/Inprise JDK. > > How stable are the Blackdown RC3 native threads? Has anyone managed to run > LotusXSL, XP/XT with native threads? I had to use green threads here. > > Ciao, > Andreas > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Which Linux JVM is better?
After a little more server-side testing I've discovered the following to be true: -- (RedHat Linux 6.1, with kernel modified to up the number of file descriptors and per-user thread limits, 300MHz machine, 256MB RAM) -- Inprise JVM 1.2.2 for Linux vs. Blackdown JVM 1.2.2 RC3 -- green threads vs. native Preface: Tests involved hitting our Java server application, which utilizes JDBC to talk to a MySQL database on a separate box, with as many simultaneous tcp/ip connection requests as possible using Segue's Silk Performer load testing tool. In sum: * The Inprise Java-Linux port could not handle nearly as many simultaneous server-side connections as the Blackdown port when using green threads. * Using native threads, however, the Inprise port wins hands down. This, of course, is to be expected as the Blackdown porters have not finished testing and fixing their native threads port yet. Using Inprise's native threads, our application was able to handle many more simultaneous connections than we could with the Blackdown green threads port. It would seem that if we linux/java users could somehow combine the efforts of both camps (Sun/Inprise and Blackdown), we would have a pretty well-rounded JVM right now, since the Inprise port is doing really well with native threads, and the Blackdown guys have done a good job with green threads. One question I have of Blackdown is why they have prioritized their green threads porting efforts over native threads, when native threads offer the best overall server-side performance (if I'm not mistaken in my assumptions)? I think more and more people are using Java for server-side development, as opposed to client-side, especially on Linux - again, if I'm not mistaken. Thanks, James P.S. These ideas, informations and opinions are my own and do not necessarily express the ideas and opinions of my employer. Mike Christiansen wrote: James Caple wrote: > > For what it's worth, my experience has been that the Blackdown RC3 port is > much more scaleable and stable than the Inprise Linux port. I'd place my > bets on the Blackdown port for server-side performance and scaleability. > Although somewhat slow in porting, Blackdown is doing a very thorough job. As much as I hate to say it, my money is on Imprise. I am finding that Blackdown's VM is causing JRun to hang. This may be a problem with native threads, or with the fact that I am running on a two processor SMP configuration. However, switching to Inmprise / green threads did the trick. Mike > > My comments are based on tests using green threads without a JIT, at the > moment. > > JC
