- This topic has 39 replies, 6 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
Well, now it looks like we have two identical configurations behaving differently, which continues to lack a sensical explaination.
The only thing that remains is either enabling JIT for the launch the MyEclipse connector is performing or disabling it for the
script launch. Can you can check that out and report back? In the meantime, I’ve asked someone else to do a fresh download,
configuration, and install to see if the result replicate your experiences, mine, or something else entirely.OK. Then it’s off to try parallel installs on other machines. Thanks for checking on the JIT flag and helping us figure out what’s up here. This is truly a unique problem report.
Hey guys,
I just download WS5.1 and installed on my machine. I installed a freshcopy of eclipse-3.0RC1 + MyEclipse 3.8beta1. I went under the Websphere 5.1 preference page and pointed it out to the WS install. I left the defaults for the rest of the fields, my hostname for the hostname and server1 for the servername. I then checked the option “Is Websphere version 5.1?”. Then under JDK I pointed a new jdk setup out to the java directory under the WS install. Then I created a simple webapp, deployed it to websphere and then I started up the appserver using MyEclipse. It spun up just fine. Both the console output and the server1/SystemOut.log were exception free.
We went through nearly the same steps here and still got the same
errors. Here are our exact steps:1. unzipped a fresh copy of eclipse 3.0 RC1 into the c:\tools directory.
2. installed MyEclipse 3.8 beta 1 into c:\tools\myeclipse directory.
3. insatlled WebSphere Application Server 5.1 into c:\tools accepting all
default settings. The install media was the WAS CD.
4. created a directory c:\tools\WebSphere\update and extracted the
contents of the fixpack 4 zip file.
5. opened a command prompt and changed to the
c:\tools\WebSphere\update directory. There I executed:set JAVA_HOME=c:\tools\WebSphere\AppServer\java
and then ran updateWizard.bat to apply the patch.
6. started WebSphere from the command line. I viewed the logs and
verified that everything worked file.
7. I opened the Administrative Console and verified that my application
server server1 was created and it was running properly.
8. I opened up a second browser and tested several of the example apps
that are distributed with WebSphere.
9. After I was confident that the installation was working properly I
stopped WebSphere.
10. next I started eclipse.
11. I setup the IBM JDK by going to window->preferences->java->
installed JREs and selected the add button. I selected the browser button
next to the JRE home directory entry field and selected the
c:\tools\WebSphere\AppServer\java directory. I entered a JRE name and
did not change any other setting on this dialog.
12. I changed to the MyEclipse->Application Servers->WebSphere 5
configuration window. There I selected the Enable radio button, entered
c:\tools\WebSphere\AppServer in the WebSphere Home Directory entry,
entered bw007007 (my hostname) in the Host Name entry, entered
server1 in the Server Name entry and checked the WebSphere 5.1 check
box. Under the WebSphere 5->JDK window I selected the IBM JDK that
I added in step 11. Everything else is using the default values.
13. I attempted to start WebSphere from within eclipse and got the
same error as before.We hope to try to repeat this process on another system today.
We hope to try to repeat this process on another system today.
That sounds like a good test. When you do this, could you try downloading WAS 5.1 from the IBM website instead of using the installation CD? The reason I ask is I want to see if there might be some subtle difference between the version on the website and the one on the CD. It may seem silly, but I’ve seen IBM do that kind of stuff before. Here’s the website link to make things easy:
http://www-106.ibm.com/developerworks/websphere/downloads/I am having the identical problem .. its not the app install .. its something to do with the easie plugin for was5. is someone from myeclipse looking into this? please post this on the thread if the solution is found .. thanks
We looked into it, but as you can see from the thread, were unable to replicate the problem internally. It appears we were running identical configurations and getting differing results. We tested on two independent systems internally and everything worked as expected.
In your Websphere connector settings, make sure you specify your hostname as BW007007, not bw007007. Apparently, the Launcher is case-sensitive. I had the same problem as you, and after I changed the case, I was able to start WAS5.
Good luck.
