For help with installation, bugs reports or feature requests, please head over to our new forums.
Genuitec Community on GitHub
- This topic has 7 replies, 3 voices, and was last updated 19 years, 9 months ago by
Scott Anderson.
-
AuthorPosts
-
gdeaconMemberHello,
I really want to migrate to MyEclipse but I cannot do so until I can get my Websphere installation to work within the IDE. I configured the connector and the app starts to start up however, it terminates Here’s the output from SystemO.log ….
[11/14/06 9:00:55:218 EST] 4fc21bc9 WsServer E WSVR0003E: Server server1 failed to start
com.ibm.ws.exception.RuntimeError
at com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:164)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:134)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:543)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:418)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:183)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
—- Begin backtrace for nested exception[11/14/06 9:00:55:233 EST] 4fc21bc9 WsServer E WSVR0009E: Error occurred during startup
Any help in this matter would be very much appreciated.
Thanx
Garrett DeaconNovember 14, 2006 at 9:40 am #261788
Riyad KallaMemberGarrett,
One of the most common problems is when users forgot to configure their app servers to run exactly with the JDK that they ship with. For example WebLogic and WebSphere both ship JDKs inside their install that they need to be run with. Try double checking your connector settings and make sure those are setup correctly.Also, make sure that your connector settings are correct to, here’s an example configuration for WebSphere 6:
http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-13944.htmlYou can use that as an indicator of the correct paths and dirs that need to be setup for each field (for example, it’s easy to get the node or server values wrong)
November 16, 2006 at 10:48 am #262036
gdeaconMemberHi Riyad,
I checked and double checked both the JDK being used and the Root Dir for the app server.
Here’s the setting for the JDK
C:\WebSphere5\AppServer\javaHeres my AppServer dir
C:\WebSphere5\AppServerI am useing Websphere5 so the app server dir is a bit different than the config you had as an example for yucks I changed it to reflect yours and the app would not start cuz it could not find the bin dir
I am at my witts end here. Any ideas from the stack trace I sent you?
Thanx
-GarrettNovember 16, 2006 at 11:20 am #262050
Riyad KallaMemberOk, another thing ot check, even though it might sound silly, is your server really named “server1” as in the default connector setting or did you name it something else? Also is this version 5.0 or 5.1? (e.g. do you have the checkbox checked in the connector settings?) And lastly, does the app server start up fine when launched externally? What does the startup log look like?
November 17, 2006 at 9:42 am #262134
gdeaconMemberHey Riyad,
Here’s the output of the SystemOut.log my default server is named server1. I do not have 5.1 checked since we are running 5.0.2.9.
Any other ideas am I SOL 🙁
Thanx
-Garrett************ Start Display Current Environment ************
WebSphere Platform 5.0 [BASE 5.0.2.9 cf90448.01] [JDK 1.3.1.7 jdk0429.03] running with process name gdeacon01-lt\gdeacon01-lt\server1 and process id 5892
Host Operating System is Windows XP, version 5.1
Java version = J2RE 1.3.1 IBM Windows 32 build cn131-20040517 (JIT enabled: jitc), Java Compiler = jitc, Java VM name = Classic VM
was.install.root = C:\WebSphere5\AppServer
user.install.root = C:\WebSphere5\AppServer
Java Home = C:\WebSphere5\AppServer\java\jre
ws.ext.dirs = C:\WebSphere5\AppServer\java/lib;C:\WebSphere5\AppServer/classes;C:\WebSphere5\AppServer/classes;C:\WebSphere5\AppServer/lib;C:\WebSphere5\AppServer/lib/ext;C:\WebSphere5\AppServer/web/help;C:\WebSphere5\AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = C:\WebSphere5\AppServer/properties;C:\WebSphere5\AppServer/properties;C:\WebSphere5\AppServer/lib/bootstrap.jar;C:\WebSphere5\AppServer/lib/j2ee.jar;C:\WebSphere5\AppServer/lib/lmproxy.jar;C:\WebSphere5\AppServer/lib/urlprotocols.jar
Java Library path = C:\WebSphere5\AppServer\java\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WebSphere5\AppServer\bin;C:\WebSphere5\AppServer\java\bin;C:\WebSphere5\AppServer\java\jre\bin;C:\Program Files\Common Files\Actuate\7.0\JDK141\jre\bin\client;C:\WebSphere5\MQ\Java\lib;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\PROGRA~1\CA\SHARED~1\SCANEN~1;C:\Program Files\CA\SharedComponents\ScanEngine;C:\Program Files\CA\SharedComponents\CAUpdate\;C:\Program Files\CA\SharedComponents\ThirdParty\;C:\Program Files\CA\SharedComponents\SubscriptionLicense\;C:\PROGRA~1\CA\ETRUST~1;C:\Program Files\Rational\ClearCase\bin;C:\Program Files\Rational\common;C:\PROGRA~1\IBM\SQLLIB\BIN;C:\PROGRA~1\IBM\SQLLIB\FUNCTION;C:\PROGRA~1\IBM\SQLLIB\SAMPLES\REPL;C:\WebSphere5\MQ\bin;C:\WebSphere5\MQ\WEMPS\bin;C:\Program Files\QuickTime\QTSystem;C:\WebSphere5\MQ\bin;C:\WebSphere5\MQ\bin;C:\WebSphere5\MQ\java\bin;C:/WebSphere5/MQ/WEMPS\bin
************* End Display Current Environment *************November 17, 2006 at 10:04 am #262145
Riyad KallaMemberHmm it looks like you set everything up correctly, I”m really not sure what is going on. Are you running service pack #9 I think for WAS? I just helped another user on WAS 5.0 that had to remove “the latest service pack” in order to get it to work… I wonder if this is the same problem.
Also, let’s assume the worse, you are still not SOL. You just launch WebSphere externally, and use our Remote Debugging guide to debug anything you need. So you still get al the functionality, it’s just 2 steps, instead of 1.
http://www.myeclipseide.com/images/tutorials/quickstarts/remotedebugging/November 20, 2006 at 2:03 pm #262294
gdeaconMemberHi Riyad,
I have to use this version of the App server becuase our app is deployed on the customr’s site with that version. I installed Fixpack 2 and patch #9 when I installed the app server. Not sure I can uninstall stuff for the reasons I mentioned.
Server info….
IBM WebSphere Application Server, 5.0.2.9
Build Number: cf90448.01
Build Date: 12/03/2004
—————————————Thanx for the link on external debugging I’ll take a look at that
-GarrettNovember 20, 2006 at 2:54 pm #262302
Scott AndersonParticipantGarrett,
Please also have a look at our WebSphere 5 tutorial here: http://www.myeclipseide.com/Articles/WebSphere5.1LogConfiguration/WAS5.1LogConfiguration.html
Does the server start correctly from the commandline, outside of MyEclipse? If not, getting that working first is critical.
It might help with the logging a bit better or allow you to figure out what’s up. As for the stack, what you sent looks like a security component
of some sort, but it’s impossible to see exactly.What you could do is create a launch configuration so you can see exactly what the server instance is being launched with. Details on
how to do that are in Section 9 of the Application Server Quickstart.You can then have websphere generate a startup script externally so you can see how the launch config differs from the
commandline script. You can create the script with:startServer.bat server1 -script startServer1.bat -
AuthorPosts
