For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 8 replies, 2 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
I’ve just finished updating to the M3 release in order to utilize the WebSphere v6 Application Server integration. My problem is that I cannot launch WS from MyEclipse. I get a Microsoft Visual C++ Runtime Library Error. It states Runtime Error! Program: C:\Program Files\IBM\WebSphere\AppServer\java\bin\javaw.exe
The application has requested the Runtime to terminate it in an unusual way. Please contact the application’s support team for more information.
I have gone through the First Steps and started the application server and was able to successfully stop the server but cannot start from MyEclipse. I also went through and changed the path to not include spaces and it still got the same error.
Please help.
Chris
Chris,
That one is really an odd one as it’s saying that something is crashing the JVM, but I don’t know what that has to do with Visual C++. Perhaps the IBM JVM has some native performance optimizations or something. We’ve honestly never seen this one before. Does it start OK from the command line? All MyEclipse does is launch with the same parameters so it’s odd that it would work outside the environment but not within it, which is why I’m asking.
Scott,
I can launch WebSphere from the command line when I go to the profile called MyEclipse. It works fine.
C:\Program Files\IBM\WebSphere\AppServer\profiles\MyEclipse\bin>startServer serv
er1
ADMU0116I: Tool information is being logged in file C:\Program
Files\IBM\WebSphere\AppServer\profiles\MyEclipse\logs\server1\startSe
rver.log
ADMU0128I: Starting tool with the MyEclipse profile
ADMU3100I: Reading configuration for server: server1
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3000I: Server server1 open for e-business; process id is 3976C:\Program Files\IBM\WebSphere\AppServer\profiles\MyEclipse\bin>
Under your WebSphere 6 > JDK preferences, is the “JRE” you have set pointing to:
C:\Program Files\IBM\WebSphere\AppServer\java
as the root directory? It should be *precisely* that directory, not the jre directory below it.Yes, everything under the JDK is set to the java directory and not the jre. I’ve moved it from having spaces and it still gave me the same error. Maybe this install is not working correctly, is there a chance of another build that I could get? As I stated before, I can stop the server with no problem from MyEclipse, however, I haven’t been able to start from it. It appears something is wrong with the launching because I tried using a JBoss server that I have used in the previous version of MyEclipse and I am getting an error as well. It states that the Transport dt_socket failed to initialize, rc=509.
This worked previously in M2.
I am going to try to completely uninstall the previous version and start from a clean install of eclipse and MyEclipse. I’ll tell you the results when I get them.
Scott,
I completely uninstalled MyEclipse and Eclipse and still have the errors as stated above. I even tried to create the JBoss server using a JDK 1.4.2 from Sun and I still get the error. I believe it’s something with the install M3.
Please advise.
I even tried to create the JBoss server using a JDK 1.4.2 from Sun and I still get the error.
There seems to be something local to your machine that is keeping pretty much everything from working. In all honesty, the errors you’ve reported are the first times we’ve seen any of them, on any platform. I don’t suppose there’s another machine you could try it out on, could you? How about a different workspace at least?
Scott,
I took your advice and uninstalled both Eclipse and MyEclipse AND removed RAD v6 and other tools associated with RAD v6. It appears that something in RAD v6 was conflicting with MyEclipse. I’m not sure but once I uninstalled RAD v6 and its associated tools, it works.
Well, that’s good news that we figured out what the issue was, and I’m glad to hear you were willing to uninstall a $3000 tool to get our fine $30 tool working. 🙂 But I feel a little guilty for that and I hope you don’t end up missing it too much. If you do, changing the install order might fix the issue. For example, I assume you had RAD v6 installed before Eclipse / MyEclipse. Maybe installing it *after* won’t cause the problem it had in the preexisting config. I’ve seen that with software before, but given the time it would take to test that theory I certainly understand only doing it if you decide you’ve got to get RAD v6 back.
