Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Errors Starting Two Instances of Tomcat 6 on Windows Server

DZone's Guide to

Errors Starting Two Instances of Tomcat 6 on Windows Server

· DevOps Zone ·
Free Resource

Automatic continuous monitoring keeps continuous deployment pipelines flowing smoothly and efficiently. Try Instana APM to automatically monitor containers and microservices!

Today I was setting up a second tomcat instance on a single Windows machine and was not able to run two instances at the same time. The first instance started fine, but when I went to start a second instance the second server would not start.

I found the following errors in the logs from the jakarta_service_20121010.log:

[2012-10-10 14:37:15] [206 javajni.c] [error] The specified module could not be found.
[2012-10-10 14:37:15] [985 prunsrv.c] [error] Failed creating java C:\Java\jre6\bin\client\jvm.dll
[2012-10-10 14:37:15] [1280 prunsrv.c] [error] ServiceStart returned 1

At first, both services where set to use jvm mode for both Startup and Shutdown.

But the solution to allow both to work, was to set both services to Java mode for both Startup and Shutdown as seen here:

Tomcat6w.exe Service settings

Now running multiple instances runs like a charm.

 

 

Automatic real-time observability is critical to getting the full benefit of CI/CD. Hear @DevOpsDon discuss how Franklin American Mortgage Company cut their new application deployment time from 6-12 months to 2 weeks with the help of Instana APM.

Topics:

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}