I nuked the included SuSE 8.1/United 1.0 that came on my appro box to try Fedora RC1 because I couldn't get a usable jdk/jvm to run tomcat on. The only improvement so far with Fedora is that I get better error messages (I think).
I tried the blackdown rc1 for amd64 and after a few seconds of running my app, I get the attached error. On SuSE, the jvm process just silently exits in roughly the same amount of time.
I can't seem to install a 32-bit jdk because I keep getting errors like the following from the self-extracting executables:
/root/j2sdk-1_4_2_03-linux-i586.bin: ./install.sfx.16985: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
Is there a decent jdk for Fedora RC1 amd64? Or is there a way to make one of the ones I've already tried actually work?
Thanks, Barry Roberts
Barry Roberts wrote:
/root/j2sdk-1_4_2_03-linux-i586.bin: ./install.sfx.16985: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
The error message says it clearly: you don't have the 32-bit userland libraries installed. They should be somewhere in the place you get the rest of the RPMs from.
Barry Roberts wrote:
I tried the blackdown rc1 for amd64 and after a few seconds of running my app, I get the attached error. On SuSE, the jvm process just silently exits in roughly the same amount of time.
This is the wrong list. You should post the JVM/Hotspot error to the java-linux list somewhere on Blackdown.org. It might be a good idea not to use ZIP format.
/root/j2sdk-1_4_2_03-linux-i586.bin: ./install.sfx.16985: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
The 32 bit jdk should, in theory, work on Fedora but you will need to install the i686 glibc rpm's. If you selected mozilla during installation, the 32-bit libraries should be present, otherwise you can get them from the distribution or the external updates respository that has been discussed here recently.
On Fri, 2004-01-30 at 14:40, Nathan Bryant wrote:
Barry Roberts wrote:
I tried the blackdown rc1 for amd64 and after a few seconds of running my app, I get the attached error. On SuSE, the jvm process just silently exits in roughly the same amount of time.
This is the wrong list. You should post the JVM/Hotspot error to the java-linux list somewhere on Blackdown.org. It might be a good idea not to use ZIP format.
/root/j2sdk-1_4_2_03-linux-i586.bin: ./install.sfx.16985: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory
The 32 bit jdk should, in theory, work on Fedora but you will need to install the i686 glibc rpm's. If you selected mozilla during installation, the 32-bit libraries should be present, otherwise you can get them from the distribution or the external updates respository that has been discussed here recently.
Theory? Of course it works as long as you have the proper libraries. I have JRE-1.4.3 installed and running as a plugin for Mozilla 1.4.5.
regards,
On Fri, Jan 30, 2004 at 04:40:10PM -0500, Nathan Bryant wrote:
This is the wrong list. You should post the JVM/Hotspot error to the java-linux list somewhere on Blackdown.org. It might be a good idea not to use ZIP format.
So far no response on that list, and the plain text was too big for this list.
The 32 bit jdk should, in theory, work on Fedora but you will need to install the i686 glibc rpm's. If you selected mozilla during installation, the 32-bit libraries should be present, otherwise you can get them from the distribution or the external updates respository that has been discussed here recently.
Ok, so much for the theory. I've tried the latest 32-bit jvms from Sun, blackdown.org, and IBM. With the 32-bit glibc and libstdc++, they install, and will run Tomcat. Sometimes. For a few seconds. Then I hit the server a couple of times and get something like the error below.
So if anybody is succesfully using Java, especially tomcat or any servlet container on an x86-64, I would love to hear how it was done (what jvm, distro, etc.), since this is about what I was getting on SuSE 8.1.
Thanks, Barry Roberts
Jan 31 04:15:35 optitwo kernel: Oops: 0010 Jan 31 04:15:35 optitwo kernel: CPU 1 Jan 31 04:15:35 optitwo kernel: Pid: 18527, comm: java Not tainted Jan 31 04:15:35 optitwo kernel: RIP: 0010:[<00000001801c7fce>] Jan 31 04:15:35 optitwo kernel: RSP: 0000:0000010078583e48 EFLAGS: 00010212 Jan 31 04:15:35 optitwo kernel: RAX: 0000000000000000 RBX: 00000000cb5e2d40 RCX: 0000000000000000 Jan 31 04:15:35 optitwo kernel: RDX: 0000000000000000 RSI: 0000010078583f38 RDI: 00000000cb5e2dd0 Jan 31 04:15:35 optitwo kernel: RBP: 0000000000000000 R08: 0000000008052b7c R09: 00000000c8988920 Jan 31 04:15:35 optitwo kernel: R10: 0000000000000000 R11: 00000000c898878c R12: 0000010078583f58 Jan 31 04:15:35 optitwo kernel: R13: 0000010005412728 R14: 000000000000000c R15: 0000010078582a58 Jan 31 04:15:35 optitwo kernel: FS: 0000002a95565060(0000) GS:ffffffff80572880(005b) knlGS:00000000cb5e4bb0 Jan 31 04:15:35 optitwo kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b Jan 31 04:15:35 optitwo kernel: CR2: 00000001801c7fce CR3: 0000000037ffe000 CR4: 00000000000006e0 Jan 31 04:15:35 optitwo kernel: Process java (pid: 18527, stackpage=10078583000) Jan 31 04:15:35 optitwo kernel: Stack: 0000010078583e48 0000000000000000 00000001801c7fce 0000000100000000 Jan 31 04:15:35 optitwo kernel: 0000000000000000 55b37e4400000000 0000000100000000 08052b7c00000000 Jan 31 04:15:35 optitwo kernel: 8013daaa00000000 00000000ffffffff 3b9ab29000000000 c898878c00000000 Jan 31 04:15:35 optitwo kernel: Call Trace: [<ffffffff801101ce>]{do_signal+158} [<ffffffff8013daaa>]{compat_sys_futex+202} Jan 31 04:15:35 optitwo kernel: [<ffffffff8011061b>]{intret_signal+45} Jan 31 04:15:35 optitwo kernel: Jan 31 04:15:35 optitwo kernel: Code: Bad RIP value. Jan 31 04:15:35 optitwo kernel: RIP [<00000001801c7fce>] RSP <0000010078583e48> Jan 31 04:15:35 optitwo kernel: CR2: 00000001801c7fce
I've been running Tomcat on x86-64 using Blackdown 1.4.2 amd64 build all day and it's working fine. I tested a few webapps that are fairly complex.
I also tried Blackdown's 1.4.2 for i386 and it also gave me no problems, although I didn't test that as much.
The one problem I did notice is that JNI fails on the amd64 build if you use 32 bit libraries (have to use 32 bit JVM, but it works fine if you do).
What version of Tomcat are you using? Anything odd about your server.xml config?
PS - it seems to work fine under both SuSE 9.0 and FC1, but most of the testing I've done has been under SuSE.
-ml
Barry Roberts wrote:
On Fri, Jan 30, 2004 at 04:40:10PM -0500, Nathan Bryant wrote:
This is the wrong list. You should post the JVM/Hotspot error to the java-linux list somewhere on Blackdown.org. It might be a good idea not to use ZIP format.
So far no response on that list, and the plain text was too big for this list.
The 32 bit jdk should, in theory, work on Fedora but you will need to install the i686 glibc rpm's. If you selected mozilla during installation, the 32-bit libraries should be present, otherwise you can get them from the distribution or the external updates respository that has been discussed here recently.
Ok, so much for the theory. I've tried the latest 32-bit jvms from Sun, blackdown.org, and IBM. With the 32-bit glibc and libstdc++, they install, and will run Tomcat. Sometimes. For a few seconds. Then I hit the server a couple of times and get something like the error below.
So if anybody is succesfully using Java, especially tomcat or any servlet container on an x86-64, I would love to hear how it was done (what jvm, distro, etc.), since this is about what I was getting on SuSE 8.1.
Thanks, Barry Roberts
Jan 31 04:15:35 optitwo kernel: Oops: 0010 Jan 31 04:15:35 optitwo kernel: CPU 1 Jan 31 04:15:35 optitwo kernel: Pid: 18527, comm: java Not tainted Jan 31 04:15:35 optitwo kernel: RIP: 0010:[<00000001801c7fce>] Jan 31 04:15:35 optitwo kernel: RSP: 0000:0000010078583e48 EFLAGS: 00010212 Jan 31 04:15:35 optitwo kernel: RAX: 0000000000000000 RBX: 00000000cb5e2d40 RCX: 0000000000000000 Jan 31 04:15:35 optitwo kernel: RDX: 0000000000000000 RSI: 0000010078583f38 RDI: 00000000cb5e2dd0 Jan 31 04:15:35 optitwo kernel: RBP: 0000000000000000 R08: 0000000008052b7c R09: 00000000c8988920 Jan 31 04:15:35 optitwo kernel: R10: 0000000000000000 R11: 00000000c898878c R12: 0000010078583f58 Jan 31 04:15:35 optitwo kernel: R13: 0000010005412728 R14: 000000000000000c R15: 0000010078582a58 Jan 31 04:15:35 optitwo kernel: FS: 0000002a95565060(0000) GS:ffffffff80572880(005b) knlGS:00000000cb5e4bb0 Jan 31 04:15:35 optitwo kernel: CS: 0010 DS: 002b ES: 002b CR0: 000000008005003b Jan 31 04:15:35 optitwo kernel: CR2: 00000001801c7fce CR3: 0000000037ffe000 CR4: 00000000000006e0 Jan 31 04:15:35 optitwo kernel: Process java (pid: 18527, stackpage=10078583000) Jan 31 04:15:35 optitwo kernel: Stack: 0000010078583e48 0000000000000000 00000001801c7fce 0000000100000000 Jan 31 04:15:35 optitwo kernel: 0000000000000000 55b37e4400000000 0000000100000000 08052b7c00000000 Jan 31 04:15:35 optitwo kernel: 8013daaa00000000 00000000ffffffff 3b9ab29000000000 c898878c00000000 Jan 31 04:15:35 optitwo kernel: Call Trace: [<ffffffff801101ce>]{do_signal+158} [<ffffffff8013daaa>]{compat_sys_futex+202} Jan 31 04:15:35 optitwo kernel: [<ffffffff8011061b>]{intret_signal+45} Jan 31 04:15:35 optitwo kernel: Jan 31 04:15:35 optitwo kernel: Code: Bad RIP value. Jan 31 04:15:35 optitwo kernel: RIP [<00000001801c7fce>] RSP <0000010078583e48> Jan 31 04:15:35 optitwo kernel: CR2: 00000001801c7fce
On Thu, Feb 05, 2004 at 01:39:46AM -0800, Mike Larkin wrote:
The one problem I did notice is that JNI fails on the amd64 build if you use 32 bit libraries (have to use 32 bit JVM, but it works fine if you do).
What version of Tomcat are you using? Anything odd about your server.xml config?
Tomcat 4.1.27. Nothing really weird with my server.xml. From the default that comes with Tomcat, I add context's for my apps, usually put the ajp coyote connector on port 139, and that's all I change, I think. I wonder if the Oracle thin jdbc .jar I'm using is the problem.
I did get a blackdown 32-bit jdk (don't remember which version, but it was the latest a few weeks ago) to run for a couple of weeks once, but it was constantly spitting messages to /var/log/messages. And it did eventually die. That was on SuSE 8.1.
The current rc of the blackdown 64-bit jvm works with -Xint, but very slowly. And no errors. So I'm hoping the release will "just work" for me.
Thanks, Barry Roberts
Could it be a conflict on port 139 with Samba? Just a thought...
By the way, the 1.5.0 beta JDK for AMD64 fails miserably with Tomcat under SuSE 9.0.
-ml
Barry Roberts wrote:
On Thu, Feb 05, 2004 at 01:39:46AM -0800, Mike Larkin wrote:
The one problem I did notice is that JNI fails on the amd64 build if you use 32 bit libraries (have to use 32 bit JVM, but it works fine if you do).
What version of Tomcat are you using? Anything odd about your server.xml config?
Tomcat 4.1.27. Nothing really weird with my server.xml. From the default that comes with Tomcat, I add context's for my apps, usually put the ajp coyote connector on port 139, and that's all I change, I think. I wonder if the Oracle thin jdbc .jar I'm using is the problem.
I did get a blackdown 32-bit jdk (don't remember which version, but it was the latest a few weeks ago) to run for a couple of weeks once, but it was constantly spitting messages to /var/log/messages. And it did eventually die. That was on SuSE 8.1.
The current rc of the blackdown 64-bit jvm works with -Xint, but very slowly. And no errors. So I'm hoping the release will "just work" for me.
Thanks, Barry Roberts
On Fri, 2004-01-30 at 16:29, Barry Roberts wrote:
Is there a decent jdk for Fedora RC1 amd64? Or is there a way to make one of the ones I've already tried actually work?
i'm not sure how keen you are to try a beta, but it looks like sun's jdk 1.5.0 beta supports opteron: http://java.sun.com/j2se/1.5.0/docs/relnotes/features.html#platform_proc64
rob.
-
Barry Roberts -
Mark Lane -
Mike Larkin -
Nathan Bryant -
Rob Myers -
Ulrich Drepper