My Oracle Support Banner

Oracle Enterprise Metadata Management (OEMM) Window Service Does Not Start (Doc ID 2378262.1)

Last updated on MARCH 30, 2018

Applies to:

Oracle Enterprise Metadata Management - Version 12.2.1.1 and later
Information in this document applies to any platform.

Symptoms

On Oracle Enterprise Metadata Management (OEMM) 12.2.1.2, the error below occurs when trying to start the Windows OEMM Service:

Mar 23, 2018 9:59:23 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory D:\OEMM02092018\OracleMetadataManagement\tomcat\webapps\ROOT has finished in 454 ms
Mar 23, 2018 9:59:23 AM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-11580"]
Mar 23, 2018 9:59:23 AM org.apache.catalina.startup.Catalina start
INFO: Server startup in 52606 ms
Mar 23, 2018 9:59:23 AM org.apache.catalina.core.StandardServer await
SEVERE: StandardServer.await: create[localhost:11581]:
java.net.BindException: Address already in use: JVM_Bind
at java.net.DualStackPlainSocketImpl.bind0(Native Method)
at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
at java.net.ServerSocket.bind(ServerSocket.java:375)
at java.net.ServerSocket.(ServerSocket.java:237)
at org.apache.catalina.core.StandardServer.await(StandardServer.java:444)
at org.apache.catalina.startup.Catalina.await(Catalina.java:781)
at org.apache.catalina.startup.Catalina.start(Catalina.java:727)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:294)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:428)


The error is logged in the Tomcat log files located at <OEMM_INSTALL_DIRECTORY>/OralceMetadataManagement/data/logs/tomcat.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.