File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Websphere and the fly likes WAS 5 and Windows XP? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » Websphere
Bookmark "WAS 5 and Windows XP?" Watch "WAS 5 and Windows XP?" New topic
Author

WAS 5 and Windows XP?

John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
I have successfully installed WAS 5 on Windows XP, but when the server starts I get a message "failed to initialize" (the server does not ever actually start)...I have heard others mention that they can get this configuration to work...any suggestions?


www.websiteandsound.com
"If you do what you've always done, you'll get what you've always gotten."
Johannes de Jong
tumbleweed
Bartender

Joined: Jan 27, 2001
Posts: 5089
John I have the same problem.
In my case I think its because I have WSAD 5.0 installed on the same machine. As I can start my server from inside WSAD I have not bothered to look into it much deeper.
If I can find the time I will try and determine the actual cause.
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
Originally posted by Johannes de Jong:
John I have the same problem.
In my case I think its because I have WSAD 5.0 installed on the same machine.

In case it helps narrow down the problem, I do not have WSAD installed. Maybe WSAD launches WAS with command line arguments that resolve the issue...
John Dale
Ranch Hand

Joined: Feb 22, 2001
Posts: 399
I don't know anything about XP. I assume you are not using Home Edition.
You don't mention what you saw in the log files. I don't have enough WAS experience to tell you the best way to go about this, but I think you may want to look at the following. I'll be happy to look at this with you.
There are several ways to start WAS, but until you get past problems, it is probably best to use startServer.
cd <WAS base directory>\bin
startServer <servername>
If you need to check the servername, use
serverStatus -all
cd <WAS base dir>\logs\<servername> .
Look at startServer.log . If thing go well, this contains just a few routine message describing the environment and listing the console messages from the startup.
If systemErr.log is not empty, you will want to look at that.
systemOut.log normally provides line showing the startup in initialization of each part of the system, and error messages in context.
I think native_stderr.log and native_stdout.out are used for output to low level to be intercepted by WAS. If non-empty, you want to check out what's there.
There is also a GUI tool for displaying log data and checking errors against IBM the support knowledge base. But since I've not done enough with it to have a feel for whether it would help here, I'd start with the logs above.
Christophe Lee
Ranch Hand

Joined: Jul 10, 2001
Posts: 142
Please give the full error message and how you are starting. I am running WSAD5 and WAS5 on XP...so far so good.
The only thing I can think of off the top of my head is that you may not have set up a pre-existing username/password (from your OS) during the initial installation of WAS.
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
Here are some clues from SystemOut.log:
[5/7/03 17:44:16:641 EDT] 5dd8a6fa JMSEmbeddedPr A MSGS0050I: Starting the Queue Manager
[5/7/03 17:44:16:688 EDT] 5dd8a6fa JMSEmbeddedPr E MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed
[5/7/03 17:44:16:703 EDT] 5dd8a6fa JMSService E MSGS0001E: Starting the JMS Server failed with exception: java.lang.Exception: MSGS0058E: Unable to start the JMS Server as WebSphere Embedded Messaging has not been installed
at com.ibm.ws.messaging.JMSEmbeddedProviderImpl.start(JMSEmbeddedProviderImpl.java:213)
at com.ibm.ws.messaging.JMSService.start(JMSService.java:251)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:343)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:234)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:182)
at com.ibm.ws.runtime.WsServer.start(WsServer.java:135)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:232)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

And then further down this error:
[5/7/03 17:45:07:453 EDT] 5dd8a6fa ApplicationMg A WSVR0200I: Starting application: MDBSamples
[5/7/03 17:45:07:812 EDT] 5dd8a6fa EJBContainerI I WSVR0207I: Preparing to start EJB jar: PtoPSampleMDB.jar
[5/7/03 17:45:08:141 EDT] 5dd8a6fa Helpers W NMSV0605W: A Reference object looked up from the context "java:" with the name "comp/env/jms/SamplePPQCF" was sent to the JNDI Naming Manager and an exception resulted. Reference data follows:
Reference Factory Class Name: com.ibm.ws.util.ResRefJndiLookupObjectFactory
Reference Factory Class Location URLs: <null>
Reference Class Name: java.lang.Object
Type: ResRefJndiLookupInfo
Content: com.ibm.ws.util.ResRefJndiLookupInfo@5a4ce6db ResRefJndiLookupInfo: Look up Name="jms/SamplePPQCF";JndiLookupInfo: jndiName="Sample/JMS/QCF"; providerURL=""; initialContextFactory=""
Exception data follows:
javax.naming.NameNotFoundException: Sample/JMS/QCF
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)

I tried a clean reinstall -- still the same...
John Dale
Ranch Hand

Joined: Feb 22, 2001
Posts: 399
I suspect you installed an example appliction that uses message driven beans, but don't have a JMS server. Either you didn't specify to install an embedded messaging server, or installation of the messaging server failed.
Do you recall passing up a chance to install the embedded messaging server during the install? It is well down in the feature checkboxes you get if you select customer install. Right below that is an option to install message driven beans examples.
Installation is logged in the base log directory, e.g., c:\program files\websphere\logs, one level above the server startup logs we've been discussing. Installation of embedded messaging is logged in mq_install.log. Configuration of embedded messaging is logged in files that start with createMQ .
I forgot to ask whether you ran the install verification tool, "Verify Installation" in the First Steps program. But glancing at my ivt.log, I don't see any mention of checking the JMS/embedded messaging server, so perhaps it does't check that for you. Still, if you haven't done the verification, you probably should.
I found the WAS 5 terminology for Java messaging servers a bit confusing, at least initially. I think it works like this: Message driven beans (MDBs) need a JMS server. Your JMS server can be either the embedded JMS server (aka as WebSphere JMS, shipped with the base WAS, or the more comprehensive WebSphere MQ product, which also functions as a JMS provider. What's confusing is that the the term MQ is used to describe features of the embedded WebSphere JMS server (which may be a stripped-down version of WebSphere MQ). Anyway, if you want to install the MDB examples, you need the embedded messaging server, aka jmsserver.
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
I just did a custom install -- I deselected Example Applications and let it roll. I still get error about JMS. (Along with that uselessly long list of stack traces that result afterwards).
Will await word on any other ideas...meanwhile will stick with JRun and Weblogic which all work perfectly after the first try...
John Dale
Ranch Hand

Joined: Feb 22, 2001
Posts: 399
If you still have it, I'm really curious about what is in logs\mq_install.log .
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
Originally posted by John Dale:
If you still have it, I'm really curious about what is in logs\mq_install.log .

Found no file by that name...but I did find a file called createMQ.perry_server1.log (created during last installation), and another called deleteMQ.perry_server1.log (created during custom install without example apps)...they are both chock-full of exceptions, if you like I can post them...meanwhile there is one other clue that may help...(or just compound the problem further ;-) ):
SRVE0146E: Failed to Start Transport on host , port 9090. The most likely cause is that the port is already in use.

I know that port 9090 is in use by an Oracle listener application, TNSLSNR.EXE. So I stopped Oracle processes, and restarted. This time the server initialized, but upon opening the admin, I get this message in browser:
Virtual Host or Web Application Not Found
The web group /admin has not been defined

Additinally, SystemOut.log looks like it's still trying to start example applications:

[5/10/03 2:53:20:094 EDT] 2121387d MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: Sample/JMS/Q1
[5/10/03 2:53:20:109 EDT] 2121387d MDBListenerIm W WMSG0019E: Unable to start MDB Listener PtoPSampleMDB, JMSDestination Sample/JMS/Q1 : javax.naming.NameNotFoundException: Sample/JMS/Q1
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[5/10/03 2:53:26:672 EDT] 26f8b87e OSEListenerDi E PLGN0021E: Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /admin/ has not been defined
[5/10/03 2:53:42:766 EDT] 26f8b87e OSEListenerDi E PLGN0021E: Servlet Request Processor Exception: Virtual Host/WebGroup Not Found : The web group /ivt/ivtserver has not been defined
[5/10/03 2:54:20:156 EDT] 2121387d MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: Sample/JMS/Q1
[5/10/03 2:54:20:266 EDT] 2121387d MDBListenerIm W WMSG0019E: Unable to start MDB Listener PtoPSampleMDB, JMSDestination Sample/JMS/Q1 : javax.naming.NameNotFoundException: Sample/JMS/Q1
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[5/10/03 2:54:20:297 EDT] 7ee3f867 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: Sample/JMS/listen
[5/10/03 2:54:20:312 EDT] 7ee3f867 MDBListenerIm W WMSG0019E: Unable to start MDB Listener PSSampleMDB, JMSDestination Sample/JMS/listen : javax.naming.NameNotFoundException: Sample/JMS/listen
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[5/10/03 2:55:20:359 EDT] f207861 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: Sample/JMS/listen
[5/10/03 2:55:20:375 EDT] 7ee3f867 MDBListenerIm W WMSG0017E: Unable to lookup JMS resources, JNDI lookup exception: Sample/JMS/Q1
[5/10/03 2:55:20:391 EDT] f207861 MDBListenerIm W WMSG0019E: Unable to start MDB Listener PSSampleMDB, JMSDestination Sample/JMS/listen : javax.naming.NameNotFoundException: Sample/JMS/listen
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[5/10/03 2:55:20:406 EDT] 7ee3f867 MDBListenerIm W WMSG0019E: Unable to start MDB Listener PtoPSampleMDB, JMSDestination Sample/JMS/Q1 : javax.naming.NameNotFoundException: Sample/JMS/Q1
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1503)
at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1457)
at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1167)
at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:132)
at javax.naming.InitialContext.lookup(InitialContext.java:359)
at com.ibm.ejs.jms.listener.MDBListenerImpl.createResources(MDBListenerImpl.java:199)
at com.ibm.ejs.jms.listener.MDBListenerImpl.internalStart(MDBListenerImpl.java:474)
at com.ibm.ejs.jms.listener.MDBListenerImpl.restart(MDBListenerImpl.java:446)
at com.ibm.ejs.jms.listener.MDBListenerImpl.alarm(MDBListenerImpl.java:718)
at com.ibm.ejs.util.am._Alarm.run(_Alarm.java:80)
at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:592)
[5/10/03 2:55:48:016 EDT] 2121387d HttpTransport A SRVE0172I: Stopped transport http on port 9,080.
[5/10/03 2:55:48:031 EDT] 2121387d HttpTransport A SRVE0172I: Stopped transport https on port 9,443.
[5/10/03 2:55:48:047 EDT] 2121387d HttpTransport A SRVE0172I: Stopped transport http on port 9,090.
[5/10/03 2:55:48:062 EDT] 2121387d HttpTransport A SRVE0172I: Stopped transport https on port 9,043.
[5/10/03 2:55:53:125 EDT] 2121387d ApplicationMg A WSVR0217I: Stopping application: MDBSamples
[5/10/03 2:55:53:219 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:266 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/ko] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:266 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/ko] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:297 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:312 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/es] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:312 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/es] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:328 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:344 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/pt_br] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:359 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/pt_br] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:359 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:375 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/ja] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:391 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/ja] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:391 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:422 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/it] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:469 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/it] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:484 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:500 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/de] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:500 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/de] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:516 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:531 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/fr] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:531 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/fr] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:547 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:562 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/zh_tw] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:562 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/zh_tw] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:578 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:594 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/zh_cn] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:594 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/zh_cn] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:609 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:625 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/en] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:625 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs/en] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:625 EDT] 2121387d WebContainer A SRVE0170I: Stopping Web Module: MessageDrivenBeanSample.
[5/10/03 2:55:53:641 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs] [Servlet.LOG]: SimpleFileServlet: destroy
[5/10/03 2:55:53:656 EDT] 2121387d WebGroup I SRVE0180I: [MessageDrivenBeanSample] [/MessageDrivenBeans/docs] [Servlet.LOG]: JSP 1.2 Processor: destroy
[5/10/03 2:55:53:656 EDT] 2121387d EJBContainerI I WSVR0041I: Stopping EJB jar: PSSampleMDB.jar
[5/10/03 2:55:53:672 EDT] 2121387d EJBContainerI I WSVR0041I: Stopping EJB jar: PtoPSampleMDB.jar
[5/10/03 2:55:53:672 EDT] 2121387d ApplicationMg A WSVR0220I: Application stopped: MDBSamples
[5/10/03 2:55:54:312 EDT] 2121387d ServerCollabo A WSVR0024I: Server server1 stopped

[ May 10, 2003: Message edited by: John Fontana ]
John Dale
Ranch Hand

Joined: Feb 22, 2001
Posts: 399
Hmm. Never tried to install when something else was running on port 9090. I wonder if that confused the WAS install. In some cases, WAS will offer use use different port numbers to avoid conflicts with other WAS configurations installed on the same platform.
Here is a theory: Perhaps the WAS install saw that you had port 9090 active, assumed that meant you have a WebSphere network manager running on the node (since 9090 is the default port for web access to the network manager), and helped you out by not installing the adminconsole application, which provides the web prefix /admin.
You could take a superficial look to see what EARs are at least partially installed on your server.
Go to the server directory under installedApps in your AppServer directory.
Do you see a folder adminconsole.ear?
How about folder MDBSamples.ear?
I think what you would want to see in a base WAS install with no MDB or samples, would be
DefaultApplication.ear
adminconsole.ear
ivtApp.ear
If your install was successful except for these points, it can be fixed, I think. But it may be better to start over.
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
John - I think you nailed it!
The dumb MDBSample app was the only one in the installedApps folder...I put DefaultApplication.ear, adminconsole.ear, ivtApp.ear in installed apps folder -- now there is just an error 404 trying to find SimpleFileServlet.
Guess I'll reinstall while Oracle is stopped, then try changing port numbers in config files once it's working...will post results.
John Dale
Ranch Hand

Joined: Feb 22, 2001
Posts: 399
John Fontana
Ranch Hand

Joined: Feb 28, 2002
Posts: 235
And smile you should, John..that's what did it....
I'd like to note for the archives that I installed using IIS plug-in...to remove lingering Websphere directory after uninstall I had to stop the site via IIS snap-in (not services control panel)...
Ten I did a search and replace on all occurences of 9090 in AppServer directory (replaced with 9091, which is unused on my machine)...
Thanks very much, J.D.!
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: WAS 5 and Windows XP?