Bazzar bug in Eclipse/JVM/JDK?
Hi,
I am having this weird issue when debuging a STATIC block. Basically, I have a break point on a line of code inside the STATIC block, but when I press F6 to step over that line, it skips all the lines after that.
The thing is those lines were executed, it just not step to it for some bazzar reasons.
Does anyone here able to help me?
I am running Ubuntu 7.04, JDK6 and tomcat5.5. I had tried using jdk1.5 instead, but nothing seemed to help.
Thanks very much for your help.
in a nutshell, the eclipse debugger isn't very good at coping with static blocks
and the JDK doesn't enter into matters with eclipse, it only uses a JRE
Similar Messages
-
32-bit vs 64-bit JVM, JDK, DLL's
I've got a project that has a couple dependencies:
1. My project interacts with an FTDI USB->Serial converter based device. Access to this device is via DLL(FTDI calls them D2XX drivers). FTDI offers both 32-bit and 64-bit drivers. Please see here .
2. In order to get access to the DLL via Java, I'm using a JNI called [jd2xx|http://bleyer.org/jd2xx/] . I don't know if or how a JNI would change if the DLL used is 32-bit or 64-bit.
My build & run environment was XP/32. Now I want to build/run on Vista64. But I'm confused because there are multiple options for downloading and installing the different parts which make up the system:
1. Netbeans is available for 32-bit and 64-bit. Which JVM should I point Netbeans to?
2. JVM comes in 32-bit or 64-bit.
3. JDK comes in 32-bit or 64-bit.
While I don't think anyone else actually uses my project, I'd like to have both XP/32 support and Vista/64 support. If I must go one way or the other, it's gotta be Vista/64.
I have tried multiple combinations, but I get a variety of errors depending on what's installed. The errors are all related to 32-bit/64-bit conflicts.
Can someone point me down the right path?
Thanks
KeithI searched fairly thoroughly through the NetBeans GUI to see if I could target a particular platform, like 32-bit vs 64-bit ---- and I didn't find one. While it may not matter for java itself, when java interacts with a native dll, there are obviously implications.Java class files are os-agnostic - there isn't a "32-bit version" or a "64-bit version", they're both the same. What is different is the JVM that you run a class file on. A 32-bit JVM requires the appropriate 32-bit libraries, etc; the same requirement exists for a 64-bit JVM. I don't know if you can tell an IDE to run using one JVM or the other (obviously this would be possible only with 64-bit arch). I do know that the java tool for Linux/Solaris allows the use of a -d32 or -d64 option to specify that, and that the options aren't valid for the Windows java tool. I also know that Eclipse has native dependencies due to SWT, so that probably causes some restrictions. And. as you note, doing somethisng like JNI has "implications".
If you have further questions re NB, you should raise then at a NB site, not here. -
Could not find the Main Class. Program will exit. Eclipse w/ JDK 6 RC
Hi all,
I needed to upgrade to JDK 6 RC w/ Eclipse while encountering a java.lang.NullPointer exception.
Now I would like to compile my code with the new VM. I set all preferences to VM Version 6.
Now I have the following Error:
Java Virtual Machine Launcher
Could not find the Main Class. Program will exit.
What do I do now? Attached you find the Error Message.
Bye
Gerrit
================================The System.error looks like:
java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
Exception in thread "main"i wouldn't report a nullpointer to sun unless you're fairly confident there's some sort of bug. if main() can't be found it sounds to me like a config issue. if nullpointer, sounds like a code issue. post the code if you want, but i don't think sun will help you debug this.
-
Generic bug in Eclipse 3.1M4??
I gave Eclipse 3.1M4 a try and noticed a bug(?)/ feature(?) in a code like the following:
class Test implements Iterator<Integer> {
public boolean hasNext() { return false; }
public Integer next() { return null; }
public void remove() {}
}the problem is that the next() method raises the following compiler warning:
"Type safety: The return type Integer of the method next() of type Test needs unchecked conversion to conform to the return type E of inherited method"
Code looks fine to me -- am I missing something? Ideas?
thanks,
Barak"Type safety: The return type Integer of the method
next() of type Test needs unchecked conversion to
conform to the return type E of inherited method"That is a bug. -
The following code generates a segmentation fault while it's compile with CC and not with gcc.
The crash only occurs if the jvm is loaded and if the buffer size is 100000. (I tried with 50000 and there's no crash).
I assume that the crash occurs because of a corruption of the stack pointer but I don't know exactly what happens for the moment. Does anyone have an idea?
#include <stdio.h>
#include "jni.h"
#define BUFFER_SIZE 100000
typedef struct
char sz[BUFFER_SIZE];
} my_struct;
void bar(my_struct s)
return;
void foo()
my_struct s;
bar(s);
bar(s);
bar(s);
bar(s);
return;
void useJVM()
JavaVMOption options[2];
JavaVMInitArgs vm_args;
JavaVM *jvm;
JNIEnv *env;
long result;
jclass cls;
options[0].optionString = ".";
options[1].optionString = "-Djava.compiler=NONE";
vm_args.version = JNI_VERSION_1_2;
vm_args.options = options;
vm_args.nOptions = 2;
vm_args.ignoreUnrecognized = JNI_TRUE;
result = JNI_CreateJavaVM*(&jvm,(*void* **)&env, &vm_args);
if (result == JNI_ERR ) {
fprintf(stdout,"Error invoking the JVM");
return;
return;
int main( int argc,
char **argv)
if (argc != 1)
useJVM();
foo();
fprintf(stdout,"OK\n");
return 0;
} {noformat}
Built like this :
CC -mt -PIC -compat=4 -c -g -I/usr/j2sdk1.4.2/include/ -I/usr/j2sdk1.4.2/include/solaris/ mainjni.c
CC -mt -PIC -compat=4 -z allextract -o bugsun mainjni.o -L/usr/j2sdk1.4.2/jre/lib/sparc/ -ljvm -lthread -lcthe program exits with a segmentation fault.
Built like this :
gcc -c -g -I/usr/j2sdk1.4.2/include/ -I/usr/j2sdk1.4.2/include/solaris/ mainjni.c
gcc -o bugsun mainjni.o -L/usr/j2sdk1.4.2/jre/lib/sparc/ -ljvm -lthread -lcthe program works. Is it a CC bug?
Edited by: gude on May 30, 2008 9:02 AM
Edited by: gude on May 30, 2008 9:04 AMMy code :
#include <stdio.h>
#include "jni.h"
#define BUFFER_SIZE 100000
typedef struct
char sz[BUFFER_SIZE];
} my_struct;
void bar(my_struct s)
return;
void foo()
my_struct s;
bar(s);
bar(s);
bar(s);
bar(s);
return;
void useJVM()
JavaVMOption options[2];
JavaVMInitArgs vm_args;
JavaVM *jvm;
JNIEnv *env;
long result;
jclass cls;
options[0].optionString = ".";
options[1].optionString = "-Djava.compiler=NONE";
vm_args.version = JNI_VERSION_1_2;
vm_args.options = options;
vm_args.nOptions = 2;
vm_args.ignoreUnrecognized = JNI_TRUE;
result = JNI_CreateJavaVM(&jvm,(void **)&env, &vm_args);
if(result == JNI_ERR ) {
fprintf(stdout,"Error invoking the JVM");
return;
return;
int main( int argc,
char **argv)
if (argc != 1)
useJVM();
foo();
fprintf(stdout,"OK\n");
return 0;
}To compile with CC:
CC -mt -PIC -compat=4 -c -g -I/usr/j2sdk1.4.2/include/ -I/usr/j2sdk1.4.2/include/solaris/ mainjni.c
CC -mt -PIC -compat=4 -z allextract -o bugsun mainjni.o -L/usr/j2sdk1.4.2/jre/lib/sparc/ -ljvm -lthread -lcTo compile with gcc:
gcc -c -g -I/usr/j2sdk1.4.2/include/ -I/usr/j2sdk1.4.2/include/solaris/ mainjni.c
gcc -o bugsun mainjni.o -L/usr/j2sdk1.4.2/jre/lib/sparc/ -ljvm -lthread -lcI noticed that if I only call the function bar() three times in the function foo(), it works... -
Using JRockit for SAP JVM (JDK 1.4.2_37b02)
Can I use JRockit to monitor SAP JVM (J2EE) threads, memory, Garbage Collector?
We are running on Windows 2003, SP2 with MS SQL 2005. We run SAP NetWeaver Portal 7.02 on Sun Partner JDK 1.4.2_37
SAP has there own SAP Memory Analyzer Profiler tools, but there graphs, messaging (email, sms, etc.) as well as reports are weak.
Thanks.
JamesNo, this will not work. The SAP JVM is based on Hotspot, while the JRockit tools require the JRockit JVM to work.
Henrik -
Eclipse JRE/JDK must be available error
HELP!!!. i am trying to run eclipse 3.5 and i am getting the following error
A Java Runtime Environment (JRE) or java Development Kit (JDK)
must be available in order to run eclipse. No Java virtual machiene
was found after searching the following locations:
C:\Users\Colin|Desktop\eclipse-jee-galileo-win32\eclipse\jre\bin\javaw.exe
javaw.exe in your current PATH
bare with me because i am new to this. I installed both JDK and JRE from the following webpage <http://www.oracle.com/technetwork/java/javase/downloads/index.html> and have reinstalled them after i have unzipped the eclipse files and i am still getting the error.
if i follow that path C:\Users\Colin|Desktop\eclipse-jee-galileo-win32\eclipse\jre\bin\javaw.exe
the jre\bin\javaw.exe part doesnt exist so is there a way to change where it is looking to the correct location???
my javaw.exe file is located at
C:\Program Files\Java\jdk1.6.0_21\bin
any help would be appreciated.Hello,
In the installation eclipse search for java virtual machines on your system.
In your case eclipse doesn't found a suitable javaw executable in the system path.
You have to set the "C:\Program Files\Java\jdk1.6.0_21\bin" in the system path and then install eclipse.
1# From the desktop, right-click My Computer and click Properties.
2# In the System Properties window, click on the Advanced tab.
3# In the Advanced section, click the Environment Variables button.
4# Finally, in the Environment Variables window, highlight the path variable in the Systems Variable (not user variables) section and click the Edit button. Add ";C:\Program Files\Java\jdk1.6.0_21\bin" to the path line. Each different directory is separated with a semicolon.
5# Open a system console and execute
java -versionyou have to get something like
java version "1.6.0_18"
Java(TM) SE Runtime Environment (build 1.6.0_18-b07)
Java HotSpot(TM) Client VM (build 16.0-b13, mixed mode)because now your java binaries are in the system path
6# Install eclipse
Best reggards, -
Well, I've seen that many people have had this problem. Unfortunately, I believe most of the advice was for shells (w/ Linux). I'm using Windows Vista Ultimate (64-bit) (if this makes any difference).
I downloaded eclipse and extracted to desktop. When I open up "eclipse" however, it gives me this error message:
A Java Runtime Environment(JRE) or Java Development Kit(JDK) must be available in order to run Eclipse. No Java virtual machine was found after searching the following locations: E:\UserName\Programs\eclipse\jre\bin\javaw.exe javaw.exe in your current PATH
I have no idea how to fix this. I have JDK and JRE in a Java folder in C:\. I have gotten JCreator to work easily, but eclipse won't even open. Any help would be appreciated.New here too. I downloaded a music site, Limewise.com Pro and it gives me the same message. I can't even open it. I've got the Java JRE installed, I have the Limewise installed, but the two won't connect. Is it a firewall thing? How do I fix it? I paid for a music site I can't even open! HELP! I've spent hours and can't figure it out. I'm a non-techie. If you can tell me, please?
Lanie -
Calendar bug setting DAY_OF_WEEK in JDK 1.3.1
I cannot find a workaround for this bug:
import java.util.Calendar;
import java.util.Date;
public class Mescal {
public static void main(String[] args) {
Calendar cal = Calendar.getInstance();
cal.set(2002, Calendar.FEBRUARY, 2); // Sat, 2 Feb 2002
cal.set(Calendar.MILLISECOND, 0);
Date d = new Date(cal.getTime().getTime());
Calendar cal2 = Calendar.getInstance();
cal2.setTime(d);
cal.set(cal2.get(Calendar.YEAR),
cal2.get(Calendar.MONTH),
cal2.get(Calendar.DATE));
// cal.set(Calendar.WEEK_OF_MONTH, cal2.get(Calendar.WEEK_OF_MONTH));
System.out.println("start: " + cal.getTime() + " : " + d);
cal.setTime(d);
cal.set(Calendar.DAY_OF_WEEK, Calendar.MONDAY);
System.out.println("Set weekday: " + cal.getTime());
cal.set(Calendar.HOUR_OF_DAY, 0);
System.out.println("Set hour: " + cal.getTime());
cal.set(Calendar.MINUTE, 0);
System.out.println("Set minute: " + cal.getTime());
cal.set(Calendar.SECOND, 0);
System.out.println("Set second: " + cal.getTime());
The output is:
start: Sat Feb 02 11:19:18 CET 2002 : Sat Feb 02 11:19:18 CET 2002
Set weekday: Mon Jan 28 11:19:18 CET 2002
Set hour: Mon Dec 31 00:19:18 CET 2001
Set minute: Mon Nov 26 00:00:18 CET 2001
Set second: Mon Oct 29 00:00:00 CET 2001
The problem arises when setting the weekday takes the date back to the previous month. For example, starting off with Feb 9:
start: Sat Feb 09 11:20:50 CET 2002 : Sat Feb 09 11:20:50 CET 2002
Set weekday: Mon Feb 04 11:20:50 CET 2002
Set hour: Mon Feb 04 00:20:50 CET 2002
Set minute: Mon Feb 04 00:00:50 CET 2002
Set second: Mon Feb 04 00:00:00 CET 2002
This has been fixed in JDK1.4Beta2, but obviously we're not going to pin our application on that. There's also a problem with 1.4 that I'll get to in a bit.
The second calendar attempt (seen in code sample but ultimately not used) doesn't make any difference. Although if you don't use setTime and only initialize the calendar using set(int year, int month, int day) then setting the weekday sets it to the 1st week of the month.
For example:
Calendar cal = Calendar.getInstance();
cal.set(2002, Calendar.FEBRUARY, 13); // Sat, 2 Feb 2002
cal.set(Calendar.MILLISECOND, 0);
System.out.println("start: " + cal.getTime());
cal.set(Calendar.DAY_OF_WEEK, Calendar.MONDAY);
//rest of code is same
produces:
start: Wed Feb 13 11:38:20 CET 2002
Set weekday: Mon Feb 04 11:38:20 CET 2002
Set hour: Mon Feb 04 00:38:20 CET 2002
Set minute: Mon Feb 04 00:00:20 CET 2002
Set second: Mon Feb 04 00:00:00 CET 2002
The bug (?) in JDK1.4Beta2:
if you set WEEK_OF_YEAR, then the date is advanced one.
Calendar cal = Calendar.getInstance();
cal.set(2002, Calendar.FEBRUARY, 13); // Sat, 2 Feb 2002
cal.set(Calendar.MILLISECOND, 0);
cal.setFirstDayOfWeek(Calendar.SUNDAY);
Date d = new Date(cal.getTime().getTime());
Calendar cal2 = Calendar.getInstance();
cal2.setTime(d);
// cal.set(cal2.get(Calendar.YEAR),
// cal2.get(Calendar.MONTH),
// cal2.get(Calendar.DATE));
cal.set(Calendar.WEEK_OF_YEAR, cal2.get(Calendar.WEEK_OF_YEAR));
// System.out.println("start: " + cal.getTime() + " : " + d);
// cal.setTime(d);
System.out.println("start: " + cal.getTime());
Gives you:
start: Thu Feb 14 11:41:37 CET 2002
Set weekday: Mon Feb 11 11:41:37 CET 2002
Set hour: Mon Feb 11 00:41:37 CET 2002
Set minute: Mon Feb 11 00:00:37 CET 2002
Set second: Mon Feb 11 00:00:00 CET 2002
If you comment out the line cal.set(Calendar.WEEK_OF_YEAR
then the first line of output reads:
start: Wed Feb 13 11:38:17 CET 2002
An unholy mess.Hi,
I had the same bug as you one week ago... though i never come up with a neat solution, i used several loops to counter this. Its works nicely, but the logic is messy. Here's the code:
Calendar c =new GregorianCalendar();
int first=2002;
int second=2;
c.set(Calendar.YEAR,first);
c.set(Calendar.MONTH,second-1); //setting it to feburary
//getting the month after i set
int m = c.get(Calendar.MONTH);
//testing if it has 31 days in the month
c.set(Calendar.DATE,31);
//if the month doesnt have 31 days, the month will be
//march as java set it the the next month
int m1 = c.get(Calendar.MONTH);
int d = c.get(Calendar.DATE);
System.out.println("month1 is "+m1);
if(m1!=m)
//if m and m1 doesnt match means the month
//doesnt have 31 days
{//if
//set the month back to the desire month
c.set(Calendar.MONTH,second-1);
//test the month for 30 days c.set(Calendar.DATE,30);
m1 = c.get(Calendar.MONTH);
d = c.get(Calendar.DATE);
System.out.println("month1 is "+m1);
if(m1!=m)
{//if
c.set(Calendar.MONTH,second-1);
c.set(Calendar.DATE,29);
m1 = c.get(Calendar.MONTH);
d = c.get(Calendar.DATE);
System.out.println("month1 is "+m1);
if(m1!=m)
{//if
c.set(Calendar.MONTH,second-1);
c.set(Calendar.DATE,28);
m1 = c.get(Calendar.MONTH);
d = c.get(Calendar.DATE);
System.out.println("month1 is "+m1);
}//end if
}//end if
}//end if
}//end if -
Thread dump running Classic JVM(jdk 1.2.2)
Hi,
We get a thread dump while running our application. The application is in java/jsp running on apache-tomcat. The tomcat version is 3.2.1. Java version being used is:
java version "1.2.2"
Classic VM (build JDK-1.2.2-007, native threads, symcjit)
Does anyone have any idea how to identify the reason for the thread dump? The application eventually hangs after the thread dump. Thanks in advance. Below is the dump:
<pre>
Full thread dump Classic VM (JDK-1.2.2_007, native threads):
"Thread-34" (TID:0x5faa550, sys_thread_t:0x2f4158, state:CW, native ID:0xb9c) prio=5
"Thread-33" (TID:0x5faa1d0, sys_thread_t:0x22092f98, state:CW, native ID:0xa54) prio=5
at java.lang.Object.wait(Native Method)
at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-32" (TID:0x5faa220, sys_thread_t:0x2207df88, state:R, native ID:0xb18) prio=5
at java.net.SocketInputStream.socketRead(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java, Compiled Code)
at org.apache.tomcat.service.connector.TcpConnector.receiveFully(TcpConnector.java, Compiled Code)
at org.apache.tomcat.service.connector.TcpConnector.receive(TcpConnector.java, Compiled Code)
at org.apache.tomcat.service.connector.Ajp13ConnectionHandler.processConnection(Ajp13ConnectionHandler.java, Compiled Code)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-31" (TID:0x5fa9e48, sys_thread_t:0x22080228, state:CW, native ID:0xb2c) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-30" (TID:0x5fa9e98, sys_thread_t:0x22080140, state:CW, native ID:0x908) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-29" (TID:0x5fa9ee8, sys_thread_t:0x2207e758, state:CW, native ID:0x74c) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-28" (TID:0x5fa9f38, sys_thread_t:0x22080518, state:R, native ID:0x2fc) prio=5
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
at java.net.ServerSocket.implAccept(ServerSocket.java:242)
at java.net.ServerSocket.accept(ServerSocket.java:224)
at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-27" (TID:0x5fa9b58, sys_thread_t:0x2207ff00, state:CW, native ID:0xa7c) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-26" (TID:0x5fa9ba8, sys_thread_t:0x2207fd90, state:CW, native ID:0xa70) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-25" (TID:0x5fa9bf8, sys_thread_t:0x2207fb78, state:CW, native ID:0x4d4) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-24" (TID:0x5fa9ca0, sys_thread_t:0x2207f8f0, state:CW, native ID:0x7c8) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-23" (TID:0x5fa9c98, sys_thread_t:0x22055c18, state:CW, native ID:0xa60) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-22" (TID:0x5fa94a0, sys_thread_t:0x220556a0, state:CW, native ID:0x68c) prio=5
at java.lang.Object.wait(Native Method)
at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-21" (TID:0x5fa94f0, sys_thread_t:0x220555b8, state:R, native ID:0xb24) prio=5
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
at java.net.ServerSocket.implAccept(ServerSocket.java:242)
at java.net.ServerSocket.accept(ServerSocket.java:224)
at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-20" (TID:0x5fa9540, sys_thread_t:0x22055448, state:CW, native ID:0x664) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-19" (TID:0x5fa9590, sys_thread_t:0x22055360, state:CW, native ID:0x5c0) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-18" (TID:0x5fa9338, sys_thread_t:0x220551f0, state:CW, native ID:0x874) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-17" (TID:0x5fa9388, sys_thread_t:0x22055080, state:CW, native ID:0x4f4) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-16" (TID:0x5fa9480, sys_thread_t:0x22064cf8, state:CW, native ID:0x814) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-15" (TID:0x5fa9428, sys_thread_t:0x22064b88, state:CW, native ID:0x8ec) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-14" (TID:0x5fa9478, sys_thread_t:0x22064aa0, state:CW, native ID:0x24c) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-13" (TID:0x5fa8f68, sys_thread_t:0x22064930, state:CW, native ID:0x410) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-12" (TID:0x5fa8fb8, sys_thread_t:0x22064848, state:CW, native ID:0x3f0) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-11" (TID:0x5fa86b8, sys_thread_t:0x220607f0, state:CW, native ID:0xb28) prio=5
at java.lang.Object.wait(Native Method)
at org.apache.tomcat.util.ThreadPool$MonitorRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-10" (TID:0x5fa85f0, sys_thread_t:0x22061618, state:R, native ID:0x6fc) prio=5
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:414)
at java.net.ServerSocket.implAccept(ServerSocket.java:242)
at java.net.ServerSocket.accept(ServerSocket.java:224)
at org.apache.tomcat.service.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java:286)
at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java, Compiled Code)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-9" (TID:0x5fa8648, sys_thread_t:0x22061530, state:CW, native ID:0x484) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-8" (TID:0x5fa83f0, sys_thread_t:0x220613c0, state:CW, native ID:0x8f0) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-7" (TID:0x5fa8440, sys_thread_t:0x22061250, state:CW, native ID:0x94c) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-6" (TID:0x5fa8490, sys_thread_t:0x220610e0, state:CW, native ID:0x994) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-5" (TID:0x5fa84e0, sys_thread_t:0x2205a2a8, state:CW, native ID:0x530) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-4" (TID:0x5fa8120, sys_thread_t:0x2205a138, state:CW, native ID:0x730) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-3" (TID:0x5fa8170, sys_thread_t:0x2205a050, state:CW, native ID:0x688) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-2" (TID:0x5fa81c0, sys_thread_t:0x2205a560, state:CW, native ID:0x3c0) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-1" (TID:0x5fa8218, sys_thread_t:0x22053520, state:CW, native ID:0x8fc) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"StandardManager" (TID:0x5fa1158, sys_thread_t:0x220596a0, state:CW, native ID:0x724) prio=5
at java.lang.Thread.sleep(Native Method)
at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"StandardManager" (TID:0x5f9d178, sys_thread_t:0x22031d18, state:CW, native ID:0xaa0) prio=5
at java.lang.Thread.sleep(Native Method)
at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"StandardManager" (TID:0x5f872f8, sys_thread_t:0x21c8b718, state:CW, native ID:0x880) prio=5
at java.lang.Thread.sleep(Native Method)
at org.apache.tomcat.session.StandardManager.threadSleep(StandardManager.java, Compiled Code)
at org.apache.tomcat.session.StandardManager.run(StandardManager.java, Compiled Code)
at java.lang.Thread.run(Thread.java:479)
"Thread-0" (TID:0x5f4e670, sys_thread_t:0x21b0eac0, state:CW, native ID:0x8bc) prio=5
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java, Compiled Code)
at org.apache.tomcat.util.Queue.pull(Queue.java, Compiled Code)
at org.apache.tomcat.logging.LogDaemon$1.run(TomcatLogger.java, Compiled Code)
at org.apache.tomcat.logging.LogDaemon.run(TomcatLogger.java, Compiled Code)
"SymcJIT-LazyCompilation-1" (TID:0x5f2e4f8, sys_thread_t:0x20e977d8, state:CW, native ID:0x458) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
"SymcJIT-LazyCompilation-0" (TID:0x5f2e540, sys_thread_t:0x20e9b6d0, state:CW, native ID:0x9bc) prio=1
at SymantecJITCompilationThread.DoCompileMethod(Native Method)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
"SymcJIT-LazyCompilation-PA" (TID:0x5f2e508, sys_thread_t:0x20e9b560, state:CW, native ID:0x820) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at SymantecJITCompilationThread.run(JITcompilationthread.java, Compiled Code)
"Finalizer" (TID:0x5f29320, sys_thread_t:0x20dddec0, state:CW, native ID:0x4e8) prio=8
at java.lang.Object.wait(Native Method)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java, Compiled Code)
at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:174)
"Reference Handler" (TID:0x5f293b0, sys_thread_t:0x20ddc7d0, state:CW, native ID:0x55c) prio=10
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:424)
at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:114)
"Signal dispatcher" (TID:0x5f293e0, sys_thread_t:0x20dda218, state:R, native ID:0xa1c) prio=5
Monitor Cache Dump:
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8178/6FF4140: <unowned>
Waiting to be notified:
"Thread-3" (0x2205a050)
java.net.PlainSocketImpl@5FA7DC0/6FF18C8: owner "Thread-10" (0x22061618) 1 entry
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8128/6FF4248: <unowned>
Waiting to be notified:
"Thread-4" (0x2205a138)
SymantecJITCompilationThread@5F2E540/6C1F6A0: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-PA" (0x20e9b560)
org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FAA1D8/6FFF340: <unowned>
Waiting to be notified:
"Thread-33" (0x22092f98)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA95D8/6FFADA8: <unowned>
Waiting to be notified:
"Thread-20" (0x22055448)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA81C8/6FF32F8: <unowned>
Waiting to be notified:
"Thread-2" (0x2205a560)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9598/6FFAC90: <unowned>
Waiting to be notified:
"Thread-19" (0x22055360)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8448/6FF4978: <unowned>
Waiting to be notified:
"Thread-7" (0x22061250)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9C50/6FFBAF8: <unowned>
Waiting to be notified:
"Thread-24" (0x2207f8f0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9430/6FFA840: <unowned>
Waiting to be notified:
"Thread-15" (0x22064b88)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9C00/6FFC850: <unowned>
Waiting to be notified:
"Thread-25" (0x2207fb78)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA84E8/6FF4350: <unowned>
Waiting to be notified:
"Thread-5" (0x2205a2a8)
org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FA94A8/6FFAFB8: <unowned>
Waiting to be notified:
"Thread-22" (0x220556a0)
org.apache.tomcat.util.Queue@5F4E6C0/6D4B798: <unowned>
Waiting to be notified:
"Thread-0" (0x21b0eac0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8498/6FF4458: <unowned>
Waiting to be notified:
"Thread-6" (0x220610e0)
java.net.PlainSocketImpl@5FA9768/6FFB970: owner "Thread-28" (0x22080518) 1 entry
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8F70/6FFA630: <unowned>
Waiting to be notified:
"Thread-13" (0x22064930)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9B60/6FFCA60: <unowned>
Waiting to be notified:
"Thread-27" (0x2207ff00)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9740/6FFB9F0: <unowned>
Waiting to be notified:
"Thread-23" (0x22055c18)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9340/6FFAB88: <unowned>
Waiting to be notified:
"Thread-18" (0x220551f0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8F20/6FFA738: <unowned>
Waiting to be notified:
"Thread-14" (0x22064aa0)
java.lang.ref.ReferenceQueue$Lock@5F29338/6BF89C0: <unowned>
Waiting to be notified:
"Finalizer" (0x20dddec0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA83F8/6FF4A80: <unowned>
Waiting to be notified:
"Thread-8" (0x220613c0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA93E0/6FFA948: <unowned>
Waiting to be notified:
"Thread-16" (0x22064cf8)
java.net.PlainSocketImpl@5FA8FE8/6FF9860: owner "Thread-21" (0x220555b8) 1 entry
java.lang.ref.Reference$Lock@5F293C0/6BF84B8: <unowned>
Waiting to be notified:
"Reference Handler" (0x20ddc7d0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8FC0/6FF98E0: <unowned>
Waiting to be notified:
"Thread-12" (0x22064848)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9BB0/6FFC958: <unowned>
Waiting to be notified:
"Thread-26" (0x2207fd90)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9390/6FFAA80: <unowned>
Waiting to be notified:
"Thread-17" (0x22055080)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8650/6FF4B88: <unowned>
Waiting to be notified:
"Thread-9" (0x22061530)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9E50/6FFF128: <unowned>
Waiting to be notified:
"Thread-31" (0x22080228)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA8220/6FF31A8: <unowned>
Waiting to be notified:
"Thread-1" (0x22053520)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9EF0/6FFEF18: <unowned>
Waiting to be notified:
"Thread-29" (0x2207e758)
org.apache.tomcat.util.ThreadPool$MonitorRunnable@5FA86C0/6FF5858: <unowned>
Waiting to be notified:
"Thread-11" (0x220607f0)
org.apache.tomcat.util.ThreadPool$ControlRunnable@5FA9EA0/6FFF020: <unowned>
Waiting to be notified:
"Thread-30" (0x22080140)
Registered Monitor Dump:
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Method Monitor: <unowned>
SymcJIT Lazy Queue Lock: <unowned>
Waiting to be notified:
"SymcJIT-LazyCompilation-0" (0x20e9b6d0)
"SymcJIT-LazyCompilation-1" (0x20e977d8)
SymcJIT Method Monitor: <unowned>
SymcJIT Method List Monitor: <unowned>
SymcJIT Lock: <unowned>
utf8 hash table: <unowned>
JNI pinning lock: <unowned>
JNI global reference lock: <unowned>
BinClass lock: <unowned>
Class linking lock: <unowned>
System class loader lock: <unowned>
Code rewrite lock: <unowned>
Heap lock: <unowned>
Monitor cache lock: owner "Signal dispatcher" (0x20dda218) 1 entry
Thread queue lock: owner "Signal dispatcher" (0x20dda218) 1 entry
Waiting to be notified:
"Thread-34" (0x2f4158)
Monitor registry: owner "Signal dispatcher" (0x20dda218) 1 entry
</pre>
Regards,
PrashantNo. we are getting the thread dumps only on the production server, and it being running on production, we cannot try it out with newer versions. However, we have so far been unable to simulate the thread dumps on our machines using the same version.
-
Is it possible I found a bug in Java Pattern (JDK 1.5)???
It is hard to believe that I should have found an error in the java.util.regex.Pattern class - and I hope you can tell me I'm wrong. Look at this example:
Let's say the pattern is "%\d+". I can then easily match against, let's say "%20". If I however changes the string to "%20 ", then no match, not complete or partial! The oddest thing is that it seems to be connected to the usage of "%". To really nail the point..if you change the string to "%20 %20 ", then you will find two partial matches (which is correct). I have tried to debug the Pattern-class myself - but my debugger wouldn't show me the local variables in the Pattern class, so I gave up. Try to run the program below with JRE 1.5 (update 18) and exchange the "s" var to test it.
public class RegExp {
private static Pattern pattern = Pattern.compile("%\\d+");
public static void main(String[] args) {
String s = "%20";
Matcher m = pattern.matcher(s);
if (m.matches()) {
System.out.println("Complete match:");
for (int i = 0; i <= m.groupCount(); i++) {
System.out.println("Group " + i + " : " + m.group(i));
} else if (m.find()) {
int pos = 0;
while (m.find(pos)) {
System.out.println("Partial match:");
pos = m.end();
for (int i = 0; i <= m.groupCount(); i++) {
System.out.println("Group " + i + " : " + m.group(i));
} else {
System.out.println("NO MATCH");
Edited by: mortensi on Jun 4, 2009 2:25 AMSorry about the code. It truly compiled and worked..but I didn't know about the code-tag thing. Here is an version that should work well...or at least I hope so
import java.util.regex.Matcher;
import java.util.regex.Pattern;
public class RegExp {
private static Pattern pattern = Pattern.compile("%\\d+");
* @param args
public static void main(String[] args) {
String s = "%20";
Matcher m = pattern.matcher(s);
if (m.matches()) {
System.out.println("Complete match:");
for (int i = 0; i <= m.groupCount(); i++) {
System.out.println("Group " + i + " : " + m.group(i));
} else if (m.find()) {
int pos = 0;
while (m.find(pos)) {
System.out.println("Partial match:");
pos = m.end();
for (int i = 0; i <= m.groupCount(); i++) {
System.out.println("Group " + i + " : " + m.group(i));
} else {
System.out.println("NO MATCH");
} -
Oracle XML parser and IBM jdk bug
Hello,
From a few messages found in the XML forum it seems that IBM jvm could cause problems with oracle XML parser. ( see http://technet.oracle.com:89/ubb/Forum11/HTML/003823.html )
I am using IBM jvm (jdk 1.3) on a linux box, and problems are starting to arise:
I have
- 1 BC4J based jsp app which works fine.
- 2 XML parsing BC4J apps which cause strange errors (like parsing 40 documents fine and failing on the 41st for no apparent reason)
Hopefully, Steven Muench provided precious advice on this (basically, disabling the JIT), however some issues are still open:
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>You should file a bug with IBM to get this fixed, using your stylesheet as a testcase. Lots of people have hit this problem.<HR></BLOCKQUOTE>
Has anyone (from oracle or else) done this yet? I have gone (quickly) through IBM website but I didn't find any bug report utility or the like...
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Disable your JIT compiler (or switch JVM's) and you won't have the error.<HR></BLOCKQUOTE>
Turning off the JIT indeed made the errors vanish, thanks a lot for the tip!
I have a few more questions though :
* As the BC4J framework uses the xml parser, It is fairly possible that the ibm jvm bug will affect it...
I haven't had any problems (yet?) with the BC4J part of my applications, but I'm a bit concerned about having random bugs lurking around (I have more than enough of my own :) )
Has anyone stumbled upon IBM JVM vs oracle parser issues in BC4J? (oracle.xml.parser.v2.XXXXXX exceptions...)
* If BC4J is indeed affected, what's the solution?
- Disable the JIT? (And forget about performance?... hmmm... no)
- Switch parsers? (oracle parser is too tightly integrated in the BC4J Framework isn't it?.. hmm... not possible either)
- Wait for a patch from IBM (and use another one in the meantime) / switch JVM :
In either case, I'd really like to know what is the JVM that oracle people use / would advise.
Thanks for your help
nullFor those interested,
last week i reported this bug in the ibm jvm news forum.
They said that the problem had been investigated and would be fixed in their next service release.
FYI: the current release (SR7, labeled "build cx130-20010329) still has various problems wih oracle XML parser.
Remi
null -
Hi, I'm extracting an XML file via JDBC, and it works OK in JDeveloper compiled with java version "JDK1.2.2_JDeveloper" as the target JDK version in the project properties. The file comes out as it should and I can invoke IE to view it. But when I compile with java version "1.3.0" as the target JDK version, I get hexcode or something instead of characters. This is the output when the files are compiled for JDK version "JDK1.2.2_JDeveloper":<P>"D:\Java\JDeveloper\java1.2\jre\bin\javaw.exe" -classpath "D:\wd\classes;D:\Java\JDeveloper\lib\jdev-rt.zip;D:\Java\JDeveloper\jdbc\lib\oracle8.1.7\classes12.zip;D:\Java\JDeveloper\lib\connectionmanager.zip;D:\Java\JDeveloper\java1.2\jre\ lib\rt.jar" MCP <BR>filename: D:\wd\Jenny<BR>name: Jenny<BR>Connected<BR>Returnfile = '<stanfordDocument name="Jenny" type="Produktion" lastSavedDate="1997-08-10T05:51:10+01:00"><numberOfTreeSpecies>1</numberOfTreeSpecies><treeSpecies name="GRAN" numberOfAssortments="1"/><treeSpecies name="TALL" numberOfAssortments="1"/></stanfordDocument>'<BR>Jenny extracted.<BR>Connection closed. <BR>-----------------<P>Compiled for java version "1.3.0":<P>"D:\Java\sdk1.3\jre\bin\javaw.exe" -classpath "D:\wd\classes;D:\Java\JDeveloper\lib\jdev-rt.zip;D:\Java\JDeveloper\jdbc\lib\oracle8.1.7\classes12.zip;D:\Java\JDeveloper\lib\connectionmanager.zip;D:\Java\sdk1.3\lib\dt.jar;D:\Ja va\sdk1.3\jre\lib\rt.jar;D:\Java\sdk1.3\jre\lib\i18n.jar" MCP <BR>filename: D:\wd\Jenny<BR>name: Jenny<BR>Connected<BR>Returnfile = '3C007300740061006E0066006F007200640044006F00630075006D0065006E00740020006E0061006D0065003D0022004A0065006E006E0079002200200074007900700065003D002200500072006F00640075006B007400690 06F006E00220020006C006100730074005300610076006500640044006100740065003D00220031003900390037002D00300038002D00310030005400300035003A00350031003A00310030002B00300031003A0030003000220 03E003C006E0075006D006200650072004F006600540072006500650053007000650063006900650073003E0031003C002F006E0075006D006200650072004F006600540072006500650053007000650063006900650073003E0 03C007400720065006500530070006500630069006500730020006E0061006D0065003D0022004700520041004E00220020006E0075006D006200650072004F0066004100730073006F00720074006D0065006E00740073003D0 02200310022002F003E003C007400720065006500530070006500630069006500730020006E0061006D0065003D002200540041004C004C00220020006E0075006D006200650072004F0066004100730073006F00720074006D0 065006E00740073003D002200310022002F003E003C002F007300740061006E0066006F007200640044006F00630075006D0065006E0074003E00'<BR>Jenny extracted.<BR>Connection closed. <BR>-----------------<P><BR>It seems there is a difference in how the characters are interpreted by the JVM. When I try <BR>to extract the file using a JavaBean and JSP, I also get just numbers. The browser is using the <BR>standard JVM, not the JDev one. Is this a bug in the JVM that comes with Jdev? Or in the compiler? How can I get <BR>the XML file out of the database so that the standard JVM can interpret it as characters? <BR>(In both cases the character encoding is set to "ISO8859_1".)<P>/Fredrik
nullAny ideas?Put a debugging println in the constructor.
Seriously.
Put a debugging println in the constructor.
You may be absolutely certain you are calling the initialization method (which makes me wonder whether you should be calling it from the constructor in the first place). But you may have an issue like multiple class loaders that results in the code doing something you are absolutely certain it does not do.
Put a debugging println in the constructor. -
Hi EveryOne
I want clear differcence between JVM ,JDK and Java Runtime
And which includes whick one ?
For running .class file what we require ?A Java virtual machine (JVM) is a program that executes Java class files.
A Java runtime environment (JRE) includes a JVM and all the standard class libraries that come with the Java platform. A JRE can also include things like plugins for your browser.
A Java developers kit (JDK) includes a JRE and all the tools you need to develop programs for the Java platform.
If you just want to run .class files from a command line, you just need a JRE. -
WebLogic 5.1 & IBM JDK 1.1.8 on RedHat Linux 6.2
Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat 6.2 machine. When I start the sample server, it always SIGEV in the native thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like to evaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]Hi Michael
It appears to be a bug in the IBM JDK 1.1.8 release version built on May ??
,2000. I downloaded the newer version IBM JDK 1.1.8 built on July 13,2000
and it appears to be fine with SP4.
I am curious as to the status of IBM JDK1.3 on RedHat 6.2 and well as the
SUN JDK1.3. Both appear to crash. I would really like to take advantage of
the performance features offered.
Thanks
"Michael Girdley" <[email protected]> wrote in message
news:[email protected]..
>
>
Could you please post the error?
You should also make sure that you are using a certified JVM. Theplatform
support page for WebLogic Server is located at:
http://www.weblogic.com/platforms/index.html
This page has the latest and greatest information on the platforms that
WebLogic is certified and supported on.
Thanks,
Michael
Michael Girdley
Product Manager, WebLogic Server & Express
BEA Systems Inc
"Narayanan Iyer" <[email protected]> wrote in message
news:[email protected]..
Hello
I am trying to get WebLogic 5.1 to run with IBM JDK 1.1.8 on a RedHat
6.2
machine. When I start the sample server, it always SIGEV in the native
thread (something like that).
I do not have any problems with the Blackdown 1.2.X JDK. I would like toevaluate the IBM JDK as that is the preferred solution in my group.
Please reply
Thanks you
Narayanan Iyer
[email protected]
Maybe you are looking for
-
I have been having huge problems with MediaSource ever since I bought by Zen Touch. For some reason, this software slows my computer down to an extreme level, including not allowing me to use some programs (including WMP 0) and forces me to restart.
-
Taglib repeating in jsp page in TOMCAT. (Can this be Tag pool issue? )
Hi, We have an application and it is running fine on one servlet container "ServletExec". We are migrating our application to Tomcat and some weird things happenned. In one of my JSP pages say page " A ", I have included another small JSP say " B "wh
-
How do I update my 3GS to iOS 5?
How do I update my 3GS to iOS 5? I've tried the update on iTunes but it says my phone is up-to-date with version 4.2.1
-
Problem in BDC page down for VA41
Hi, please help. -Mahesh Message was edited by: Mahesh Varma
-
Hi! I cant save my document in office. Can anybody help?
Suddenly it stopped working. I have all recent updates, and my Office is brand new