facebook

WebSphere 6.1 Generic JVM argument not loaded on startup

  1. MyEclipse Archived
  2.  > 
  3. Application Servers and Deployment
Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #279422 Reply

    elm3d
    Member

    I’ve run into an issue with the WebSphere 6.1 Connector for MyEclipse. I followed the directions for the MyEclipse WAS 6.0 Tutorial to set up my websphere connector and can successfully perform hot deploys on an EJB project. However when my application tries to start up a MDB that references the System Property configFilePath it always returns a Null. I’ve placed the argument -DconfigFilePath=C:\Path in the Application Servers >server1>Process Definition > Java Virtual Machine, so this system property should be available to all profiles associated with server1. My WebSphere Connector seems to be configured properly since the Start command will start WAS 6.1 and it is loading my applications associated with my MyEclipse profile. At first I thought this was an error with my WAS profiles, but when I run the startServer server1 command in <WAS_HOME>profiles\MyEclipse\bin from the command prompt…configFilePath is loaded up. In addition efforts to use the Optional program arguments to resolve this issue have proven unsuccessful. Any suggestions would be appreciated.

    Thanks,
    Eugene

    Install Details

    *** Date:
    Thursday, December 6, 2007 4:42:24 PM EST

    ** System properties:
    OS=Windows2000
    OS version=5.0
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.0.1 GA
    Build id: 6.0.1-GA-200710

    Eclipse Graphical Editing Framework

    Version: 3.3.1.v20070814
    Build id: 20070814-1555

    Eclipse Platform

    Version: 3.3.1.R33x_r20070911-_19UEkpF-B7Uh2hKy75y
    Build id: M20070921-1145

    Eclipse RCP

    Version: 3.3.1.R33x_r20070802-8y8eE8sEV3Fz0z0GlHJrXvTAUS
    Build id: M20070921-1145

    Eclipse Java Development Tools

    Version: 3.3.1.r331_v20070629-7o7jE72EDlXAbqAcnbmyg1rf8RIL
    Build id: M20070921-1145

    Eclipse Plug-in Development Environment

    Version: 3.3.1.R33x_r20070802-7N7M3D1VIA_52JsDFsEC
    Build id: M20070921-1145

    Eclipse Project SDK

    Version: 3.3.1.R33x_r20070802-7M7J78_mu1mnlRa7A4Ns52XeZ6D0
    Build id: M20070921-1145

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\Program Files\MyEclipse 6.0\eclipse\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\Program Files\MyEclipse 6.0\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.1.R33x_v20070828\eclipse_1020.dll
    -startup
    C:\Program Files\MyEclipse 6.0\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20070828.jar
    -exitdata
    5e8_80
    -vm
    C:\Program Files\MyEclipse 6.0\jre\bin\javaw.exe

    #279447

    Riyad Kalla
    Member

    Eugene,
    Actually you will want to go to the “JDK” sub-preference node under the WAS 6.1 connector, and set it under the Optional VM Arguments (your -D argument). The optional program arguments are passed to the launch class of your app server, but you need to pass -D to the VM, not the launch class of WebSphere.

    #279457

    elm3d
    Member

    Riyad,

    That did the trick, thank you for your quick response.

    Eugene

    #279458

    Riyad Kalla
    Member

    Glad it helped.

    #308618

    dkmankotia
    Member

    Hi Riyad,

    I am also facing the same problem while accessing systemproperties. I have set them in Admin console but while retrieving through System.getProperty it returns null. I am using websphere 7 however I don’t see jdk sub preference option.

    Can you please tell me how do I pass properties for Websphere 7

    thanks,
    Deepak

Viewing 5 posts - 1 through 5 (of 5 total)
Reply To: WebSphere 6.1 Generic JVM argument not loaded on startup

You must be logged in to post in the forum log in