david1234

Members
  • Content count

    0
  • Joined

  • Last visited

Community Reputation

0 Neutral

About david1234

  • Rank
    Newbie
  • Birthday 01/01/01
  1. I found the solution (at least to my problem): I used the following option System.setProperty("javax.net.debug","all"); to debug what is happening and compare the output generated by running the program using the sun JVM and then the JET test run (Step 2 of 7) JET uses a version of cacerts which is stored in: C:\jet7.2-pro\profile1.6.0_24\jre\lib\security it is different from the one used by the sun java machine which is stored in: C:\Program Files\Java\jdk1.6.0_24\jre\lib\security by copying it to the JET profile directory, the software finally behaves as expected I hope it works when it's compiled. David
  2. I am getting the same error which doesn't happen when I run the code from within Netbeans. I am using Jet7.2 with Java SE6 update 24 installed under windows XP javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target at com.sun.net.ssl.internal.ssl.Alerts.getSSLException(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.fatal(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.fatalSE(Unknown Source) at com.sun.net.ssl.internal.ssl.ClientHandshaker.serverCertificate(Unknown Source) at com.sun.net.ssl.internal.ssl.ClientHandshaker.processMessage(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.processLoop(Unknown Source) at com.sun.net.ssl.internal.ssl.Handshaker.process_record(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.readRecord(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.performInitialHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.startHandshake(Unknown Source) at sun.net.www.protocol.https.HttpsClient.afterConnect(Unknown Source) at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at java.net.HttpURLConnection.getResponseCode(Unknown Source) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unknown Source) at javax.swing.JEditorPane.getStream(Unknown Source) at javax.swing.JEditorPane.getStream(Unknown Source) at javax.swing.JEditorPane.setPage(Unknown Source) at javax.swing.JEditorPane.setPage(Unknown Source)
  3. Dear support, I found the problem, which had nothing to do with JET Pack and JET compiler, there was a slight difference in configuration files of my software, one was used by the packed version and the other one by the compiler in 'directly run' mode. Sorry for the trouble David
  4. Thanks for the quick reply, here is the list which I copied out of the .prj file. The part that behaves strangely, without generating any error code is a web service call using the JAX-RPC library and Netbeans feature to generate code from a WSDL file, so towares the end of the classpath. Thanks for looking into this, David %%Excelsior JET v6.5 project file -compilewithfixedheap+ -genstackalloc+ -genstacktrace- -global+ -gui+ -ignoreclassduplication+ -ignorememberabsence+ -inline+ -jetcpenablemanualsettings+ -splashcloseonawtwindow- -splashcloseonclick- -splashgetfrommanifest- -apptype=Plain -classabsence=HANDLE -compilerheap=1191182336 -... -heaplimit=0 -inlinelimit=100 -inlinetolimit=1000 -jetcplastpage:=PageClasspath -jetrt=Desktop -jetvmprop=-Djet.gc.defragment:true -Dsun.java2d.noddraw:true -Djet.jit.fast -Djet.jit.disable.resolution -Djet.gc.heaplimit:0 -Djet.gc.ratio:50 -Djet.stack.trace -jpiiproject=C:\....jpn -main=... -outputdir=. ... -stacklimit=900000 ... !classpathentry C:/...netbeans/build/classes -pack=none -protect=all -optimize=all !end !classpathentry C:/.../resources -pack=none -protect=all -optimize=all !end !classpathentry C:/.../bsf-2.4.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../bsh-1.3.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../exist-modules.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../exist-optional.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../exist.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../httpunit.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../itext-1.5.2.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../jcommon-serializer-0.3.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../js-1.6R5.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../junit-3.8.1.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../libdocbundle-0.1.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../libformat-0.1.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../libloader-0.4.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../librepository-0.2.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../libxml-0.99.0.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../mail-1.4.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../nekohtml-0.9.5.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../pentaho-reporting-engine-classic-0.8.10.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../poi-3.0.1-jdk122-final-20071014.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../servlet-api-2.4.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../various-stuff.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/.../jtidy-4aug2000r7-dev.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Program Files/NetBeans 6.7/java2/modules/ext/AbsoluteLayout.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Program Files/NetBeans 6.7/platform10/modules/ext/swing-layout-1.0.3.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/FastInfoset.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/jaxrpc-api.jar -pack=all -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/jaxrpc-impl.jar -pack=all -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/jaxrpc-spi.jar -pack=all -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/saaj-impl.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/relaxngDatatype.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/Documents and Settings/root/.netbeans/6.7/modules/ext/jaxrpc16/xsdlib.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/gensearch/jar/jars-for-3.6/commons-logging.jar -pack=noncompiled -protect=nomatter -optimize=all !end !classpathentry C:/gensearch/jar/jars-for-3.6/xercesImpl291.jar -pack=noncompiled -protect=nomatter -optimize=all !end
  5. Hi, I am facing following problem: the compiled application works as compiled (just double clicking on the executable created by Excelsior JET), but when I pack it using JetPackII the length of the executable changes slightly (~1kb more): 77.5 MB (81,320,960 bytes) JETPack version 77.5 MB (81,319,936 bytes) JET Compiled version most of the app works as it supposed to, but when I try calling a web service through JAX-RPC, the packed version fails (no display of the JPanel) and the compiled version works. There is no error message generated by the Jet packed version. All the libs that are in the 'Step 3 ' of the compiler are marked as 'packed into exe' in the step 2 of Jetpack I am using JET 6.5 professional under WinXP SP3. Any ideas what I can try? Thanks David
  6. Although I am not the originator of this thread, I am facing the same issue when trying to call a web service with Axis: Exception in thread "AWT-EventQueue-0" java.lang.ExceptionInInitializerError at org.apache.axis.components.logger.LogFactory.getLog(Unknown Source) at org.apache.axis.description.OperationDesc.<clinit>(Unknown Source) at com._4d.www.namespace._default.UMD_WebServiceBindingStub._initOperationDesc1(Unknown Source) at com._4d.www.namespace._default.UMD_WebServiceBindingStub.<clinit>(Unknown Source) Here is some background: I am using the latest Jet 6.5 Professional Edition, when using the 'TEST RUN' facility in the compiler my web service call functions, when I either used the 'packaged' installed version or directly the compiled version, it gives me above error. I am running winXP Pro and writing code with Netbeans6.5. What else can I do ?
  7. Any idea when you will release 6.5? It's now mid May
  8. OK, I will try to pack something together (datafiles/software), it will take a few days as I am on the road, I hope to be able to send you something by end of this week David
  9. java version "1.6.0_03" Java 2 Runtime Environment, Standard Edition Excelsior JET 6.00: RT: Professional edition, build jet-600-release (Fr Dec 07 00:10:58 NOVT 2007) JET PRofile [1.6.0_03] Runtime: Desktop [sMP:yes, optimizations: enabled] Components: C:\Program Files\PhenoSystems\Gensearch 3.5.1\gensearch3.5.1.exe: jet-600-release (pro, en) Thanks for your help David PS: I will be travelling heavily so my feedback time will slow down, that doesn't indicate that this issue is not important
  10. Here are the results running on a JRE 1.6.0_05. 'Action 1' takes 35s on a Pentium M 1.5GHz 1GB RAM 'Action 1' takes 40s on a AMD Athlon 64x dual core4200+ 1GB RAM => roughly same time... JET Compiled: ~ 180 secs on dualcore with 6.0 and 6.0MP1 ~ 40s on dualcore with 6.4beta3 versus 35/40 sec on Pentium M with 6.0/6.0MP1/6.4b3 Can you please speed up development of 6.4b3 which seem to fix this
  11. Ok will do. I also did following test: compiled the application with 6.4beta3 and run on a dual core: it works! So what ever has changed between 6.0/6.0MP1 and 6.4beta3 seems to fix the issue. I will also run the test with the JRE and report back
  12. I checked the compiler settings, and they were on Deskop runtime. I also recompiled my application after applying the mainetance pack on 6.0, also with the Desktop runtime: still slow down effect (by this I mean 3 to 5 times slower than a single core with same frequency). This was on a Pentium D 915. I will run a few tests on various other dual cores I can lay my hand on and also try the beta version of the compiler and will report what I see.
  13. Hi, I have been using JET for a few years now for our software package and up to know had no major issues (except for memory management in the early days). Now we have a customer with a dualcore 2.79GHz HP machine and following strange behavior: our old version of the software compiled with JET 5.0 runs at normal speed our newer version, compiled with JET6.0 runs on this machine several times slower! We are not facing this issue on other PCs which are also dualcore or single core. I haven't tried 6.0MP1 yet, could this help? Has anyone else seen something like this? What would you need to help identify the source of the slow down? Thanks David
  14. Hello, I understand the previous question was whether JET compiler will run under Vista. My question, actually the question of my customers, is: do programs compiled with JET (4.5 or 4.8? ) 'normally' run on Vista? They will be getting their first machines with Vista beg. of next year and are anxious to know... thanks david
  15. yes, I did basically the same as for the crypto extension which work well...