[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.
Question
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!
9.3

WAS 6.1 Server Port Conflict...

Asked by Mdavis0816 in IBM Websphere Application Server

Tags: WAS v6.1

Hello,

I am receiving the following error when attempting to start up my WAS v6.1 server in RSA 7. I have verified that the port is not in use (listening or active). Even after a restarting XP and going directly into RSA, I receive the same error at this point. This server had previously worked for the past few days, and no changes have been made to it whatsoever. Additionally, I have not added any additional servers or profiles within RSA.

Thanks for any advice! 
1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26:
27:
28:
29:
30:
31:
32:
33:
34:
35:
36:
37:
38:

[9/2/09 16:10:27:867 CDT] 0000000a ManagerAdmin  I   TRAS0017I: The startup trace state is *=info:com.ibm.*=all.
[9/2/09 16:10:27:867 CDT] 0000000a WsServerContr 1   Executing executeUtilityOnWindows with args: C:\SDP\V7\runtimes\base_v61\profiles\SAMS_4.0\config WPWDCCJ0Node02Cell WPWDCCJ0Node02 server1 
[9/2/09 16:10:27:867 CDT] 0000000a WsServerContr 1   Getting WindowsService obj with: server1 and C:\SDP\V7\runtimes\base_v61\profiles\SAMS_4.0\config WPWDCCJ0Node02Cell WPWDCCJ0Node02 server1 
[9/2/09 16:10:27:882 CDT] 0000000a WindowsServic >  getWindowsServiceNameForServer() Entry
[9/2/09 16:10:27:882 CDT] 0000000a WindowsServic 1   In executeCommand, args are: C:\SDP\V7\runtimes\base_v61\bin\WASService.exe -getServiceName server1 -profilePath C:\SDP\V7\runtimes\base_v61\profiles\SAMS_4.0 
[9/2/09 16:10:27:961 CDT] 0000000a WindowsServic 1   Runtime.exec() returned process java.lang.ProcessImpl@7fbe7fbe
[9/2/09 16:10:28:008 CDT] 0000000a WindowsServic 1   retCode from childProcess.waitFor() is 0
[9/2/09 16:10:28:008 CDT] 0000000a WindowsServic 3   exitCode = 0
[9/2/09 16:10:29:008 CDT] 0000000a WindowsServic 1   Trying to new up WindowsService using serverName=server1, winServiceName=null
[9/2/09 16:10:29:008 CDT] 0000000a ManagerAdmin  I   TRAS0018I: The trace state has changed. The new trace state is *=info.
[9/2/09 16:10:29:399 CDT] 0000000a AdminTool     A   ADMU0128I: Starting tool with the SAMS_4.0 profile
[9/2/09 16:10:29:399 CDT] 0000000a AdminTool     A   ADMU3100I: Reading configuration for server: server1
[9/2/09 16:10:32:463 CDT] 0000000a AdminTool     A   ADMU3028I: Conflict detected on port 8889.  Likely causes: a) An instance of the server server1 is already running  b) some other process is using port 8889
[9/2/09 16:10:32:463 CDT] 0000000a AdminTool     A   ADMU3027E: An instance of the server may already be running: server1
[9/2/09 16:10:32:463 CDT] 0000000a WsServerLaunc E   ADMU3002E: Exception attempting to process server server1
[9/2/09 16:10:32:463 CDT] 0000000a WsServerLaunc E   ADMU3007E: Exception com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1
	at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:304)
	at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
	at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:136)
	at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:126)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:618)
	at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)
 
[9/2/09 16:10:32:510 CDT] 0000000a AdminTool     E   ADMU0111E: Program exiting with error: com.ibm.websphere.management.exception.AdminException: ADMU3027E: An instance of the server may already be running: server1
	at com.ibm.ws.management.tools.WsServerLauncher.runTool(WsServerLauncher.java:304)
	at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:264)
	at com.ibm.ws.management.tools.WsServerController.executeUtilityOnWindows(WsServerController.java:136)
	at com.ibm.ws.management.tools.WsServerLauncher.main(WsServerLauncher.java:126)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:618)
	at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:263)
[9/2/09 16:10:32:510 CDT] 0000000a AdminTool     A   ADMU1211I: To obtain a full trace of the failure, use the -trace option.
[9/2/09 16:10:32:510 CDT] 0000000a AdminTool     A   ADMU0211I: Error details may be seen in the file: C:\SDP\V7\runtimes\base_v61\profiles\SAMS_4.0\logs\server1\startServer.log
[+][-]09/02/09 07:52 PM, ID: 25247509Accepted Solution

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

About this solution

Zone: IBM Websphere Application Server
Tags: WAS v6.1
Sign Up Now!
Solution Provided By: pkwan
Participating Experts: 1
Solution Grade: A
 
[+][-]09/03/09 05:39 AM, ID: 25249983Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
[+][-]09/03/09 05:43 AM, ID: 25250018Author Comment

Often, when Experts are collaborating with members who have asked questions, they will request additional information about the problem. Askers respond with an author comment like this one.

Start your 30-day free trial to view this Author Comment or ask the Experts your question.

 
 
Loading Advertisement...
20091111-EE-VQP-92 - Hierarchy / EE_QW_3_20080625