[rajnag21]

Hi ,
I tried to start websphere from within myeclipse and i get this error.

The JVM option is invalid: -Xshareclasses:name=webspherev61,nonFatal
Could not create the Java virtual machine.

I went into debug launch profile to understand what options are being added and I found this

“-Xbootclasspath/p:C:/Program Files/IBM/WebSphere/AppServer1/java/jre/lib/ext/ibmorb.jar;C:/Program Files/IBM/WebSphere/AppServer1/java/jre/lib/ext/ibmext.jar” -Xquickstart -Declipse.security -Dosgi.install.area=”C:/Program Files/IBM/WebSphere/AppServer1″ -Dpython.cachedir=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/temp/cachedir” -Dosgi.configuration.area=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/configuration” -Dosgi.framework.extensions=com.ibm.cds

-Xshareclasses:name=webspherev61,nonFatal

-Dibm.websphere.internalClassAccessMode=allow -Djavax.management.builder.initial=com.ibm.ws.management.PlatformMBeanServerBuilder -Dserver.root=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01″ -Dderby.system.home=”C:/Program Files/IBM/WebSphere/AppServer1/derby” -Djava.util.logging.configureByServer=true -Djava.util.logging.manager=com.ibm.ws.bootstrap.WsLogManager -Duser.install.root=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01″ -Dcom.ibm.itp.location=”C:/Program Files/IBM/WebSphere/AppServer1/bin” -Dwas.install.root=”C:/Program Files/IBM/WebSphere/AppServer1″ -Djava.security.auth.login.config=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/properties/wsjaas.conf” -Djava.security.policy=”C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/properties/server.policy” -Dws.ext.dirs=”C:/Program Files/IBM/WebSphere/AppServer1/java/lib;C:/Program Files/IBM/WebSphere/AppServer1/profiles/AppSrv01/classes;C:/Program Files/IBM/WebSphere/AppServer1/classes;C:/Program Files/IBM/WebSphere/AppServer1/lib;C:/Program Files/IBM/WebSphere/AppServer1/installedChannels;C:/Program Files/IBM/WebSphere/AppServer1/lib/ext;C:/Program Files/IBM/WebSphere/AppServer1/web/help;C:/Program Files/IBM/WebSphere/AppServer1/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime” -Djava.library.path=”C:/Program Files/IBM/WebSphere/AppServer1/java/bin;C:/Program Files/IBM/WebSphere/AppServer1/bin” -Dwas.debug.mode=false -Xscmx50M -Xms50m -Xmx256M

Now How do I remove this option so this error doesnt happen or for that matter simply put how do i start websphere from within myeclipse ?

[Riyad Kalla]

You need to configure WebSphere to launch with the application server that ships with it, under the ‘java’ or directory under the install dir. Then the -Xshareclasses will be understood.

[rajnag21]

I dont understand what you are saying. I can start websphere standalone app server byitself. I am not able to do it from within myeclipse only.

[Riyad Kalla]

When you install WebSphere, in addition to the install directory containing the application server, it also contains a JDK. You must go to your connector settings under Window > Prefs > MyEclipse > App Servers > WebSphere 6.1 > JDK, and configure that specific JDK to launch WebSphere.

[rajnag21]

Hi,
I took care to make sure that websphere connector is configured to start with IBM JDK only since it is vastly different from sun’s own JDK. It’s stilll not working.

[Riyad Kalla]

rajnag21,
The -Xshareclasses argument is specific to Java 5 and later VMs and relates to the new class sharing feature that was introduced. The only way I see you getting “invalid argument” errors from it, is if you accidentally setup WebSphere to run with a 1.4 VM.

Are you sure you are using a clean WebSphere 6.1 install? I have one locally and it runs as expected, also the VM that ships with it is Java 5.

[rajnag21]

I am using 1.4 jdk to start up myeclipse and I have configured websphere connector to start websphere with its own connector. the specific version of JDK I am using to start myeclipse is j2sdk1.4.2_12.

[Riyad Kalla]

rajnag21,
The JDK that WebSphere 6.1 installs is 1.5. I just installed 6.1, downloaded from the IBM site and the Java version is:

C:\Java\Application Servers\websphere-6.1\java\bin>java -version
java version “1.5.0”
Java(TM) 2 Runtime Environment, Standard Edition (build pwi32devifx-20061107 (iF
ix 111765: SR3 + 111700))
IBM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-2006100
1 (JIT enabled)
J9VM – 20060915_08260_lHdSMR
JIT – 20060908_1811_r8
GC – 20060906_AA)
JCL – 20061107

C:\Java\Application Servers\websphere-6.1\java\bin>

I don’t know where the 1.4 setup is comming from that you are using, but double-check under your 6.1 install dir under ‘java’ that you are using that JDK.

[rajnag21]

Riyad,
There is a misunderstanding.
1)I have eclipse installed under c:.
2)I have myeclipse installed under c\program files\…
3)I have websphere installed under c:\ibm\websphere\.
4)I also have a sun jdk installed under c:\jdk. The system or computer path and classpath point to the sun’s jdk.
5)By this time i also have configured a profile for my websphere 6.1 app server ND and I am able to start and stop the server through its own start and stop scripts.
6)I start myeclipse. The myeclipse/eclipse platform uses sun jdk to start up since sun jdk and associated libraries are picked up from path and classpath.
7)I configure websphere java/jre VM to be used for my project. the default before this was the sun jdk. I go to websphere connectors and put in the appropriate path to websphere app server and the node and cell info is picked up and displayed . I go to jvm settings and make sure that websphere jdk is the one that is being used. I click on start at this point(just like you documentation says)
I get the error that i described in my first post. If you give me your email address I will gladly send you all the screen shots.

-Raj

[Riyad Kalla]

Raj,
There is no misunderstanding.

1) The connector launches WebSphere 6.1 correctly
2) You cannot get it to launch because you have configured WebSphere 6.1 to launch with a 1.4 JDK
3) WebSphere 6.1 installs JDK 5.0 under it’s install dir in a directory called “java”, and this is the JDK you need to setup WebSphere to launch with.

I’m not sure if you are misunderstanding my instructions or if something is different about your setup. Can you PM me a screenshot of your WebSphere 6.1 > JDK configuration screen AND a screenshot of the details of that JDK configuration you are using?

[rajnag21]

Riyad,
Thanks for that help. Someone gave me a copy of websphere 6.1 with 1.4 version of ibm jdk. I now have a copy of it with the IBM 1.5 jdk and it works ok.

I still have a problem, though. When i try to stop it I get the following error.

DMU0116I: Tool information is being logged in file
C:\IBM\WebSphere\AppServer\profiles\AppSrv02\logs\server1\stopServer.log
ADMU0128I: Starting tool with the AppSrv02 profile
ADMU3100I: Reading configuration for server: server1
ADMU0509I: The server “server1” cannot be reached. It appears to be stopped.
ADMU0211I: Error details may be seen in the file:
C:\IBM\WebSphere\AppServer\profiles\AppSrv02\logs\server1\stopServer.log
I will PM you contents of the log file.

Install history:

I installed the app server and it did the default profile creation. I added another profile with the advanced options method. I did not want to start this new profile server as a windows service. I installed all sample apps on it.

[Riyad Kalla]

Hmm… is this the default profile you are trying to start or the custom one? When you switch to the debug perpective do you still see the process running, or is it actually shutting down correctly?

[rajnag21]

It looks like it is stoppped. But I would prefer a graceful stop. can you look at the information and tell me how I could do that.
When I do the start and stop from outside myeclipse, from the websphere scripts themselves, It pops up a window asking me to login to the target server with the user identity and user password.
I will PM you the screenshots.

[Riyad Kalla]

rajnag21,
I have filed a note for a developer to look into this issue internally… the problem is that with a default WebSphere setup I cannot reproduce the dirty-shutdown issue at the moment… I will keep playing with it and see what we find.

Sorry for the trouble.

[rajnag21]

Riyad,
I am sorry I did not tell you . I did not do default profile. I added another profile. I am sending you the screenshots of all the steps I took so you can duplicate the issue.

[Author]

Posts