Re: Informix JDBC2.00_JC1 + Sun's HotSpot VM
Here is informix's response: I have had a look through out knowledge base and on the 6th of May (last Thursday) a bug was raised for this problem. I've subsequently managed to access the JDBC2.0 source and I believe that this bug was raised in error and will be closed by R&D without a fix. My reasoning for this is the following. We check the system property "java.vm.version" for the version number; -classic returns '1.2.1' but -hotspot return '1.0fcs' so clearly the Hotspot VM is at fault here - if it is a 1.2.1 VM, why doesn't it report 1.2.1 ? Below is a small example programme that you can compile and run under the two VMs which will illustrate the fault: class vers { public static void main(String args[]) { //This next line is how we obtain the VM version. String jdkVersion = System.getProperty("java.vm.version"); System.out.println(jdkVersion); } } (My output was the following:) F:\\java\\tmp>java -classic vers 1.2.1 F:\\java\\tmp>java -hotspot vers 1.0fcs I have, none the less, submitted a request for a code fix to the US which I expect to get turned down as the fault does not lie in the Informix product. In article <3736A0DE.EEAC599F@Dresdner-Bank.com>, Joerg Schneider <Joerg.Schneider@Dresdner-Bank.com> wrote: > Hello everybody, > > I tried out the latest Informix JDBC driver (Version 2.00 JC1) and found > out that > the demo's work with the Classic Java 1.2.1 VM. > > After installation of the HotSpot-Engine for JDK 1.2.1 the driver came > up with a message that it needs to be run in a JDK 1.2 environment and > exits, so no demo > is running anymore. > > Running the demo's with the "java -classic" option set, still works. > > Running "java -classic" works with the driver and "-version" returns : > java version "1.2.1" > Classic VM (build JDK-1.2.1-A, native threads) > > Running "java" with an installed HotSpot-Engine doesn't work with the > driver and "-version" returns : > java version "1.2.1" > HotSpot VM (1.0fcs, mixed mode, build E) > > Any idea's > > -- Paul Denny Group DBA PA News http://www.pa.press.net --== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.---
Hi! Paul Denny wrote in his message about cause of the fault. I simply want to add some words how resolve this problem. All what you need is java -Djava.vm.version=1.2.1 ... Paul Denny wrote in his message<7h9da9$1el$1@nnrp1.deja.com> ... >Here is informix's response: > >I have had a look through out knowledge base and on the 6th of May (last >Thursday) a bug was raised for this problem. > >I've subsequently managed to access the JDBC2.0 source and I believe >that this bug was raised in error and will be closed by R&D without a >fix. My reasoning for this is the following. We check the system >property "java.vm.version" for the version number; -classic returns >'1.2.1' but -hotspot return '1.0fcs' so clearly the Hotspot VM is at >fault here - if it is a 1.2.1 VM, why doesn't it report 1.2.1 ? > >Below is a small example programme that you can compile and run under >the two VMs which will illustrate the fault: > >class vers >{ > public static void main(String args[]) > { > //This next line is how we obtain the VM version. > String jdkVersion = System.getProperty("java.vm.version"); > System.out.println(jdkVersion); > } >} > >(My output was the following:) > >F:\\java\\tmp>java -classic vers >1.2.1 > >F:\\java\\tmp>java -hotspot vers >1.0fcs > >I have, none the less, submitted a request for a code fix to the US >which I expect to get turned down as the fault does not lie in the >Informix product. > >In article <3736A0DE.EEAC599F@Dresdner-Bank.com>, > Joerg Schneider <Joerg.Schneider@Dresdner-Bank.com> wrote: >> Hello everybody, >> >> I tried out the latest Informix JDBC driver (Version 2.00 JC1) and >found >> out that >> the demo's work with the Classic Java 1.2.1 VM. >> >> After installation of the HotSpot-Engine for JDK 1.2.1 the driver came >> up with a message that it needs to be run in a JDK 1.2 environment and >> exits, so no demo >> is running anymore. >> >> Running the demo's with the "java -classic" option set, still works. >> >> Running "java -classic" works with the driver and "-version" returns : >> java version "1.2.1" >> Classic VM (build JDK-1.2.1-A, native threads) >> >> Running "java" with an installed HotSpot-Engine doesn't work with the >> driver and "-version" returns : >> java version "1.2.1" >> HotSpot VM (1.0fcs, mixed mode, build E) >> >> Any idea's >> >> > >-- >Paul Denny >Group DBA >PA News >http://www.pa.press.net > > >--== Sent via Deja.com http://www.deja.com/ ==-- >---Share what you know. Learn what you don't.---
Thanks for this Vladimir, it is a useful workaround, Further response from Informix: I've received word back from the US. They've agreed that we're not dependent on the VM version, only the Java version, so the current checking is a bug. We'll change the code to check 'java.version' and not 'java.vm.version' - I've already tested this and Hotspot returns '1.2.1' for 'java.version', so it should work. I've ordered a patch for you (the fix will also see its way into the next release) but, according to official lines, patches may take up to 45 days but I seriously doubt if it'll be more than a week before you have your patch. In article <7hb9an$2ui1@www.na.informix.com>, "Vladimir Laptukhov" <lvm@isb.gomel.by> wrote: > Hi! > > Paul Denny wrote in his message about cause of the fault. I simply want to > add some words how resolve this problem. All what you need is > java -Djava.vm.version=1.2.1 ... > > Paul Denny wrote in his message<7h9da9$1el$1@nnrp1.deja.com> ... > >Here is informix's response: > > > >I have had a look through out knowledge base and on the 6th of May (last > >Thursday) a bug was raised for this problem. > > > >I've subsequently managed to access the JDBC2.0 source and I believe > >that this bug was raised in error and will be closed by R&D without a > >fix. My reasoning for this is the following. We check the system > >property "java.vm.version" for the version number; -classic returns > >'1.2.1' but -hotspot return '1.0fcs' so clearly the Hotspot VM is at > >fault here - if it is a 1.2.1 VM, why doesn't it report 1.2.1 ? > > > >Below is a small example programme that you can compile and run under > >the two VMs which will illustrate the fault: > > > >class vers > >{ > > public static void main(String args[]) > > { > > //This next line is how we obtain the VM version. > > String jdkVersion = System.getProperty("java.vm.version"); > > System.out.println(jdkVersion); > > } > >} > > > >(My output was the following:) > > > >F:\\java\\tmp>java -classic vers > >1.2.1 > > > >F:\\java\\tmp>java -hotspot vers > >1.0fcs > > > >I have, none the less, submitted a request for a code fix to the US > >which I expect to get turned down as the fault does not lie in the > >Informix product. > > > >In article <3736A0DE.EEAC599F@Dresdner-Bank.com>, > > Joerg Schneider <Joerg.Schneider@Dresdner-Bank.com> wrote: > >> Hello everybody, > >> > >> I tried out the latest Informix JDBC driver (Version 2.00 JC1) and > >found > >> out that > >> the demo's work with the Classic Java 1.2.1 VM. > >> > >> After installation of the HotSpot-Engine for JDK 1.2.1 the driver came > >> up with a message that it needs to be run in a JDK 1.2 environment and > >> exits, so no demo > >> is running anymore. > >> > >> Running the demo's with the "java -classic" option set, still works. > >> > >> Running "java -classic" works with the driver and "-version" returns : > >> java version "1.2.1" > >> Classic VM (build JDK-1.2.1-A, native threads) > >> > >> Running "java" with an installed HotSpot-Engine doesn't work with the > >> driver and "-version" returns : > >> java version "1.2.1" > >> HotSpot VM (1.0fcs, mixed mode, build E) > >> > >> Any idea's > >> > >> > > > >-- > >Paul Denny > >Group DBA > >PA News > >http://www.pa.press.net > > > > > >--== Sent via Deja.com http://www.deja.com/ ==-- > >---Share what you know. Learn what you don't.--- > > -- Paul Denny Group DBA PA News http://www.pa.press.net --== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.---