was服务一直起不来,急急急.......
[11-11-9 20:43:56:440 CST] 7b7f7d45 SASRas A JSAS0005I: 已注册 SecurityCurrent。
[11-11-9 20:43:56:440 CST] 7b7f7d45 SASRas A JSAS0006I: 已初始化安全性连接拦截器。
[11-11-9 20:43:56:455 CST] 7b7f7d45 SASRas A JSAS0007I: 已注册客户机请求拦截器。
[11-11-9 20:43:56:549 CST] 7b7f7d45 SASRas A JSAS0008I: 已注册服务器请求拦截器。
[11-11-9 20:43:56:580 CST] 7b7f7d45 SASRas A JSAS0009I: 已注册 IOR 拦截器。
[11-11-9 20:43:57:154 CST] 7b7f7d45 NameServerImp E NMSV0011E: 无法使用端口 2809 启动引导服务器。验证没有服务器或其它进程已正在使用引导服务器端口。同时验证正在使用具有足够（例如，root，管理员）特权的用户标识来启动引导服务器。
org.omg.CORBA.INTERNAL: CREATE_LISTENER_FAILED_4 vmcid: 0x49421000 minor code: 56 completed: No
[11-11-9 20:43:57:340 CST] 7b7f7d45 WsServer E WSVR0003E: 服务器 server1 无法启动
com.ibm.ws.exception.RuntimeError: Unable to initialize the Name Service
at com.ibm.ws.naming.bootstrap.NameServerImpl.start(NameServerImpl.java:402)
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:183)
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:79)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:41)
at java.lang.reflect.Method.invoke(Method.java:386)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)
Caused by: com.ibm.ws.naming.distcos.NameSpaceConstructionException: Unable to start bootstrap server using port 2809. 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.
at com.ibm.ws.naming.bootstrap.NameServerImpl.startBootstrapService(NameServerImpl.java:640)
错误日志如上,请好心人帮忙
[解决办法]
新手， 让高手来解答
日志显示端口被暂用
netstat -aon
[解决办法]
findstr "2809" 查看下是什么进程占用，如果了解的话把它终止再试试
taskkill /pid XXX /F
