VisualVM - not supported JVM

Hello Community,
   Related to this post: https://forums.oracle.com/message/4800072
I thought I'd start a new thread since I can't comment the one above.
1) I have visualvm *32 install
2) Monitoring a 64 bit jvm app locally
3) Changed "visualvm.conf" jdk home to 64 bit 1.7
4) I still get the same issue.
Summary
Version:
1.3.5 (Build 121105); platform 20120926-d0f92ba97f49
System:
Windows 7 (6.1) Service Pack 1, amd64 64bit
Java:
1.7.0_04; Java HotSpot(TM) 64-Bit Server VM (23.0-b21, mixed mode)
Vendor:
Oracle Corporation, http://java.oracle.com/
Environment:
Cp1252; en_US (visualvm)
User directory:
C:\Users\trx\AppData\Roaming\VisualVM\1.3.5
Cache directory:
C:\Users\trx\AppData\Local\VisualVM\Cache\1.3.5
Clusters:
C:\visualvm_135\platform
C:\visualvm_135\visualvm
C:\visualvm_135\profiler
Any thoughts on resolving this issue?
Thanks in advance.
TRX

Hi,
as you can see, you are running VisualVM on 32bit JVM
1.6.0_20; Java HotSpot(TM) Client VM (16.3-b01, mixed mode, sharing)
You don't need to unistall 32bit JVM. Just tell VisualVM to use tour 64bit JVM.
One way is to use --jdkhome command-line switch.
visualvm_13\bin\visualvm.exe --jdkhome <path_to_64bit_JVM>
If you want to change it permanently, you can edit
visualvm_13\etc\visualvm.conf
uncomment and edit netbeans_jdkhome entry to point to your 64bit JVM.
HTH,
Tom

Similar Messages

  • The Oracle JRockit JVM is not supported by SAP JCo 3.0.5.

    Hello all,
    I am preparing our new Oracle Fusion Middleware platforms. So far we have been running BPEL 10.1.3.4.0 and we are going to build the 11g platform (WLS and SOA suite) in parallel.
    I have already installed WLS Server 10.3.3 and then SOA Suite + the SOA patchset bu selecting always Jrockit_160_17_R28.0.0-679.
    Now I am abaout to install the adapters and I red in the documentation
    http://download.oracle.com/docs/cd/E14571_01/doc.1111/e17054/intro.htm
    For supported JVM information that corresponds to each operating system, see the SAP Note #1077727 in the SAP Service Marketplace.
    Note:
    The Oracle JRockit JVM is not supported by SAP JCo 3.0.5.
    Is anybody aware of this? If it is valid, how could I achieve not to re-installa everything from scratch and select SUN JVM?
    Could I for example create a new Managed Server where I will explicity select SUN JVM to be installed for this instance?
    Best Regards,
    Loukas Rougkalas

    Please post your question to SOA forum. This forum is about WebLogic Connector Container.

  • Running a 64-bit JVM is not supported on this platform.error on DAC install

    Hi Friends,
    I am getting the error while installating DAC server on RHEL5.4(64 bit)
    Running a 64-bit JVM is not supported on this platform.
    What is the fix?
    Regards,
    DB

    I have tried that but run into issues too... are you installing DAC directly on Linux 64 from installer or copying over from Windows binaries of DAC?

  • JVM Vendor not supported error in NWDS.

    I installed the NWDS 7.3 for customizing my portal 7.3 logon page. I am following an interesting blog for the same: Getting started with Netweaver 7.3 portal Part 2 - NWDS and Logon Page
    However I am yet to complete this task successfully due to a JVM vendor not supported error. I have a JAVA_HOME entry to the javaw.exe path. Also, i have vm entry of the same path in the NWDS shortcut- properties- target value. C:Program Files (x86)Javajdk1.7.0_02 in
    I chose program files (x86) for this installation bcos during my previous java error i read in my log that JVM 64 bit could not be run.
    Initially i use to get JVM error during startup itself bcos of which i was not able to get to the home page of developer studio. I solved that error now by installing right version and making necessary entries as mentioned above. Now i get a pop up stating that oracle vendor is not supported (it says that i should have either a Sun or SAP provided java). Is it really the problem? If so, can some 1 get me the link to download it.
    I am creating a new thread since the old ones posted by others on the same topic does not give me the solution.
    Thanks in advance

    Hi,
    I also come to this warning. I did a little research, and found solution that worked for me by solving source of problem, without need of trying different JDK versions.
    My current configuration:
    SAP NWDS:
         - v7.30 EHP1 (7.31) SP10 PAT0001 (8.31.100001.140103092401 SP10 PAT0001)
         - file: "nwds-extsoa-7.3-EHP1-SP10-PAT0001-win32.zip"
         - Download location: https://nwds.sap.com/swdc/downloads/updates/netweaver/nwds/nw/731/doc/auto_latest_distributions.html
    JDK:
         - v7 Update 51 - both x86 and x64 versions. As NWDS is x86 version, that platfotm is enought if you don't need native support for x64 applications.
         - Latest version download location: http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html
         - Older versions download location: http://www.oracle.com/technetwork/java/javase/archive-139210.html
         - I'm not suggesting that you need to install last version. I tested it on this version and it worked for me, but I use NWDS only for few specific tasks. So I did't test all functions for JVM compatibility. But my solution should work for solving cause of vendor specific problem. Not other JVM problems. And installing newer Java may be source of other problems, like is every release. But with correct backup there shouldn't be a problem.
    Problem:
    Problem is in older code of initial JVM check, where are specified allowed vendors. Oracle is not included in configuration, so warning is shown. Module is located in plugins folder:
         "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
    Version number (orange) can differs based on NWDS distribution. In jar file is configuration stored in file "config.xml". There is this part, that specifies allowed vendors:
    <supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
          <vendor name="SAP AG">
              <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
          </vendor>
          <vendor name="Sun Microsystems Inc.">
              <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
          </vendor>
      </supportedRuntimes
    Here you can see that only "SAP AG" and "Sun Microsystems Inc." from older Java releases are included. And that's the problem, as new versions are released by Oracle. So vendor differs and warning is here.
    Solution:
    Before we begin it's best to backup whole NWDS directory and also workspace(s)!
    1) Locate file with JVM checking module:
         "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
        As mentioned before, version number can be different in your release.
    2) Create backup copy of current file. Call it for example "com.sap.ide.jvm.check_1.0.0.140103091951.jar.BAK".
    3) Copy original file to temporary location. I used "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951.jar"
    4) Extract files from JAR. JAR files are basically ZIP files. I used 7-zip program to extract source to folder based on file name:
    "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\".
    5) Locate and edit configuration file "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\config.xml". Add vendor node "Oracle Corporation" (part in green color). Just copy existing node and replace vendor name.
    <supportedRuntimes shutdownIfNotMatches="false" warnIfNotMatches="true">
        <vendor name="SAP AG">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
        <vendor name="Sun Microsystems Inc.">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
        <vendor name="Oracle Corporation">
            <versionRange jdkRequired="true" minInclusive="1.6.0_07"/>
        </vendor>
    </supportedRuntimes>
    6) Pack directory. Pack whole content of directory from step 5) back to ZIP format. Change extension to .JAR in your favorite compression program, or rename new file from ".zip" to ".jar" after compression is done. Now we have our new corrected file for checking JVM version in NWDS - "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar".
    7) Replace original file. Copy file over original one:
    "C:\Temp\com.sap.ide.jvm.check_1.0.0.140103091951\com.sap.ide.jvm.check_1.0.0.140103091951.jar" -->
    "<SAP NWDS>\plugins\com.sap.ide.jvm.check_1.0.0.140103091951.jar". Overwrite if asked.
    8) Done.

  • JVM not supporting swing

    hey i have a problem i have downloaded a JVM for XP window but its not supporting swing compenent while compilation in jdk1.3
    Tell me how to solve this

    Exactly what JVM did you download? And where did you download it from?

  • Scrollable resultsets are not supported in my application

    I want to use scrollable resultsets.But when i am writing the code
    Class.forName("sun.jdbc.odbc.JdbcOdbcDriver");
              String url = "jdbc:odbc:pmora";
              Connection con = DriverManager.getConnection(url,
    "jbel", "jbel");
              Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE,
    ResultSet.CONCUR_READ_ONLY);
    ResultSet srs = stmt.executeQuery(
    "SELECT COF_NAME, PRICE FROM COFFEES");
    while (srs.next()) {
         String name = srs.getString("COF_NAME");
         float price = srs.getFloat("PRICE");
         System.out.println(name + " " + price);
    To get support for scrollable resultsets, what driver we should use?Where we can get it?
    #database is oracle 8
    #driver version 2
    #jdbcodbcbridgedriver
    #While running the class, The followingmessage is getting displayed
    Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D366658
    Function=[Unknown.]
    Library=D:\j2sdk1.4.0_01\jre\bin\client\jvm.dll
    NOTE: We are unable to locate the function name symbol for the error
    just occurred. Please refer to release documentation for possible
    reason and solutions.
    Current Java thread:
         at sun.jdbc.odbc.JdbcOdbc.setStmtAttrPtr(Native Method)
         at sun.jdbc.odbc.JdbcOdbc.SQLSetStmtAttrPtr(JdbcOdbc.java:4676)
         at sun.jdbc.odbc.JdbcOdbcResultSet.setRowStatusPtr(JdbcOdbcResultSet.java:4473)
         at sun.jdbc.odbc.JdbcOdbcResultSet.initialize(JdbcOdbcResultSet.java:171)
         at sun.jdbc.odbc.JdbcOdbcStatement.getResultSet(JdbcOdbcStatement.java:423)
         - locked <02A3D7F0> (a sun.jdbc.odbc.JdbcOdbcStatement)
         at sun.jdbc.odbc.JdbcOdbcStatement.executeQuery(JdbcOdbcStatement.java:253)
         at ScrollableRS.main(ScrollableRS.java:27)
    Dynamic libraries:
    0x00400000 - 0x00406000      D:\j2sdk1.4.0_01\bin\java.exe
    0x77F50000 - 0x77FF9000      C:\WINNT\System32\ntdll.dll
    0x77E60000 - 0x77F45000      C:\WINNT\system32\kernel32.dll
    0x77DD0000 - 0x77E5B000      C:\WINNT\system32\ADVAPI32.dll
    0x77CC0000 - 0x77D35000      C:\WINNT\system32\RPCRT4.dll
    0x77C10000 - 0x77C63000      C:\WINNT\system32\MSVCRT.dll
    0x6D330000 - 0x6D445000      D:\j2sdk1.4.0_01\jre\bin\client\jvm.dll
    0x77D40000 - 0x77DCD000      C:\WINNT\system32\USER32.dll
    0x77C70000 - 0x77CB0000      C:\WINNT\system32\GDI32.dll
    0x76B40000 - 0x76B6C000      C:\WINNT\System32\WINMM.dll
    0x6D1D0000 - 0x6D1D7000      D:\j2sdk1.4.0_01\jre\bin\hpi.dll
    0x6D300000 - 0x6D30D000      D:\j2sdk1.4.0_01\jre\bin\verify.dll
    0x6D210000 - 0x6D228000      D:\j2sdk1.4.0_01\jre\bin\java.dll
    0x6D320000 - 0x6D32D000      D:\j2sdk1.4.0_01\jre\bin\zip.dll
    0x6D250000 - 0x6D25A000      D:\j2sdk1.4.0_01\jre\bin\JdbcOdbc.dll
    0x1F7B0000 - 0x1F7E1000      C:\WINNT\System32\ODBC32.dll
    0x77340000 - 0x773CB000      C:\WINNT\system32\COMCTL32.dll
    0x763B0000 - 0x763F5000      C:\WINNT\system32\comdlg32.dll
    0x772D0000 - 0x77333000      C:\WINNT\system32\SHLWAPI.dll
    0x773D0000 - 0x77BC4000      C:\WINNT\system32\SHELL32.dll
    0x71950000 - 0x71A34000      C:\WINNT\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.0.0_x-ww_1382d70a\comctl32.dll
    0x1F850000 - 0x1F866000      C:\WINNT\System32\odbcint.dll
    0x0AF30000 - 0x0AF99000      E:\Oracle\Ora81\BIN\SQORA32.DLL
    0x60600000 - 0x60682000      E:\Oracle\Ora81\BIN\oracore8.dll
    0x60800000 - 0x60848000      E:\Oracle\Ora81\BIN\oranls8.dll
    0x10000000 - 0x1001A000      E:\Oracle\Ora81\BIN\OCI.dll
    0x0B0B0000 - 0x0B0BF000      E:\Oracle\Ora81\bin\sqresUS.dll
    0x60400000 - 0x60502000      E:\Oracle\Ora81\bin\OraClient8.Dll
    0x0B1D0000 - 0x0B1D6000      E:\Oracle\Ora81\bin\oravsn8.dll
    0x60200000 - 0x60264000      E:\Oracle\Ora81\bin\oracommon8.dll
    0x60000000 - 0x6011F000      E:\Oracle\Ora81\bin\orageneric8.dll
    0x60350000 - 0x60356000      E:\Oracle\Ora81\bin\orawtc8.dll
    0x60A00000 - 0x60A2B000      E:\Oracle\Ora81\bin\oranl8.dll
    0x60B00000 - 0x60BAA000      E:\Oracle\Ora81\bin\oran8.dll
    0x60E00000 - 0x60E10000      E:\Oracle\Ora81\bin\orancrypt8.dll
    0x61100000 - 0x61137000      E:\Oracle\Ora81\bin\oranro8.dll
    0x71AD0000 - 0x71AD8000      C:\WINNT\system32\WSOCK32.dll
    0x71AB0000 - 0x71AC5000      C:\WINNT\system32\WS2_32.dll
    0x71AA0000 - 0x71AA8000      C:\WINNT\system32\WS2HELP.dll
    0x0B1E0000 - 0x0B23E000      E:\Oracle\Ora81\bin\orannzsbb8.dll
    0x61500000 - 0x6150E000      E:\Oracle\Ora81\bin\oranldap8.dll
    0x61700000 - 0x6171C000      E:\Oracle\Ora81\bin\oraldapclnt8.dll
    0x771B0000 - 0x772CA000      C:\WINNT\system32\ole32.dll
    0x77120000 - 0x771AB000      C:\WINNT\system32\OLEAUT32.dll
    0x61900000 - 0x61906000      E:\Oracle\Ora81\bin\oranhost8.dll
    0x62100000 - 0x62106000      E:\Oracle\Ora81\bin\oranoname8.dll
    0x0B240000 - 0x0B246000      E:\Oracle\Ora81\bin\orancds8.dll
    0x62300000 - 0x62306000      E:\Oracle\Ora81\bin\orantns8.dll
    0x62500000 - 0x62508000      E:\Oracle\Ora81\bin\orannds8.dll
    0x0B250000 - 0x0B26C000      E:\Oracle\Ora81\bin\orannms8.dll
    0x62700000 - 0x62741000      E:\Oracle\Ora81\bin\ORATRACE8.dll
    0x62900000 - 0x62B1B000      E:\Oracle\Ora81\bin\orapls8.dll
    0x63100000 - 0x63108000      E:\Oracle\Ora81\bin\oraslax8.dll
    0x63200000 - 0x63272000      E:\Oracle\Ora81\bin\orasql8.dll
    0x1F800000 - 0x1F818000      C:\WINNT\System32\odbccp32.dll
    0x77C00000 - 0x77C07000      C:\WINNT\system32\VERSION.dll
    0x71A50000 - 0x71A8B000      C:\WINNT\System32\mswsock.dll
    0x76F20000 - 0x76F45000      C:\WINNT\System32\DNSAPI.dll
    0x76D60000 - 0x76D75000      C:\WINNT\System32\iphlpapi.dll
    0x76DE0000 - 0x76E06000      C:\WINNT\System32\netman.dll
    0x76D40000 - 0x76D56000      C:\WINNT\System32\MPRAPI.dll
    0x76E40000 - 0x76E6F000      C:\WINNT\System32\ACTIVEDS.dll
    0x76E10000 - 0x76E34000      C:\WINNT\System32\adsldpc.dll
    0x71C20000 - 0x71C6F000      C:\WINNT\system32\NETAPI32.dll
    0x76F60000 - 0x76F8C000      C:\WINNT\system32\WLDAP32.dll
    0x76B20000 - 0x76B35000      C:\WINNT\System32\ATL.DLL
    0x76E80000 - 0x76E8D000      C:\WINNT\System32\rtutils.dll
    0x71BF0000 - 0x71C01000      C:\WINNT\System32\SAMLIB.dll
    0x76670000 - 0x76754000      C:\WINNT\System32\SETUPAPI.dll
    0x76EE0000 - 0x76F17000      C:\WINNT\System32\RASAPI32.dll
    0x76E90000 - 0x76EA1000      C:\WINNT\System32\rasman.dll
    0x76EB0000 - 0x76EDA000      C:\WINNT\System32\TAPI32.dll
    0x76F90000 - 0x76FA0000      C:\WINNT\System32\Secur32.dll
    0x76DA0000 - 0x76DD0000      C:\WINNT\System32\WZCSvc.DLL
    0x76D30000 - 0x76D34000      C:\WINNT\System32\WMI.dll
    0x76D80000 - 0x76D9A000      C:\WINNT\System32\DHCPCSVC.DLL
    0x762C0000 - 0x7634A000      C:\WINNT\system32\CRYPT32.dll
    0x762A0000 - 0x762AF000      C:\WINNT\system32\MSASN1.dll
    0x76F50000 - 0x76F58000      C:\WINNT\System32\WTSAPI32.dll
    0x76360000 - 0x7636F000      C:\WINNT\System32\WINSTA.dll
    0x76FB0000 - 0x76FB7000      C:\WINNT\System32\winrnr.dll
    0x76FC0000 - 0x76FC5000      C:\WINNT\System32\rasadhlp.dll
    0x64700000 - 0x6470C000      E:\Oracle\Ora81\bin\orantcp8.dll
    0x71A90000 - 0x71A98000      C:\WINNT\System32\wshtcpip.dll
    0x64500000 - 0x6450D000      E:\Oracle\Ora81\bin\orannts8.dll
    0x71F80000 - 0x71F84000      C:\WINNT\System32\security.dll
    0x76C90000 - 0x76CB2000      C:\WINNT\system32\imagehlp.dll
    0x6D510000 - 0x6D58C000      C:\WINNT\system32\DBGHELP.dll
    0x76BF0000 - 0x76BFB000      C:\WINNT\System32\PSAPI.DLL
    Local Time = Thu May 15 14:59:26 2003
    Elapsed Time = 5
    # HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
    # Error ID : 4F530E43505002D5
    # Please report this error at
    # http://java.sun.com/cgi-bin/bugreport.cgi
    # Java VM: Java HotSpot(TM) Client VM (1.4.0_01-b03 mixed mode)

    You definitely don't need to be using the Sun JDBC-ODBC driver, as this will not support scrollable ResultSets. There are several drivers out there that do, ... for a list of drivers check out
    http://industry.java.sun.com/products/jdbc/drivers

  • Native VM not supported error when start WebLogic Server on Solaris

    I created a weblogic domain and server using configuration wizard from workshop 8.1, the JVM is jdk142_05. When I start weblogic server, get follwing error: native VM not supported. The enviroment is
    Solaris.
    We used the same jdk started medrec example without problem. Any idea for the possible cause?
    Thank any one who can help.
    Zhong
    uberpeer% ./startWebLogic.sh
    JAVA Memory arguments: -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m
    WLS Start Mode=Development
    CLASSPATH=:/rg2/opt/bea/weblogic81/server/lib/weblogic_knex_patch.jar:/rg2/opt/bea/weblogic81/common/lib/log4j.jar:/rg2/opt/bea/weblogic81/server/lib/debugging.jar:/rg2/opt/bea/weblogic81/server/lib/knex.jar:/rg2/opt/bea/weblogic81/javelin/lib/javelin.jar:/rg2/opt/bea/weblogic81/server/lib/wlw-lang.jar:/rg2/opt/bea/jdk142_05/lib/tools.jar:/rg2/opt/bea/weblogic81/server/lib/weblogic_sp.jar:/rg2/opt/bea/weblogic81/server/lib/weblogic.jar:/rg2/opt/bea/weblogic81/server/lib/ant/ant.jar:/rg2/opt/bea/jdk142_05/jre/lib/rt.jar:::/rg2/opt/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/rg2/opt/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/rg2/opt/bea/weblogic81/server/lib/webserviceclient.jar:/rg2/opt/bea/weblogic81/server/lib/webserviceclient+ssl.jar:/rg2/opt/bea/weblogic81/server/lib/xbean.jar:/rg2/opt/bea/weblogic81/server/lib/wlxbean.jar:/rg2/opt/bea/weblogic81/server/lib/xqrl.jar:/rg2/opt/bea/weblogic81/server/lib/netui/netui-compiler.jar:/rg2/opt/bea/weblogic81/server/lib/wli.jar:/rg2/opt/bea/weblogic81/server/lib/fop.jar:/rg2/opt/bea/weblogic81/integration/adapters/sample/lib/sample-eis.jar:
    PATH=/rg2/opt/bea/weblogic81/server/bin:/rg2/opt/bea/jdk142_05/jre/bin:/rg2/opt/bea/jdk142_05/bin:/opt/bea/weblogic700/server/lib/solaris:/opt/bea/jdk131_03/jre/bin:/opt/bea/jdk131_03/bin:/rg1/users/zhongw/weblogic/PMDomain:/rg2/opt/bea/weblogic81/workshop:/rg1/users/zhongw/bin:/bin:/usr/bin:/usr/sbin:/usr/java/bin:/usr/openwin/bin:/opt/local/bin:/usr/ccs/bin:/usr/per15/bin:/usr/local/SUNWspro/bin:/usr/local/accurev/bin:/opt/jakarta-ant/bin:/usr/local/accurev/bin:/usr/ccs/bin:/usr/local/bin:/opt/enJin/2.3.1/bin:/usr/java/bin:/usr/openwin/bin:/usr/dt/bin:/rg1/users/zhongw/Borland/JBuilder2005/bin
    * To start WebLogic Server, use a username and *
    * password assigned to an admin-level user. For *
    * server administration, use the WebLogic Server *
    * console at http://hostname:port/console *
    starting weblogic with Java version:
    java version "1.4.2_05"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
    Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
    Starting WLS with line:
    /rg2/opt/bea/jdk142_05/bin/java -client -Xms256m -Xmx256m -XX:CompileThreshold=8000 -XX:PermSize=32m -XX:MaxPermSize=128m -native -Xverify:none -da -Dplatform.home=/rg2/opt/bea/weblogic81 -Dwls.home=/rg2/opt/bea/weblogic81/server -Dwli.home=/rg2/opt/bea/weblogic81/integration -Dlog4j.configuration=file:/rg2/opt/bea/weblogic81/common/lib/workshopLogCfg.xml -Dweblogic.management.discover=true -Dweblogic.ProductionModeEnabled= -Dweblogic.security.SSL.ignoreHostnameVerify=false -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.Name=cgServer -Djava.security.policy=/rg2/opt/bea/weblogic81/server/lib/weblogic.policy weblogic.Server
    Error: native VM not supported
    Stopping Pointbase server...
    Pointbase server stopped.

    I believe this is the error you get when you try to start up a JVM with the commandline option '-native'.
    Remove this flag from your startup script and retry.
    By the way, it may be that you have the environment variable 'JAVA_OPTIONS' set to '-native' in which case:
    (first confirm this is the case)
    $ echo $JAVA_OPTIONS
    -native
    (Then edit the startup script if you get the result above)
    add in a line:
    # To remove '-native' flag
    unset JAVA_OPTIONS
    and retry.
    I have to confess I don't know what the '-native' flag is actually supposed to do, but my JVM also reports back that this is unsupported.

  • Linux AMD64: Error: hotspot VM not supported

    I have installed JDeveloper 10.1.3.1 on an AMD64 Linux (gentoo) as well as Sun's JDK 1.5.0.10. When I try to start jdev I get the following messages:
    $ jdev
    u01/oracle/product/jdev/jdev/bin
    Oracle JDeveloper 10g 10.1.3.1
    Copyright 1997, 2006 Oracle. All Rights Reserved
    Error: hotspot VM not supported
    Error: JDeveloper can't recognize the JDK version
    I have found that I can make jdev start up if I edit /opt/sun-jdk-1.5.0.10/jre/lib/amd64/jvm.cfg and change the line saying:
    -hotspot ERROR
    to:
    -hotsport IGNORE
    - but according to documentation in other places I am supposed to be able to use the HotSpot VM. How do I get this to work?

    Have you seen this 10.1.3.1 with Fedora Core 5 and AMD 64 post? It seems to indicate that the 64 bit JVM hotspot may not work.
    John

  • JDK is NOT supported for 7.1 anymore?

    I get the info that for whatever 7.1 (e.g. PI7.1, BI7.1, etc.),  JDK is NOT supported anymore.
    SAP JVM is installed during the upgrade to 7.1 .
    Is that true?    Thanks!!

    Hi Ashley,
    This is true. You can refer the same in product availability matrix (PAM) under https://service.sap.com/pam
    Cheers........,
    Raghu

  • OracleXMLSQLException: 6-byte UTF8 encoding not supported

    Hi,
    I am trying to upload XML data through the Oracle XML SQL Utility (XSU). I am running JDK 1.3.1 on the Windows client and 8.1.6 on the Solaris server. Now this works fine, but when the XML data contains German umlauts (dv|), I get the following exception:
    oracle.xml.sql.OracleXMLSQLException: 6-byte UTF8 encoding not supported.
         at oracle.xml.sql.dml.OracleXMLSave.saveXML(OracleXMLSave.java:2093)
         at oracle.xml.sql.dml.OracleXMLSave.insertXML(OracleXMLSave.java:1101)
    Since our database stores Umlauts (also through JDBC), I assume this has to do either with my client JVM or the Oracle libraries (xsu12.jar or xmlparserv2.jar)
    This is quite important to our project and as I don't know how to proceed, any help or suggestion is greatly appreciated.
    Thanks,
    Heiko

    Which version of XSU do you use? Would you send the sample data?

  • Wlwbuild task not supported?

    Sorry for the crosspost - but I don't think many JRockit peopple hang out in the
    .workshop group.
    In an attempt to speed up our build, we have tried out using the JRockit JVM for
    ant. However, we were foiled by the wlwbuild task - it insists on invoking java
    with the argument -XX:-UseThreadPriorities, which is not supported by JRockit.
    We get:
    [wlwBuild] Unknown option or illegal argument: -XX:-UseThreadPriorities. [wlwBuild]
    Could not create the Java virtual machine. [wlwBuild] Please check for incorrect
    spelling or review documentation of start up options.
    BUILD FAILED file:C:/pfa_portal/src/PortalApplication/wlwbuild.xml:80: Java returned:
    1 at org.apache.tools.ant.taskdefs.Java.execute()V(Java.java:110) at workshop.core.WlwBuildTask.execute()V(WlwBuildTask.java:141)
    at org.apache.tools.ant.Task.perform()V(Task.java:341) at org.apache.tools.ant.Target.execute()V(Target.java:309)
    at org.apache.tools.ant.Target.performTasks()V(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Proje
    ct.java:1339) at org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Proj
    ect.java:1255) at org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.jav
    a:609) at org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Propert
    ies;Ljava.lang.ClassLoader;)V(Main.java:196) at org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235)
    Any suggestions would be most welcome. Should we try to override the ant java
    task to ignore the option? Or is there a simpler fix?
    I'm also considering to polish up on my C skills to write my own java.exe which
    just strips out offending options, add a few JRockIt specific ones and calls JRockit.
    Would this be a feasable way?

    Looks like there is no easy way - I had a look at the code for the
    wlwBuild task and it looks like the WLW people have indeed hardcoded
    that option.
    I don't know enough about ant to know if it is possible to override the
    task and remove the argument.
    Writing a custom java.exe should work. Here is some code that could get
    you started:
    http://java.sun.com/j2se/1.4.2/docs/guide/jni/spec/invocation.html
    Sorry for this inconvenience,
    /Staffan
    Niels Harremoes wrote:
    Sorry for the crosspost - but I don't think many JRockit peopple hang out in the
    workshop group.
    In an attempt to speed up our build, we have tried out using the JRockit JVM for
    ant. However, we were foiled by the wlwbuild task - it insists on invoking java
    with the argument -XX:-UseThreadPriorities, which is not supported by JRockit.
    We get:
    [wlwBuild] Unknown option or illegal argument: -XX:-UseThreadPriorities. [wlwBuild]
    Could not create the Java virtual machine. [wlwBuild] Please check for incorrect
    spelling or review documentation of start up options.
    BUILD FAILED file:C:/pfa_portal/src/PortalApplication/wlwbuild.xml:80: Java returned:
    1 at org.apache.tools.ant.taskdefs.Java.execute()V(Java.java:110) at workshop.core.WlwBuildTask.execute()V(WlwBuildTask.java:141)
    at org.apache.tools.ant.Task.perform()V(Task.java:341) at org.apache.tools.ant.Target.execute()V(Target.java:309)
    at org.apache.tools.ant.Target.performTasks()V(Target.java:336) at org.apache.tools.ant.Project.executeTarget(Ljava.lang.String;)V(Proje
    ct.java:1339) at org.apache.tools.ant.Project.executeTargets(Ljava.util.Vector;)V(Proj
    ect.java:1255) at org.apache.tools.ant.Main.runBuild(Ljava.lang.ClassLoader;)V(Main.jav
    a:609) at org.apache.tools.ant.Main.start([Ljava.lang.String;Ljava.util.Propert
    ies;Ljava.lang.ClassLoader;)V(Main.java:196) at org.apache.tools.ant.Main.main([Ljava.lang.String;)V(Main.java:235)
    Any suggestions would be most welcome. Should we try to override the ant java
    task to ignore the option? Or is there a simpler fix?
    I'm also considering to polish up on my C skills to write my own java.exe which
    just strips out offending options, add a few JRockIt specific ones and calls JRockit.
    Would this be a feasable way?

  • Character format 'utf-8' not supported by your Java VM

    Hi All,
    I am Getting "Character format 'utf-8' not supported by your Java VM"  warning in Java Message monitoring also when I click view source on MainDocument (to view payload)it display as Chinese like character.
    Regards,
    Mani

    Hi Mani
    Are you using any custom module to generate the encoding in PI?
    UTF-8 should supported be by JVM.
    Is this the first time you are using this system?
    Is it happening with all the interfaces or for only this one?

  • Cache "dist-test" does not support pass-through optimization

    I have noticed this message in the log of my Extend proxy JVM. It is logged at INFO level.
    The cache dist-test does not support pass-through optimization for objects in internal format. If possible, consider using a different cache topology.
    The Extend proxy JVM is running as a storage disabled node of the cluster.
    Any ideas what is causing it?
    dist-test is configured like this:
      <caching-scheme-mapping>
        <cache-mapping>
          <cache-name>dist-*</cache-name>
          <scheme-name>near-entitled-scheme</scheme-name>
        </cache-mapping>
      </caching-scheme-mapping>
      <caching-schemes>
        <near-scheme>
          <scheme-name>near-entitled-scheme</scheme-name>
          <front-scheme>
            <local-scheme>
              <eviction-policy>HYBRID</eviction-policy>
              <high-units>1000</high-units>
            </local-scheme>
          </front-scheme>
          <back-scheme>
            <distributed-scheme>
              <scheme-ref>dist-default</scheme-ref>
            </distributed-scheme>
          </back-scheme>
        </near-scheme>
        <distributed-scheme>
          <scheme-name>dist-default</scheme-name>
          <serializer>
            <class-name>com.tangosol.io.pof.ConfigurablePofContext</class-name>
          </serializer>
          <lease-granularity>member</lease-granularity>
          <backing-map-scheme>
            <local-scheme>
              <listener>
                <class-scheme>
                  <class-name>{backing-map-listener-class-name com.oracle.coherence.common.backingmaplisteners.NullBackingMapListener}</class-name>
                  <init-params>
                    <init-param>
                      <param-type>com.tangosol.net.BackingMapManagerContext</param-type>
                      <param-value>{manager-context}</param-value>
                    </init-param>
                  </init-params>
                </class-scheme>
              </listener>
            </local-scheme>
          </backing-map-scheme>
          <autostart>true</autostart>
        </distributed-scheme>
      </caching-schemes>I presume it is something to do with the near-scheme because I do not see the message if I map dist-* caches directly to the dist-default scheme
    Cheers,
    JK.

    Hi Jonathan,
    You are getting the warning because a near cache caches Objects. Since the the proxy service is using POF, it must deserialize the POF serialized value in order to put it in the near cache. You don't see the message when you cache directly to the dist-default scheme because that scheme is configured to use POF, which allows the proxy service to pass the POF serialized value directly through to the distributed cache service.
    Thanks,
    Tom

  • Upload Error message: HTTPS protocol is not supported

    Hi,
       Whenever I do a quick par upload i'm getting an 'Operation failed' message to check sap-plugin.log.
       Log says
    Upload Error message: HTTPS protocol is not supported, please ensure this server is not using HTTPS. My webdynpro applications are getting deployed without any issues.
         How to resolve this?
    Thanks
    Sumathi

    Hi Sumathi,
    As there are often problems with the Quick PAR Upload reported, I would suggest to use the "normal" PAR upload from the icon tray (you have to activate the portal icons in the icon tray). That is almost that "quick" (one or two clicks more needed, we don't talk about more than a second) and - it works (it least it should, and at least it works in most cases even if the Quick PAR Upload fails).
    Hope it helps
    Detlev

  • MacBook Mini-DVI to VGA - Samsung 32" LCD - Mode Not Supported

    I followed the instructions on Apple's site to use the MacBook with the lid closed and an external LCD. It worked perfectly the first time I tried it. (I believe in 1920 x 1024). It seemed a little hard to read so I changed the Display resolution, then encountered the "Mode Not Supported" on my LCD. I unhooked and used my MacBook to change the settings back, but the MacBook seems to revert to the "Mode Not Supported" resolution when I close the lid. Any suggestions? Can I reset the Display Preferences on my MacBook?

    I think this procedure should work, but it requires an external USB keyboard.
    - Shut down the Mac.
    - Have all the following connected:
    - MacBook power supply
    - External display
    - USB keyboard and mouse
    - Open the lid on the MacBook and hit the power button.
    - Immediately close the lid on the MacBook and start holding down the Shift key on the USB keyboard.
    - Release the Shift key once you see the spinning gear on the gray screen on the external display.
    The above procedure should cause the Mac to start in Safe mode and hopefully will finish booting into a useable screen. If that is the case, go into Displays preferences and select a known working resolution different from the one the Mac started up in under Safe mode. Now restart normally. Hopefully the newly selected resolution will persist through the normal restart and you will have a working external screen again.

Maybe you are looking for