Jump to content
Excelsior Forums


Excelsior Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About liontiger

  • Rank

Profile Information

  • Gender

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. liontiger


    Hello, Could you please send us the jet_err file, which should have been created in working directory of the application? You can send it via email to our support contact: java@excelsior-usa.com Best Regards
  2. Hello, In order to pass arguments to the multi-app program without changing default main class, you can list them after the -args parameter: start program.exe -args --Mode=1 You can read more about it in the User's Guide. Please let us know if you have any more questions.
  3. liontiger

    Documentation of xlink, xxd and xpack

    Hello Martin, There is no documentation (besides built-in help) for most of our command-line tools. Most notable exceptions are jc and xpack, which are JET compiler and JET packager respectively. The xlink tool is our linker and should not be used explicitly, thus it is not documented. As for xxd -- I have no idea, what this tool could be. Best Regards, Ivan
  4. liontiger

    Unable to run binary

    Hello Jane, Currently Excelsior JET doesn't support cross-platform builds. So in order to compile application for target Linux machine, you will need to use Excelsior JET for Linux, on a Linux building machine (either hardware or virtual machine can work). Note however, that Excelsior JET doesn't support Unix targets except for OS X. So if you are trying to compile for Unix (e.g. FreeBSD-based system), you can try compiling for Linux and running the application in Linux Binary Compatibility mode (see https://www.freebsd.org/doc/handbook/linuxemu.html). We have not tested this approach, so it may or may not work for you or target Unix system. Best Regards
  5. liontiger

    JIT cache is deprecated?

    Hi, Can you please send us the whole log with JIT-compiled classes, as well as *.vaz file. If you prefer, you can send them directly to our support contact via email: java@excelsior-usa.com
  6. liontiger

    JIT cache is deprecated?

    JIT caching was deprecated in version 8.0 of Excelsior JET and has been removed since. As for excessive JIT compilation: Could you please try specifying all dependencies' jars as `!CLASSPATHENTRY` equations? You can remove all `!module` equations as well as `-CLASSABSENCE=HANDLE` and `-IGNOREMEMBERABSENCE+` to see which dependencies are missing from compilation set. Also, have you tried using our Maven or Gradle plugins and/or Jet Control Panel tool? Best Regards, Ivan Trepakov Excelsior Support
  7. liontiger

    JET GC settings

    These options are specific to Oracle HotSpot and its GC. Excelsior JET has its own Garbage Collector with its own set of options that cannot be mapped to or from HotSpot ones. So you can remove all of the -XX options and see if your application works fine on our GC. If after that your application will require any tuning you will have to do it using properties described in Excelsior JET User's Guide: https://www.excelsiorjet.com/docs/jet/jetw010#0321
  8. liontiger

    Long command line cannot copy paste

    If that's the case, please try using our JET Launcher tool by replacing "java" in your command line with "<JET Home>/profile1.8.0_121/jre/bin/java" where <JET Home> is the full path to your Excelsior JET installation directory. The resulting command line will look like this: <JET Home>/profile1.8.0_121/jre/bin/java -noverify -Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8091,s uspend=n -Xms=8G -Xmx=8G -Xmn2G -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/tmp -XX:CompileThre shold=1000 -XX:+UseCompressedOops -XX:ErrorFile=/var/log/hs_err_pid%p.log -XX:SurvivorRatio=3 -XX:+UseLargePages -XX:+UseTLAB -X X:TargetSurvivorRatio=90 -XX:+AlwaysPreTouch -XX:+AggressiveOpts -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:ParallelCMSThreads =4 -XX:CMSWaitDuration=90000 -XX:CMSInitiatingOccupancyFraction=10 -XX:+UseCMSInitiatingOccupancyOnly -Xloggc:$LOGDIR/gc.log -ve rbose:gc -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=12 -XX:GCLogFileSize=100M -XX:+PrintGCDetails -XX:+PrintGCDateStamps - XX:+PrintGCTimeStamps -XX:+PrintTenuringDistribution -XX:MaxMetaspaceSize=512m -XX:MaxDirectMemorySize=1024G -Dcom.sun.managemen t.jmxremote.port=18091 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false This will create a new JET project with specified arguments in JET Control Panel.
  9. liontiger

    Long command line cannot copy paste

    Does it work if you save your command line into a text file, open it in GUI text editor like JEdit or similar, and then try to copy the text from this editor to JET Control Panel? -- Ivan
  10. liontiger

    Long command line cannot copy paste

    Hello, Can you elaborate which operating system you are using and from where and to where you are trying to copy-paste the line (e.g. from terminal to JET Control Panel "Command line:" text box while creating "Plain Java SE Application")? Best Regards, Ivan Trepakov
  11. liontiger

    Load external configuration file

    Just to reiterate what has been discussed with @AndyDenby over email and to provide a public statement on this issue: It is highly discouraged to manually alter `java.class.path` property. If you will attempt to do it, you must provide ALL dependencies explicitly in that class path. So for this particular case the suggested workaround is: 1. Remove altering of `java.class.path` from `jvmArgs` configuration. Gradle plugin will handle adding all dependencies into class path on its own. 2. Exclude packaged configs (which you want to change after deployment) from created .jar file using following configuration: jar { exclude('config') } Assuming that all packaged config files are located in 'config' directory inside of .jar. The reason for such workaround is that Gradle plugin currently searches import class path entries before external class path entries, so if you don't exclude configs from .jar, JVM will find them in resources of compiled .jar file instead of your packaged external configs. There is a ticket in Excelsior JET Gradle plugin's bug tracker to add proper support for modification of `java.class.path` - https://github.com/excelsior-oss/excelsior-jet-gradle-plugin/issues/36
  12. liontiger

    Natively Compile a Spring Boot Application

    Hello, Could you please try compiling your .java files using `-parameters` argument for the javac and check if this helps?