[lupusire]

when i start the server i get this error (same by all applications)

************ Start Display Current Environment ************
WebSphere Platform 5.1 [BASE 5.1.1.3 cf30503.01] [JDK 1.4.2 cn1420-20040626] running with process name msgp382p\msgp382p\server1 and process id 1988
Host Operating System is Windows 2000, version 5.0
Java version = J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT disabled), Java Compiler = , Java VM name = Classic VM
was.install.root = D:\Programme\WebSphere\AppServer
user.install.root = D:\Programme\WebSphere\AppServer
Java Home = D:\Programme\WebSphere\AppServer\java\jre
ws.ext.dirs = D:\Programme\WebSphere\AppServer\java/lib;D:\Programme\WebSphere\AppServer/classes;D:\Programme\WebSphere\AppServer/lib;D:\Programme\WebSphere\AppServer/lib/ext;D:\Programme\WebSphere\AppServer/web/help;D:\Programme\WebSphere\AppServer/deploytool/itp/plugins/com.ibm.etools.ejbdeploy/runtime
Classpath = D:\Programme\WebSphere\AppServer/properties;D:\Programme\WebSphere\AppServer/lib/bootstrap.jar;D:\Programme\WebSphere\AppServer/lib/j2ee.jar;D:\Programme\WebSphere\AppServer/lib/lmproxy.jar;D:\Programme\WebSphere\AppServer/lib/urlprotocols.jar
Java Library path = D:\Programme\WebSphere\AppServer\java\bin;D:\Programme\WebSphere\AppServer\bin;D:/Programme/IBM/WebSphere MQ/WEMPS/bin
************* End Display Current Environment *************
[17.06.05 15:54:48:500 CEST] 30416d7d ManagerAdmin I TRAS0017I: Der Status des Start-Trace ist *=all=disabled.
[17.06.05 15:54:50:672 CEST] 30416d7d AdminInitiali A ADMN0015I: AdminService wurde initialisiert.
[17.06.05 15:54:52:797 CEST] 30416d7d Configuration A SECJ0215I: Die Konfigurationsklasse des JAAS-Anmeldungsprovider wurde auf com.ibm.ws.security.auth.login.Configuration gesetzt.
[17.06.05 15:54:52:953 CEST] 30416d7d SecurityDM I SECJ0231I: Das FFDC-Diagnosemodul com.ibm.ws.security.core.SecurityDM der Sicherheitskomponente wurde registriert: true.
[17.06.05 15:54:53:328 CEST] 30416d7d SecurityCompo I SECJ0309I: Die Java-2-Sicherheit ist inaktiviert.
[17.06.05 15:54:53:344 CEST] 30416d7d SecurityCompo I SECJ0212I: Die WCCM-JAAS-Konfigurationsdaten wurden in die Klasse des Anmeldungsprovider �bernommen.
[17.06.05 15:54:53:375 CEST] 30416d7d SecurityCompo I SECJ0240I: Die Initialisierung des Security Service ist abgeschlossen.
[17.06.05 15:54:58:234 CEST] 30416d7d JMSEmbeddedPr A MSGS0050I: Der Queue Manager wird gestartet.
[17.06.05 15:54:58:516 CEST] 30416d7d QueueManagerM E MSGS0101E: Der Befehl zum Starten des Queue Manager ist mit Exit-Code 16 fehlgeschlagen.
[17.06.05 15:54:58:531 CEST] 30416d7d JMSService E MSGS0001E: Beim Starten des JMS-Servers ist die Ausnahme java.lang.Exception: MSGS0101E: Der Befehl zum Starten des Queue Manager ist mit Exit-Code 16 fehlgeschlagen.
at com.ibm.ws.messaging.QueueManagerManager.startQueueManager(QueueManagerManager.java:394)
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:182)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:288)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
eingetreten.
[17.06.05 15:54:58:594 CEST] 30416d7d ContainerImpl E WSVR0501E: Beim Erstellen der Komponente null [class com.ibm.ws.messaging.JMSService] ist ein Fehler aufgetreten.
com.ibm.ws.exception.RuntimeWarning: MSGS0001E: Beim Starten des JMS-Servers ist die Ausnahme java.lang.Exception: MSGS0101E: Der Befehl zum Starten des Queue Manager ist mit Exit-Code 16 fehlgeschlagen. eingetreten.
at com.ibm.ws.messaging.JMSService.start(JMSService.java:295)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)

[17.06.05 15:55:00:766 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PlantsByWebSphereConnectionFactory wird als plantsby/InvQCF gebunden.
[17.06.05 15:55:00:875 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PlantsByWebSphereQ wird als plantsby/InvQ gebunden.
[17.06.05 15:55:01:203 CEST] 30416d7d ResourceMgrIm I WSVR0049I: ProdaDataSource_CF wird als eis/jdbc/Proda DataSource_CMP gebunden.
[17.06.05 15:55:01:250 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PlantsByWebSphere Mail Session wird als mail/PlantsByWebSphere gebunden.
[17.06.05 15:55:01:297 CEST] 30416d7d ResourceMgrIm I WSVR0049I: ProdaDataSource wird als jdbc/Proda DataSource gebunden.
[17.06.05 15:55:01:375 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Default Datasource wird als DefaultDatasource gebunden.
[17.06.05 15:55:01:391 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Pet Store JMS Queue Connection Factory wird als jms/queue/QueueConnectionFactory gebunden.
[17.06.05 15:55:01:406 CEST] 30416d7d ResourceMgrIm I WSVR0049I: SampleJMSQueueConnectionFactory wird als Sample/JMS/QCF gebunden.
[17.06.05 15:55:01:422 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.Q1 wird als Sample/JMS/Q1 gebunden.
[17.06.05 15:55:01:438 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.Q2 wird als Sample/JMS/Q2 gebunden.
[17.06.05 15:55:01:500 CEST] 30416d7d ResourceMgrIm I WSVR0049I: SampleJMSTopicConnectionFactory wird als Sample/JMS/TCF gebunden.
[17.06.05 15:55:01:531 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.listen wird als Sample/JMS/listen gebunden.
[17.06.05 15:55:01:547 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.news wird als Sample/JMS/news gebunden.
[17.06.05 15:55:01:562 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.sport wird als Sample/JMS/sport gebunden.
[17.06.05 15:55:01:562 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Sample.JMS.weather wird als Sample/JMS/weather gebunden.
[17.06.05 15:55:01:594 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Default_CF wird als eis/DefaultDatasource_CMP gebunden.
[17.06.05 15:55:01:609 CEST] 30416d7d ResourceMgrIm I WSVR0049I: TechSamp_CF wird als eis/WSsamples/TechSampDatasource_CMP gebunden.
[17.06.05 15:55:01:625 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PLANTSDB_CF wird als eis/jdbc/PlantsByWebSphereDataSource_CMP gebunden.
[17.06.05 15:55:01:656 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PetStore_CF wird als eis/jdbc/petstore/PetStoreDB_CMP gebunden.
[17.06.05 15:55:01:672 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Catalog_CF wird als eis/jdbc/CatalogDB_CMP gebunden.
[17.06.05 15:55:01:688 CEST] 30416d7d ResourceMgrIm I WSVR0049I: TechSamp wird als WSsamples/TechSampDatasource gebunden.
[17.06.05 15:55:01:703 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PLANTSDB wird als jdbc/PlantsByWebSphereDataSource gebunden.
[17.06.05 15:55:01:734 CEST] 30416d7d ResourceMgrIm I WSVR0049I: PetStoreDB wird als jdbc/petstore/PetStoreDB gebunden.
[17.06.05 15:55:01:750 CEST] 30416d7d ResourceMgrIm I WSVR0049I: CatalogDB wird als jdbc/CatalogDB gebunden.
[17.06.05 15:55:01:766 CEST] 30416d7d ResourceMgrIm I WSVR0049I: Pet Store Catalog DAO SQL URL wird als url/CatalogDAOSQLURL gebunden.
[17.06.05 15:55:02:938 CEST] 30416d7d CacheServiceI I DYNA0048I: WebSphere Dynamic Cache wurde initialisiert.
[17.06.05 15:55:09:438 CEST] 30416d7d JMXSoapAdapte A ADMC0013I: Der SOAP-Connector ist an Port 8880 verf�gbar.
[17.06.05 15:55:09:469 CEST] 30416d7d SecurityCompo I SECJ0243I: Der Security Service wurde gestartet.
[17.06.05 15:55:09:484 CEST] 30416d7d SecurityCompo I SECJ0210I: Die Sicherheit wurde aktiviert: false
[17.06.05 15:55:10:359 CEST] 30416d7d DeployedAppli W WSVR0215W: Das Starten der Anwendung DefaultApplication ist fehlgeschlagen. Die Anwendung wird nicht installiert.
[17.06.05 15:55:10:375 CEST] 30416d7d ApplicationMg W WSVR0100W: Beim Initialisieren von DefaultApplication ist ein Fehler aufgetreten.

[17.06.05 15:55:10:375 CEST] 30416d7d ApplicationMg W WSVR0100W: Beim Initialisieren von DefaultApplication ist ein Fehler aufgetreten.
com.ibm.ws.exception.ConfigurationWarning: No server target found for application, DefaultApplication
at com.ibm.ws.runtime.component.DeployedApplicationImpl.initialize(DeployedApplicationImpl.java:357)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.initializeApplication(ApplicationMgrImpl.java:163)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:230)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:152)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:413)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:243)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:128)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:225)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:189)
.
.
(other applications)
.
.

[17.06.05 15:55:11:125 CEST] 30416d7d RMIConnectorC A ADMC0026I: Der RMI-Connector ist an Port 2809 verf�gbar.
[17.06.05 15:55:11:359 CEST] 30416d7d WsServer A WSVR0002I: Der Server server1 ist f�r e-business bereit. Es sind Probleme beim Starten aufgetreten.

[Scott Anderson]

Can you please post all the information we request in the [URL=http://www.myeclipseide.com/PNphpBB2+file-viewtopic-t-393.html]Posting Guidelines[/URL] thread at the top of this forum? That will give us some context so that we can determine if this is an installation issue, a configuration problem, or a bug. Thanks.

[lupusire]

Operating System Win2000 SP4
Eclipse Version: 3.0.2
– Was Eclipse freshly installed for MyEclipse? no
– If not, was it upgraded to its current version using the update manager? no
other plugins: EclipseUML Free Edition Version: 2.0.0
– How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.* 8
What MyEclipse version are you using? (Help > About Eclipse Platform > Features) Version: 3.8.4
What JDK version are you using to run Eclipse? (java -version) : j2sdk1.4.2_08
What JDK version are you using to launch your application server? the jdk from websphere (142.2004.6.26)
What steps did you take that resulted in the issue? cofigure the server under window->preferences->websphere 5 then start websphere 5 from eclipse
What application server are you using? websphere5.1
Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log) no

hope this will help you to determine the problem

[Scott Anderson]

From the errors, it looks the the JMS Service is not starting properly. However, we might not be seeing all the logging information.
Have you followed the tutorial on setting up WebSphere 5.1 for logging to the Eclipse console fully? The tutorial is available here:
http://www.myeclipseide.com/Articles/WebSphere5.1LogConfiguration/WAS5.1LogConfiguration.html

Once that’s done, and you try to restart websphere with the new configuration, we’ll likely have more information as to why the issue is occuring

[lupusire]

The configuration for the logging is already set like in the tutorial shown.

We have a workstation with winXP where weblogic can be start from eclipse, but we can’t find different configurations.

[lupusire]

I have tryed it now with another winXP workstation and it also works on it.

I meant websphere not weblogic in my last reply. 🙂

[lupusire]

[Scott Anderson]

So, it works on two workstations but not on another one. What’s different between them? WebSphere versions?
Drive “D:” used for all installations?
JDK’s, configurations? Are you positive the “name of the workstation” is correct? To be sure, it should be
the same as the directory that websphere creates when started from the commandline under the ‘installedApps’ directory
under the server root.

[lupusire]

The installation of websphere is on all workstation the same.
It is on all workstations on drive “D:” with the same path.
The “host name” is also the same as the name under the “installedApps” directory.
I have tried id on three different workstations with win2000 with the same errors.
On two winxp workstations with the same websphere and eclipse installation it works.
I have tried it now with jdk update for webspher but always the same error.

[Scott Anderson]

So, it looks like it works on XP, but not Windows 2000.
If I read this link correctly:
http://www-306.ibm.com/software/webservers/appserv/doc/v51/prereqs/client_v51.htm

IBM says Websphere 5.1 needs certain SP level patches on Windows 2000 machines. Can you see if the machines
that are problematic have been patched to the level required by IBM and that they’re running Winoows Server 2000,
not the client OS, as required?

You can also generate a script to start that specific server, so you can check the launch arguments, by changing directory into
the Websphere 5.1 bin directory and running startServer.bat <server-name> -script <name-for-new-script-file>
That will allow you to compare what’s done one the commandline to see if any extra jars are added for that particular OS config
that aren’t needed on XP.

[lupusire]

we have all windows 2000 professional

and on the site
http://www-306.ibm.com/software/webservers/appserv/doc/v51/prereqs/was_v51.htm
I see only support for windows 2000 SERVER 🙁
when I start websphere with its startscript the server starts and I can deploy my application. now I will try it with starting the server with debug mode

thank you for your help[/url]

[Scott Anderson]

The other thing to check is the startup script, generated as I mentioned above, against your connector settings.
It might just be there is something unique in what has to happen on Windows 2000 and the script compensates.
If you find a difference, you can likely compensate by setting additional path entries or java library dirs on the
Paths page of the connector settings.

[lupusire]

I have insert in Eclipse by Window->Preferences->MyEclipse->Application Servers->WebSphere 5->JDK in the “Optional Java VM Arguments” the parameters from the script and under path in the classpath. The arguments were displayed in the console when I started the Server but otherwise with the same errors.

[Author]

Posts