Win a copy of Testing JavaScript Applications this week in the HTML Pages with CSS and JavaScript forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Problem starting webshere

 
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi all
Anyone has problem installing and starting websphere application server 4.0 on XP ? I keep getting the following series of errors.
----------------------------------
[02.03.26 24:33:58:246 CST] df1a7e0 Server U Version : 4.0.1
[02.03.26 24:33:58:246 CST] df1a7e0 Server U Edition: Advanced Single Server Edition for Multiplatforms
[02.03.26 24:33:58:246 CST] df1a7e0 Server U Build date: Thu Aug 09 00:00:00 CST 2001
[02.03.26 24:33:58:256 CST] df1a7e0 Server U Build number: a0131.07
[02.03.26 24:34:00:760 CST] df1a7e0 NameServer F NMSV0011E: Unable to start bootstrap server using port localhost:900. Verify that no servers or other processes are already using the bootstrap server port. Also verify that the bootstrap server is being started with a user ID which has sufficient (e.g., root, Administrator) privileges.
org.omg.CORBA.INTERNAL: minor code: 8 completed: No
at com.ibm.CORBA.iiop.GIOPImpl.createListener(GIOPImpl.java:333)
at com.ibm.CORBA.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:461)
at com.ibm.CORBA.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:524)
at com.ibm.rmi.iiop.GIOPImpl.getBootstrapEndpoint(GIOPImpl.java:226)
at com.ibm.ejs.ns.CosNaming.BootstrapServer.start(BootstrapServer.java:147)
at com.ibm.ws.naming.bootstrap.NameServer.startBootstrapService(NameServer.java:350)
at com.ibm.ws.naming.bootstrap.NameServer.doInit(NameServer.java:241)
at com.ibm.ws.naming.bootstrap.NameServer.initialize(NameServer.java:107)
at com.ibm.ws.runtime.Server.initializeNameService(Server.java:1594)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:947)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
.
-------------------------------
[02.03.27 24:27:58:778 CST] df1cff5 Server U Version : 4.0.1
[02.03.27 24:27:58:778 CST] df1cff5 Server U Edition: Advanced Single Server Edition for Multiplatforms
[02.03.27 24:27:58:778 CST] df1cff5 Server U Build date: Thu Aug 09 00:00:00 CST 2001
[02.03.27 24:27:58:778 CST] df1cff5 Server U Build number: a0131.07
[02.03.27 24:28:03:625 CST] df1cff5 NameServer F NMSV0011E: Unable to start bootstrap server using port localhost:99900. Verify that no servers or other processes are already using the bootstrap server port. Also verify that the bootstrap server is being started with a user ID which has sufficient (e.g., root, Administrator) privileges.
org.omg.CORBA.INTERNAL: minor code: 8 completed: No
at com.ibm.CORBA.iiop.GIOPImpl.createListener(GIOPImpl.java:333)
at com.ibm.CORBA.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:461)
at com.ibm.CORBA.iiop.GIOPImpl.getEndpoint(GIOPImpl.java:524)
at com.ibm.rmi.iiop.GIOPImpl.getBootstrapEndpoint(GIOPImpl.java:226)
at com.ibm.ejs.ns.CosNaming.BootstrapServer.start(BootstrapServer.java:147)
at com.ibm.ws.naming.bootstrap.NameServer.startBootstrapService(NameServer.java:350)
at com.ibm.ws.naming.bootstrap.NameServer.doInit(NameServer.java:241)
at com.ibm.ws.naming.bootstrap.NameServer.initialize(NameServer.java:107)
at com.ibm.ws.runtime.Server.initializeNameService(Server.java:1594)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:947)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
.
---------------------------------------
[02.03.27 24:33:00:502 CST] df1d08d Server U Version : 4.0.1
[02.03.27 24:33:00:512 CST] df1d08d Server U Edition: Advanced Single Server Edition for Multiplatforms
[02.03.27 24:33:00:512 CST] df1d08d Server U Build date: Thu Aug 09 00:00:00 CST 2001
[02.03.27 24:33:00:512 CST] df1d08d Server U Build number: a0131.07
[02.03.27 24:33:03:176 CST] df1d08d DrAdminServer I WSVR0054E: Failed to create a server socket, the port 7000 maybe in use: Address in use: bind
[02.03.27 24:33:03:176 CST] df1d08d StandardServe F WSVR0006E: Server Default Server failed during initialization : java.lang.NullPointerException
at com.ibm.ejs.sm.util.debug.DrAdminServer.getServerPort(DrAdminServer.java:470)
at com.ibm.ejs.sm.util.debug.DrAdminServer$ServerRunner.getServerPort(DrAdminServer.java:248)
at com.ibm.ejs.sm.util.debug.DrAdminServer.runServer(DrAdminServer.java:228)
at com.ibm.ws.runtime.Server.initializeDiagnosticThread(Server.java:1625)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:957)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
--------------------------------------
02.03.27 24:55:04:260 CST] df1d31b Server U Version : 4.0.1
[02.03.27 24:55:04:260 CST] df1d31b Server U Edition: Advanced Single Server Edition for Multiplatforms
[02.03.27 24:55:04:260 CST] df1d31b Server U Build date: Thu Aug 09 00:00:00 CST 2001
[02.03.27 24:55:04:260 CST] df1d31b Server U Build number: a0131.07
[02.03.27 24:55:04:340 CST] df1d31b Jts U Unexpected failure during transaction factory registration
java.lang.NullPointerException
at com.ibm.ejs.jts.jts.Jts.bindTransactionFactory(Jts.java:192)
at com.ibm.ws.runtime.Server.initializeTranFactory(Server.java:1600)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:949)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
[02.03.27 24:55:07:354 CST] df1d31b DrAdminServer I WSVR0054E: Failed to create a server socket, the port 7000 maybe in use: Address in use: bind
[02.03.27 24:55:07:354 CST] df1d31b StandardServe F WSVR0006E: Server kodomo failed during initialization : java.lang.NullPointerException
at com.ibm.ejs.sm.util.debug.DrAdminServer.getServerPort(DrAdminServer.java:470)
at com.ibm.ejs.sm.util.debug.DrAdminServer$ServerRunner.getServerPort(DrAdminServer.java:248)
at com.ibm.ejs.sm.util.debug.DrAdminServer.runServer(DrAdminServer.java:228)
at com.ibm.ws.runtime.Server.initializeDiagnosticThread(Server.java:1625)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:957)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
 
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Restart your OS to release these ports, or you can modify the port for websphere manually to overcome the conflicts.
 
Kodo Tan
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Simon
Yes, I have done that but I still cannot startup websphere
 
Simon Song
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
This is not a WAS problem...you must release the port number reserved for default WAS startup. Or you have to manually change the port number for WAS startup process.
Fix conflicting ports in the WebSphere Application Server instances. Choose port numbers not being used by other applications. For the Version 4.0.x Advanced Single Server Edition, open an editor on the WebSphere40 AppServer config server-cfg.xml file and find the element
<locationServiceDaemon>
Change the port to 9001. Next, find the element
<orbSettings>
Change the bootstrapPort to 901.
 
Kodo Tan
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Simon
Thanks for the instructions. I tried but I get a new error. I have been troubleshooting for some days without successful
---------------------
[02.03.30 11:14:42:000 CST] df315f3 Server U Version : 4.0.1
[02.03.30 11:14:42:000 CST] df315f3 Server U Edition: Advanced Single Server Edition for Multiplatforms
[02.03.30 11:14:42:000 CST] df315f3 Server U Build date: Thu Aug 09 00:00:00 CST 2001
[02.03.30 11:14:42:010 CST] df315f3 Server U Build number: a0131.07
[02.03.30 11:14:42:250 CST] df315f3 Jts U Unexpected failure during transaction factory registration
java.lang.NullPointerException
at com.ibm.ejs.jts.jts.Jts.bindTransactionFactory(Jts.java:192)
at com.ibm.ws.runtime.Server.initializeTranFactory(Server.java:1600)
at com.ibm.ws.runtime.Server.initializeRuntime0(Server.java:949)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:341)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
[02.03.30 11:14:46:947 CST] df315f3 DrAdminServer I WSVR0053I: DrAdmin available on port 7000
[02.03.30 11:14:49:230 CST] df315f3 WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.
[02.03.30 11:14:49:260 CST] df315f3 StandardServe F WSVR0006E: Server kodomo failed during initialization : java.lang.RuntimeException: Error creating jta/ context in JNDI
at com.ibm.ws.runtime.Server.exportUserTx(Server.java:1714)
at com.ibm.ws.runtime.StandardServer.initializeRuntime0(StandardServer.java:342)
at com.ibm.ws.runtime.Server.initializeRuntime(Server.java:882)
at com.ibm.ws.runtime.StandardServer.main(StandardServer.java:519)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:158)
 
Kodo Tan
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I can run websphere now but it seems that I cannot access http://localhost:9080.
 
Simon Song
Ranch Hand
Posts: 217
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Again, look into your config xml file for 9080 port change it to some bigger number like 90809 and connect to that port.
What's your OS? Unix? Unix has limitation on port, port under 1024 is only available to root user.
 
Kodo Tan
Ranch Hand
Posts: 105
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Simon
the log said that http is listening successfully at 9080 but I cannot access http://localhost:9080
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
Can anyone help me.
I have the same problem, but port 9080 is free, and receive the message:
WsnInitCtxFac W NMSV0602E: Naming Service unavailable. A communications error occurred.
[10/4/02 13:39:58:124 GMT-03:00] 7b74ef76 Nanny W SMTL0012W: Waiting for initial context javax.naming.CommunicationException: Caught CORBA.COMM_FAILURE when resolving initial reference=WsnNameService. Root exception is org.omg.CORBA.COMM_FAILURE: minor code: 3 completed: No

thanks
    Bookmark Topic Watch Topic
  • New Topic