Nope, sorry, can't help specifically. I just ran across that article and
figured I'd post it in case it was useful to you. Have you tried a
WebSphere newsgroup? Maybe
ibm.software.websphere.studio.application-site-developer. Seems like
someone there should be able to help you.

Susan

On 12/16/2003 01:13:02 AM "Martin Gainty" wrote:

> Susan
> This is the specific error
>
> LaunchPad.bat contents
> REM pushd %1
> REM D:\IBM\wsdk_v51\appserver\java\jre\bin\javaw -is:javahome
> D:\IBM\wsdk_v51\appserver\java\jre -jar launchpad.jar
> SET
>
FILLER="12345678901234567890123456789012345678901234567890123456789012345678

> 901234567890"
> SET JAVA_OLD_HOME = %JAVA_HOME%
> SET JAVA_HOME=D:\IBM\wsdk_v51\appserver\java\jre
> SET CLASSPATH=> D:\IBM\wsdk_v51\appserver\java\jre\bin\javaw -mx32m -jar
> launchpad.jar -is:javahome D:\IBM\wsdk_v51\appserver\java\jre
> SET FILLER=> SET JAVA_HOME = %JAVA_OLD_HOME%
> REM popd
>
> when javaw.exe executes I get version mismatch
> I have none of the ini files you mentioned on my system
>
> Suggestions?
> Martin
> ----- Original Message -----
> From: "Susan Bradeen" <[EMAIL PROTECTED]>
> To: "Struts Users Mailing List" <[EMAIL PROTECTED]>
> Sent: Monday, December 15, 2003 3:53 PM
> Subject: Re: Off Topic: A suitable JVM could not be found
>
>
> >
> > Martin,
> >
> > Just in case this might be useful, the following is from a WebSpherePro
> > Developer's Tips email newsletter (11/20/2003).
> >
> > Hope it helps,
> > Susan Bradeen
> >
> > RUNNING WSAD WITH JVM 1.4
> > I've been happy running WebSphere Studio Application Developer
> > (WSAD) using IBM's JDK 1.3.1, but I recently worked on a Web
> > application that was to run with JDK 1.4. You can change the WSAD
> > compiler to use a different JDK, but I decided to go ahead and also
> > run WSAD with JDK 1.4.
> >
> > Here's how I accomplished the JDK 1.3 to 1.4 modification:
> >
> > First, download JDK 1.4.1. Note that I could not get WSAD to work
> > with JDK 1.4.2, although it works fine with 1.4.1. (I used 1.4.1_06
> > and _05.)
> >
> > Next, copy wsappdev.ini (or wssitedev.ini, if you are using WDSc or
> > WSSD) to a backup file. That INI file should exist in the
> > installation directory. On my Windows machine, it was located at
> > C:\Program Files\IBM\Websphere Studio.
> >
> > Then edit the wsappdev.ini (or wssitedev.ini) file so there is one
> > VMArgs setting:
> >
> > VMArgs=-Xverify:none -Xoptimize -Xms128m -Xmx384m
> >
> > You can twiddle around with JDK 1.4.1's options, but I've found
> > these settings to work well for me.
> >
> > Then you need to change the start-up command in WSAD's start menu
> > option. To do this, select the icon from your desktop, click the
> > right mouse button, and select Properties. Then add the javaw.exe
> > virtual machine qualifier after the quoted wsappdev50.exe command:
> >
> > "C:\Program Files\IBM\WebSphere Studio\wsappdev50.exe" -vm
> > C:\opt\java\jdk141\bin\javaw.exe
> >
> > On 12/15/2003 03:35:36 PM "Martin Gainty" wrote:
> >
> > > Kirk et al
> > > Back on this thread with no resolution
> > > I dont want to uninstall the existing JRE 1.41_02 as other
environments
> > are
> > > using the latest version
> > > I would like to run Websphere in "isolated space" but keep knocking
into
> > the
> > > "a suitable JVM could not be found"
> > > Anyone have a solution?
> > > Thanks,
> > > -Martin
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to