Web Access service stops with Event ID: 7034

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When VMware Infrastructure Web Access is set to start automatically or is started manually, it briefly starts, but the service then unexpectedly stops.
• Windows Event Viewer shows that it went down with Event ID: 7034.
• In the Tomcat Catalina log, located at C:\Program Files\VMware\Infrastructure\VirtualCenter Server\tomcat\logs, you see entries similar to:
  
  SEVERE: StandardServer.await: create[8005]:
  java.net.BindException: Address already in use: JVM_Bind
  at java.net.PlainSocketImpl.socketBind(Native Method)
  at java.net.PlainSocketImpl.bind(Unknown Source)
  at java.net.ServerSocket.bind(Unknown Source)
  at java.net.ServerSocket.<init>(Unknown Source)
  at org.apache.catalina.core.StandardServer.await(StandardServer.java:363)
  at org.apache.catalina.startup.Catalina.await(Catalina.java:616)
  at org.apache.catalina.startup.Catalina.start(Catalina.java:576)
  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
  at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
  at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
  at java.lang.reflect.Method.invoke(Unknown Source)
  at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
  at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)

Environment

VMware VirtualCenter 2.5.x
VMware vCenter Server 5.5.x
VMware vCenter Server 5.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 4.0.x
VMware vCenter Server 5.1.x

Cause

These entries indicate that Tomcat is having a port conflict on the default Tomcat port of 8005 for vCenter Server 2.5, 4.x and 5.0. vCenter Server 5.1 and 5.5 default Tomcat port is 8003.

Resolution

To resolve this issue, ensure that there is no other software using this port or change the port that Tomcat is using.

Note: If you change the default Tomcat port, you may experience issues with the Performance charts and Hardware Status and Health Status tabs in vCenter Server.

To determine what application may be using the default port 8005 or 8003:

1. From the vCenter Server, open a command prompt and run this command:
   
netstat -anob | find /N "defaultPort"
   
   Note: Where defaultPort is the default Tomcat port for your version of vCenter Server.
   
   

2. Make a note of the PID (last column).
3. Go to Task Manager > View > Select Columns, select PID, then click OK.
4. Search Windows Task Manager for the PID that you noted from the netstat</u> command.
5. If you see an application with port 8005 or 8003, select and click End Process.
6. Start the Web Access Service and monitor.

If the service still fails, change the port that Tomcat is using for vCenter Server 2.5, 4.x and 5.0:

1. Open the Tomcat server.xml file:
   
   
   • vCenter Server 2.5: C:\Program Files\VMware\Infrastructure\VirtualCenter Server\tomcat\conf\server.xml
   • vCenter Server 4.x and 5.0: C:\Program Files\VMware\Infrastructure\tomcat\conf\server.xml


2. Change the entry for the port from:
   
   <Server port="8005" shutdown="SHUTDOWN">

to:
   
   <Server port="8006" shutdown="SHUTDOWN">

For vCenter Server 5.1 and 5.5:

1. Open the Tomcat catalina.properties file from:
   
   
   • vCenter Server 5.1 and 5.5: C:\Program Files\VMware\Infrastructure\tomcat\conf\catalina.properties
     

2. Change the entry for the port from:
   
   base.shutdown.port=8003
   
   to:
   
   base.shutdown.port=8004
   

Additional Information

Web Access サービスがイベント ID： 7034 で停止する
Web Access 服务停止并显示事件 ID：7034