| Author |
Message
|
| vennela |
 Posted: Fri Jun 17, 2005 5:15 pm Post subject: WAS: (ND) WSVR0009E |
 |
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
I have the following all on the same TEST machine.
WAS6 -> default profile
WAS6 -> svr1 profile
ND6 -> profile -> Dmgr01
I successfully added both the instances (server1 in default profile and svr1 profile) in ND. I can start the server1 of the default profile, but cannot start the server1 on svr1 profile. Below is the error.
| Quote: |
WSVR0009E: Error occurred during startup
com.ibm.ws.exception.RuntimeError: com.ibm.ws.exception.RuntimeError: com.ibm.ejs.EJSException: Could not register with Location Service Daemon, which could only reside in the NodeAgent. Make sure the NodeAgent for this node is up an running.; nested exception is:
org.omg.CORBA.ORBPackage.InvalidName: LocationService:org.omg.CORBA.TRANSIENT: java.net.ConnectException: Connection refused: connect:host=vennela,port=9902 vmcid: IBM minor code: E02 completed: No |
|
|
| Back to top |
|
 |
| vennela |
| Posted: Fri Jun 17, 2005 8:58 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Looks like I have to start the node agent (using the startNode ) before I start the application server. After I did that I could see the status of the server. I could start/stop the app server after that, but I still am not sure if that is what the problem was.
Still trying to learn |
|
| Back to top |
|
|
| JLRowe |
| Posted: Sat Jun 18, 2005 9:30 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
The node agent can start the application servers for you through the deployment manager console.
Also, do you have 2 installs (base + ND)? This isn't wrong, but it may confuse the profile creation wizard which normally does a good job of allocating unique ports per node/server/dmgr. |
|
| Back to top |
|
|
| vennela |
| Posted: Mon Jun 20, 2005 9:15 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| JLRowe wrote: |
Also, do you have 2 installs (base + ND)? This isn't wrong, |
Yes, I have 2 installs.
So, in real time, I should be having ND on machine and all the WAS installations on whatever machines and not have any WAS installation on the ND machine.... is that what you are saying is a good thing to do? |
|
| Back to top |
|
|
| JLRowe |
| Posted: Mon Jun 20, 2005 11:31 pm Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
Just install WAS ND on each machine. The WAS ND install is a superset of the WAS base install. You can create standalone app servers under WAS ND, you do not have to federate them into the cell.
You would have 2 installs of WAS if you wanted to keep them on different fix packs. All the product code is shared between the profiles, so when you install a fix pack into an install you upgrade all your profiles.
BTW, are you on windows? I have created a service for each node agent on each machine, the service starts fine but I cannot stop it... The service actually stops but the process is still running! |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Aug 04, 2005 2:42 pm Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| Quote: |
| The WAS ND install is a superset of the WAS base install. You can create standalone app servers under WAS ND, you do not have to federate them into the cell. |
Is this true with WAS5 also or is it just for WAS6? |
|
| Back to top |
|
|
| JLRowe |
| Posted: Fri Aug 05, 2005 1:06 am Post subject: |
|
|
Yatiri
Joined: 25 May 2002
Posts: 664
Location: South East London
|
With WAS5, the base (app server + node manager) and the deployment manager were seperate installs.
With WAS5, if you had an app server and deployment manager installed on one machine, you would have to apply maintenance to each install seperately. With WAS6, you only need to apply maintenance once - much nicer! |
|
| Back to top |
|
|
|
|
