[Joe]

I searched but did not find any post about this issue. Hope someone could give me a light. Thanks in advance.

In 32-bit WinXP, myeclipse with WAS 7 is working without any problem. I can start WAS server simply click the green start button inside eclipse IDE.

But in 64-bit Win 7, I tried install myeclipse with both 32-bit and 64-bit, have the same problem, that is, inside eclipse IDE, if I configure the WAS 7 as Run Mode, I can start the server with the green start button. But can’t if configure as Debug mode.

There is no problem to directly use IBM short cut to start WAS both debug mode or run mode. And if I start WAS with the start menu, I am able to attach to the debugging port and debug in myeclipse.

Here is the error message in WAS server log:
JVMJ9TI001E Agent library jdwp could not be opened (The specified module could not be found. )
JVMJ9VM015W Initialization error for library j9jvmti24(-3): JVMJ9VM009E J9VMDllMain failed
Could not create the Java virtual machine.

[support-swapna]

joe2000,

I could not replicate the issue at my end.

Can you answer some more questions for me to understand the issue better ?

1) Can you share your installation details from MyEclipse > Installation Summary > Installation Details ? Please paste them here for me.

2) Clear the contents of the .log file which is located at <workspace dir>/.metadata/.log . Now try starting the WAS 7 in debug mode. Paste the entire contents of the .log file here for me.

3) Also have a look at this thread. Check if the setting up environment variables thread is of any help to you :
https://www-304.ibm.com/support/docview.wss?uid=swg21319688

[Brian Fernandes]

Joe,

1) Could you try running MyEclipse Blue as administrator and see if that helps?
2) Is this a 64bit install of WebSphere (I do not recall ATM if WebSphere offers both a 32 and 64bit option on Windows 64-bit)

[Joe]

1. This is the “Installation Details”

*** Date:
Friday, April 29, 2011 11:32:12 AM EDT

** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13

*** MyEclipse details:
MyEclipse Blue Edition
Version: 9.0 Blue
Build id: 9.0-Blue-20110318

*** Eclipse details:
MyEclipse Blue Edition

Version: 9.0 Blue
Build id: 9.0-Blue-20110318

Eclipse Platform

Version: 3.6.1.r361_v20100909-9gF78GrkFqw7GrsZnvz0JWNTeb6fue6896L
Build id: M20100909-0800

Eclipse Java Development Tools

Version: 3.6.1.r361_v20100714-0800-7z8XFUSFLFlmgLc5z-Bvrt8-HVkH
Build id: M20100909-0800

Eclipse Plug-in Development Environment

Version: 3.6.1.r361_v20100727-7b7mFL-FET3dhESDgE5_bkJ
Build id: M20100909-0800

Eclipse Graphical Editing Framework GEF

Version: 3.6.1.v20100908-1100-777B181A3Bz-6B663E7974242
Build id: 201009132020

Eclipse RCP

Version: 3.6.1.r361_v20100827-9OArFLdFjY-ThSQXmKvKz0_T
Build id: M20100909-0800

Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\MyEclipse Blue Edition 9\myeclipse-blue.exe
-name
Myeclipse-blue
–launcher.library
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\MyEclipse Blue Edition 9\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\MyEclipse Blue Edition 9\../Common/plugins/org.eclipse.equinox.launcher_1.1.0.v20100507.jar
-install
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\MyEclipse Blue Edition 9
-configuration
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\MyEclipse Blue Edition 9\configuration
-vm
C:\Users\jliu\AppData\Local\MyEclipse Blue Edition\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dll

[Joe]

2. Clear the .log file, and start WAS server in debug. There is no log info in the .log file, this is, the .log file is still empty.
Here is info on the console screen.

ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer-7.0\profiles\AppSrv01\logs\server1\startServer.log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. startServer.log,
SystemOut.log(or job log in zOS) and other log files under
C:\Program
Files\IBM\WebSphere\AppServer-7.0\profiles\AppSrv01\logs\server1
should contain failure information.

The previous erro info is in the IBM WAS native_stderr.log file.

3. I searched and found that thread before about the environment variable setting. I have a question about how myeclipse starts WAS server?
Outside of myeclipse IDE, WAS provides a bat file in the bin folder of server profile, e.g. “C:\Program Files\IBM\WebSphere\AppServer-7.0\profiles\AppSrv01\bin\startServer.bat” server1
I don’t have problem to start server with the bat file.
Just wondering if myeclipse is calling the same bat file to start server? I modifies bat files but it does not affect myeclipse.
So I don’t know how I can add environment setting for myeclipse server startup.

4.It is a 64bit WAS on 64bit Win7. I tried myeclipse both 32 and 64. But I did not try to install 32 bit WAS.

Thanks in advance!

Joe

[Brian Fernandes]

Joe,

It was not clear from your response if you tried starting MyEclipse Blue as administrator – could you please try this?

MyEclipse does not use this batch file – but does do something similar, it will call the WebSphere launching process, which in turn will launch WebSphere – so changes in the batch file will not affect the server start.

Could you point me to the thread with the environment variables that you are referring to?

[pbonney]

I’m encountering this same issue; has anyone found a tidy resolution?

I’m running on 64-bit Windows 7. I’ve updated to MyEclipse Blue 9.1 (Build id: 9.1-Blue-20110701), with WebSphere for Developers 7.0. I am running MyEclipse Blue as Administrator.

When I try to start WAS in debug mode, I get the following error in <was-dir>\profiles\AppSrv01\logs\server1\native_stderr.log:

JVMJ9TI001E Agent library jdwp could not be opened (The specified module could not be found. )
JVMJ9VM015W Initialization error for library j9jvmti24(-3): JVMJ9VM009E J9VMDllMain failed
Could not create the Java virtual machine.

I note that the jdwp library mentioned in the error is in <was-dir>\java\jre\bin\jdwp.dll. However, MyEclipse’s Server Connector configuration insists on having a reference to the JDK in the parent directory (not the JRE containing the dll).

I tried copying everything extra from the WAS JRE sub-directory to the corresponding WAS JDK directories (e.g., contents of java\jre\bin to java\bin, java\jre\lib to java\lib, etc), and this seemed to get me past the error. But I now get other application errors, and I worry that I’ve corrupted or confused the normal WAS execution environment. At best, it feels like a messy hack.

Thanks for any insights.
Peter

[pbonney]

One additional point on my earlier post: I should clarify that I installed 64-bit WebSphere 7 (was.7000.wasdev.nocharge.windows.amd64), and updated it to fix-pack 19 (7.0.0-WS-WAS-WinX64-FP0000019.pak).

Cheers,
Peter

[Brian Fernandes]

Peter,

Some sanity checking:

1) Are you running a 64-bit version of MyEclipse? You can check this from MyEclipse > Installation Summary > Installation Details. Look for the “-arch” switch towards the end of the presented text. Does it say x86 or x86_64?

2) The problem in your case does not appear to be permission related. Can you start WAS externally? Is WAS installed as a service in windows?

[pbonney]

Hi Brian, thank you very much for the response.

1) Are you running a 64-bit version of MyEclipse?

-arch
x86_64

2) The problem in your case does not appear to be permission related. Can you start WAS externally?

I haven’t tried starting WAS externally. Since my issue is with debug mode, are you suggesting I start WAS from the command line and then try to connect to it as a remote server? (Note that I am able to run WAS from within MyEclipse in normal mode; it’s only debug mode that fails.)

Is WAS installed as a service in windows?

I uninstalled the windows service after installing the application (“WASService.exe -remove <MyHost>Node01″ in the WAS install’s bin directory).

Thanks again,
Peter

[Brian Fernandes]

Peter,

Sorry, I missed the fact that only debug mode is failing.

1) How are you starting it in debug mode, just right clicking on WAS in the server view and choosing “Debug server” instead of “Run Server”? Are there no problems reported in the run mode at all?

2) Did you attempt to start WAS in debug mode before installing the fix pack? In other words, do you know if this problem started only after installing the fix pack?

3) Go to the 3rd page of the profile configuration wizard where you configure your WAS profile and check the JDK name being referenced. Is this “WebSphere 7 JDK”? If you now go to Window > Preferences > Java > Installed JREs and select this JRE – does the path look fine? Can you paste that here?

4) In case there is something awry with your profile, as a test, could you try creating a new profile and attempt to use that?

[pbonney]

Hi Brian,

1) How are you starting it in debug mode, just right clicking on WAS in the server view and choosing “Debug server” instead of “Run Server”? Are there no problems reported in the run mode at all?

Correct. The server goes into “Starting…” status, but nothing appears in the Console and the server doesn’t start. It’s only when I go to the logs/server1 directory and look at native_stderr.log that I see the “JVMJ9TI001E Agent library jdwp could not be opened …” problem.

2) Did you attempt to start WAS in debug mode before installing the fix pack? In other words, do you know if this problem started only after installing the fix pack?

Good question. It occurred both before and after applying the fix pack. (I tested for a while without the fix pack until I realized there was an essential fix [unrelated to this problem] that I needed.)

3) Go to the 3rd page of the profile configuration wizard where you configure your WAS profile and check the JDK name being referenced. Is this “WebSphere 7 JDK”? If you now go to Window > Preferences > Java > Installed JREs and select this JRE – does the path look fine? Can you paste that here?

JRE home: C:\Program Files\IBM\WebSphere\AppServer.0\java
JRE name: WebSphere 7 JDK
I’ve confirmed that this is the JDK referenced on the third page of the profile configuration wizard. (The profile itself is at C:\Program Files\IBM\WebSphere\AppServer.0\profiles\AppSrv01.)

4) In case there is something awry with your profile, as a test, could you try creating a new profile and attempt to use that?

I’m afraid I’ve done this already, without any luck. (Indeed, I completely uninstalled and re-installed WAS 7.) I’ve tried recreating the profile using both the “Add” button and the “Load Profiles” button.

Thanks again for your help.
Peter

[Gianluca84]

Hi pbonney,

) In case there is something awry with your profile, as a test, could you try creating a new profile and attempt to use that?

I think Brian meant to actually create a new websphere profile (not as a service for example).

Unfortunately with was7 64 bit there is no grafical utility to do that you have to execute something like:

"c:\Program Files\IBM\WebSphere\AppServer\bin\manageprofiles.bat" -create 
-profileName AppSrv02 
-templatePath "c:\Program Files\IBM\WebSphere\AppServer\profileTemplates\default" 
-isDefault -winserviceCheck false -enableAdminSecurity false 
-personalCertDN "cn=testa, ou=Rochester, o=IBM, c=US"
 -signingCertDN "cn=testc, ou=Rochester, o=IBM, c=US"
 -keyStorePassword ap3n9krw -validatePorts

On your command prompt with administrator privileges.

You can check all the command option here http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/rxml_manageprofiles.html

For the record I’ve tryed WAS7 64 bit with myeclipse and is working fine both in normal mode and in debug mode. I too have disable the windows service like you did and created a new profile with no service. Then I loaded that profile into myeclipse and remove the other from there too.

Good luck!

[pbonney]

Thanks for the clarification and the clear directions, Gianluca.

I created a second profile using the command you provided:

AboutThisProfile.txt

Application server environment to create: Application server
Location: c:\Program Files\IBM\WebSphere\AppServer\\7.0\profiles\AppSrv02
Disk space required: 200 MB
Profile name: AppSrv02
Make this profile the default: True
Node name: E6520-pbNode02
Host name: E6520-pb.lan
Enable administrative security (recommended): False
Administrative console port: 9061
Administrative console secure port: 9044
HTTP transport port: 9081
HTTPS transport port: 9444
Bootstrap port: 2810
SOAP connector port: 8881
Run application server as a service: False
Create a Web server definition: False
Performance tuning setting: Standard

I then removed the AppSrv01 Server Connector from MyEclipse and created a new connector to the new profile. Unfortunately, I see the same behavior with the new profile: I can start it fine in run mode, but in debug mode I get the “JVMJ9TI001E Agent library jdwp …” error in …\AppSrv02\logs\server1\native_stderr.log.

Thanks again for the help, though!

Peter

[Gianluca84]

I did a little googleing and I came up with this:
https://www-304.ibm.com/support/docview.wss?uid=nas11a35b31a9e22b1e086257648007425e9

https://www-304.ibm.com/support/docview.wss?uid=swg21319688

The problems seems connected to the Profile service option on the server (I didn’t read fully both articles so maybe you should) and the classpath variables needed by this service to start correctly.

Are you running the WAS server with its specific JVM right? Websphere 7 jdk in your case, you have defined it during the connector configuration.

If you look at the services windows of windows 7 is there sitll some service starting with IBM*? If so check if it’s the WAS server of your second installation and and in that case remove it.

Next thing I would try:
Start the server in normal mode enter in the admin console and disable profiling. Server->Webspere Application server->yourserver->PMI -> None
or something like that.
Save and restart server in debug mode.

[Author]

Posts